Skip to main content
Questions are reusable templates you create once and deploy across your community—in challenges, on reward redemption, when users log in, and more. Define them once, use them everywhere, and gather consistent data.
Settings Location: Navigate to Control Room > Settings > Questions to create and manage questions.

​
Configuration Tabs

Every question you create has three tabs of settings:
  • Type
  • Basic Info
  • Behavior
Choose the question type that determines how users answer

​
Type

Select how users will answer your question.
Single-line text input. Good for names, emails, short responses.
Multi-line text area. For open-ended feedback, essays, detailed responses.
Users pick one option from several. Classic format.
Users select multiple options. Good for “choose all that apply” scenarios.
1-5 stars, 1-10 scale, etc. Great for feedback and satisfaction.
Calendar picker for dates and times.
Numeric input field. Can set min/max constraints.

​
Basic Info

Configure how your question appears to users.

Name (Internal Identifier)

How you identify this question in your system. Can’t be changed after creation. Use something like user_bio or loyalty_card_number.

Label (User-Facing)

What users actually see. This is the friendly question text like “Tell us about yourself” or “Your Loyalty Card Number”.

Placeholder Text (Optional)

Hint text that appears in the input field before users type. Example: “e.g., Enter your member ID” or “Tell us your story…”

​
Behavior

Control how the question behaves when deployed across your community.
Once set, the value cannot be changed by the user. Good for data that should stay fixed (like account numbers, member IDs).
Each user can only submit one answer. They can’t change their response after submitting.
Pre-fill with the user’s profile data if available. Saves users from re-entering info you already have.
Make this question available for selection in challenges, rewards, and other places. Turn off to keep it hidden (useful for drafts).
Set a limit on how many times a particular answer can be used across your community. For example, if you have a “Referral Code” question, you might limit each code to 5 uses. Enter 0 for unlimited.
Toggle to set up custom validation rules for the answer (email format, minimum length, specific patterns, etc.).

​
Where Questions Get Used

Once saved, you can deploy your question in multiple places across your community:

After Login

Collect data when users join (like building a loyalty card profile or capturing preferences). Great for gathering initial user info upfront.

In Challenges

Add questions as actions within challenges. Users answer as part of the challenge experience.

In Posts

Add feedback or polling questions to community posts and announcements.

On Rewards

Collect info when users redeem a reward (shipping address, preferences, account details needed for redemption).
The answer data flows to your analytics, so you can see trends across all deployments of each question.

​
Common Use Cases

Loyalty Card Data

Ask “Member ID”, “Birthday”, “Preferred Service” at login to build member profiles for your loyalty program.

Reward Redemption

Ask “Shipping Address”, “T-Shirt Size”, “Account Email” when users claim a reward to gather fulfillment info.

Challenge Feedback

Use “How would you rate this challenge?” across all challenges to track satisfaction trends.

Surveys & Polls

Create a set of predefined questions and reuse them in posts to build consistent feedback across campaigns.

​
Best Practices

Use descriptive internal names like loyalty_card_number or shipping_address, not abbreviated ones. You’ll thank yourself later.
Shorter questions get better response rates. Cut unnecessary words.
Add placeholder text to guide users. “e.g., 123-456-7890” for a phone number is more helpful than nothing.
Pick a naming style (snake_case or camelCase) and stick with it across all your questions.
Check what questions are getting answered, which are skipped, and if your answers are useful. Refine based on real data.
Archive questions you no longer use instead of deleting them. This preserves your historical data.

​
Next Steps

  1. Go to Questions in your Control Room Settings
  2. Click Create Question and pick a question type (Short Text, Multiple Choice, Rating Scale, etc.)
  3. Fill in Basic Info (internal name, user-facing label, placeholder)
  4. Configure Behavior (whether answers are immutable, available in the bank, need validation, etc.)
  5. Deploy your question in challenges, rewards, or at login
  6. Check analytics to see how users answer
Create once, use everywhere.