Shape the VIP release brief for your Truth or Dare product.

This private intake captures the final gameplay and moderation questions for the first premium release. The form stays polished and lightweight, while the prompts below now reflect the exact customer-facing question set for the VIP build.

Status: VIP clarification intake ready

Focus: Truth or Dare design-partner release

Roadmap: reusable product line to follow

Section 01 · Game flow and experience

Answer the final gameplay questions for the VIP release.

The form keeps a premium presentation, but the prompts below now mirror the final customer-facing question set closely.

How should players join a game?
Should the spinning bottle be a true animation/GIF, or is a polished visual spin effect enough?
Should the same player ever be picked twice in a row?

How should players join a game?

Tell us whether joining should include everyone in the channel automatically, require manual join, use an invite list, or be role-based.

Should the spinning bottle be a true animation/GIF, or is a polished visual spin effect in the card enough?

Should the same player ever be picked twice in a row, or should the bot avoid repeats where possible?

Section 02 · Packs, permissions, and card actions

Define how content, links, and controls should work.

Group related answers together here so the brief stays clean while still covering the exact decision points for packs, permissions, and card behavior.

Who should manage custom packs and questions/dares?
Do you want packs to support different categories or moods?
How should dares with links be shown, and who can add them?
What actions should appear directly on the cards?

Who should be allowed to manage custom packs and questions/dares, and do you want packs to support different categories or moods?

This is also the right place to list any categories or moods you want supported, such as party, couples, spicy/adult, team-building, or clean/safe-for-work.

For dares with links, should the card show the full link, show a button like Open Dare, or both? Should links be admin-created only, or should trusted users also be able to add them? What actions do you want directly on the cards?

Section 03 · Moderation, persistence, and launch timing

Capture moderation expectations and first-release timing.

These final answers cover the moderation guardrails, whether the experience should stay lightweight or persistent, and the date or event the first version needs to support.

Is there a target date or event you want the first version ready for?

Who should review or sign off on the final direction?

Do you need moderation controls such as safe-for-work only, adult/18+ packs, blocked topics, or role restrictions? Should the bot keep game history/logs or keep each session temporary? Do you want players to have profiles/stats, or should it stay lightweight and session-based?

Optional. You can also paste supporting links, examples, or reference docs on separate lines.

Submission

You can revisit this private brief and resubmit as the product direction sharpens.

Submission received

Thank you — the VIP product brief is in.

The clarification set has been captured for internal review. If the product direction changes, you can reopen this private link, update the form, and submit again.

Submission status Saved successfully

Submission reference A reference will appear here when returned by the endpoint.

Resubmission keeps the experience private and lightweight.