Docs
Choice Buttons Block
Published July 25, 2026
Use a Choice Buttons block when participants should make a quick single-select decision from short custom labels. It works well for conversational flows, lightweight segmentation, CTA-style choices, and short preference questions where a dropdown or full Multiple Choice layout would feel too heavy.
Choice Buttons share the structured answer model used across question blocks, so each button can support tags, scoring, answer keys, immediate feedback, and Jump Logic.
Best used for
Quick qualification
Let participants tap a short answer that immediately clarifies fit, need, budget, or intent.
Conversational decisions
Use button labels that feel natural in a guided chat-style or simple step-by-step flow.
Short preference questions
Ask participants to choose one direction, category, option, or next action.
CTA-style choices
Offer action-oriented labels such as Book a call, Send details, or Show options.
Light segmentation
Assign tags to each button so follow-up copy and reporting can use cleaner response signals.
Simple knowledge checks
Pair buttons with scoring, an answer key, and immediate feedback for short quiz moments.
When to choose another block
Yes / No
Use Yes / No when the answer is truly binary and the labels should stay as Yes and No.
Multiple Choice
Use Multiple Choice when participants need visible cards, media, tiles, or multi-select behavior.
Dropdown
Use Dropdown when the list is long and only one answer should be selected.
Scale block
Use Scale when the answer needs a rating, intensity, agreement level, or frequency range.
Text Response
Use Text Response when participants need to explain, describe, or enter a custom answer.
Setup flow
- Add a Choice Buttons block from the Question Blocks palette.
- Write a prompt that makes the decision clear.
- Add short button labels that fit comfortably on mobile.
- Turn on Required response when the participant must choose a button before continuing.
- Add optional tags, variables, scoring, answer key, or immediate feedback depending on how the answer will be used.
- Add Jump Logic when different buttons should send participants to different next steps.
- Preview the question on mobile and desktop to confirm button labels wrap cleanly.
Settings reference
Required response
Prevents participants from moving forward until they tap one button.
Button labels
The visible choices participants select from. Short labels work best.
Tags and variables
Stores cleaner response signals for outcome copy, exports, automations, and routing.
Scoring
Basic+Assigns integer points to each button for score-based outcomes.
Answer Key
Basic+Marks one button as correct for knowledge checks.
Immediate feedback
Basic+Shows right/wrong feedback after the participant selects a button when an answer key is configured.
Split Media
Basic+Overrides question-level split media when the quiz uses a Full-Page Split layout.
Jump Logic
ProRoutes participants based on the selected button, tag, score, or related variables.
Behavior notes
- Choice Buttons are single-select only.
- Button labels should be short enough to scan quickly.
- Use Multiple Choice when participants need to select more than one answer.
- Use Dropdown when the answer list is long and compactness matters more than button visibility.
- Use tags or variable keys when reporting needs a normalized value that differs from the visible button label.
Tags, scoring, and feedback
Choice Buttons can be simple visual choices, or they can feed more advanced outcomes.
- Use tags when a button should trigger personalized outcome copy, exports, automations, or routing.
- Use scoring when button choices should contribute to
{{total_score}}. - Use an answer key when the button question has a correct answer.
- Turn on immediate feedback when participants should see right/wrong feedback after they answer.
- Follow the Response Tags guide and Scoring Logic guide for downstream behavior.
Routing examples
Intent routing
Send Book a call to lead capture and Just browsing to a softer outcome message.
Product fit
Route each preferred use case to a different product recommendation path.
Support triage
Use buttons for common issue types, then show the matching follow-up question.
Lead priority
Give high-intent buttons stronger scores or route them to a faster conversion path.
Rules evaluate top-to-bottom and can use the selected button, tags, scores, or variables from earlier blocks. See the Logic & Branching guide for supported operators and guardrails.
Troubleshooting
When should I use Choice Buttons instead of Yes / No?
Use Choice Buttons when the labels need to be custom, branded, or action-oriented. Use Yes / No when the answer should remain a literal Yes or No decision.
Can participants select more than one button?
No. Choice Buttons are single-select. Use Multiple Choice with multi-select enabled when participants need to choose more than one option.
How long should button labels be?
Keep labels short and scannable. If a label needs a full sentence or supporting detail, Multiple Choice cards usually provide a better layout.
Can each button route to a different step?
Yes. Use Jump Logic to route participants to different questions, lead capture steps, outcome screens, or other available destinations based on the selected button.
Tips
- Keep labels short, direct, and action-oriented.
- Avoid using Choice Buttons for long lists.
- Use tags when a label is customer-facing but reporting needs a cleaner internal value.
- Test mobile wrapping before publishing.
- Use Multiple Choice for multi-select or media-rich answer layouts.
- Recheck Jump Logic after adding, deleting, or renaming buttons.
Next steps
Yes / No
Use a literal binary answer when the labels should stay as Yes and No.
Multiple Choice
Use visible cards, media, tiles, buttons, or multi-select choices.
Response Tags
Use tags to personalize outcomes, exports, and automations.
Logic & Branching
Route participants based on selected buttons and related variables.