Docs

Yes / No Block

Published July 25, 2026

Use a Yes / No block when a question should produce a clear binary answer. It is best for qualification gates, consent checks, eligibility questions, simple preferences, and pass/fail quiz logic where the next step depends on one of two outcomes.

Yes / No blocks can stay lightweight for simple intake, or become more powerful when paired with response tags, scoring, answer keys, immediate feedback, and Jump Logic.

Best used for

Qualification gates

Ask whether a participant meets a requirement before sending them to the next relevant step.

Consent or confirmation

Capture a clear yes/no acknowledgement before continuing a flow.

Eligibility checks

Route participants based on whether they qualify for an offer, service, or next action.

Simple preference questions

Ask binary preference questions when a longer choice list would add friction.

Knowledge checks

Use scoring, an answer key, and immediate feedback for simple right/wrong quiz moments.

Fast segmentation

Assign tags to Yes and No so downstream copy, exports, and routing stay easy to read.

When to choose another block

Choice Buttons

Use Choice Buttons when the answers are short conversational labels, but not literally Yes and No.

Multiple Choice

Use Multiple Choice when the question needs three or more options, visible cards, or multi-select behavior.

Scale block

Use a Scale block when the answer has intensity, frequency, satisfaction, or agreement levels.

Text Response

Use Text Response when the participant needs to explain their answer in their own words.

Setup flow

  1. Add a Yes / No block from the Question Blocks palette.
  2. Write a prompt that makes the decision easy to answer without extra context.
  3. Turn on Required response when participants must answer before continuing.
  4. Optionally assign a custom Yes tag and No tag for personalization, exports, and routing.
  5. Enable scoring or answer key settings when the block is part of a scored quiz or knowledge check.
  6. Add Jump Logic when Yes and No should lead to different next steps.
  7. Preview the block and confirm the labels, feedback, and routing behave as expected.

Settings reference

Required response

Prevents participants from moving forward until they choose Yes or No.

Yes tag and No tag

Stores a cleaner response signal for outcome copy, exports, automations, and routing.

Scoring

Basic+
Assigns separate integer values to Yes and No for score-based outcomes.

Answer Key

Basic+
Marks Yes or No as the correct answer for knowledge checks.

Immediate feedback

Basic+
Shows right/wrong feedback after the participant answers 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

Pro
Routes participants based on their Yes/No answer, tag, score, or related variables.

Tags and placeholders

The Yes tag and No tag fields help turn a simple binary answer into a reusable signal. Use tags when the visible answer is too plain for reporting or follow-up copy.

  • Leave tags blank when the literal Yes or No value is clear enough.
  • Use custom tags when downstream copy should say something more specific, such as qualified, not_qualified, interested, or not_ready.
  • Insert {{tag:<questionId>}} or {{tags:<questionId>}} after this block to reference the selected tag.
  • Read the Response Tags guide for placeholder behavior across outcome copy, exports, and automations.

Scoring and feedback

Turn on scoring when Yes and No should contribute to a total score. This works well for assessments, qualification quizzes, and simple eligibility models.

  • Assign separate integer values for Yes and No.
  • Values stay within the -9,999 to 9,999 range.
  • Use Answer Key when the question has a correct answer.
  • Enable Immediate feedback when participants should see right/wrong feedback after answering.
  • Show {{total_score}} on completion and use the Scoring Logic guide for score-based outcomes.

Routing examples

Yes / No blocks are especially useful when a binary decision should change the participant's path.

Lead qualification

Route Yes to booking or lead capture, and route No to a lighter nurture outcome.

Eligibility

Route eligible participants to the next step and send ineligible participants to a helpful outcome message.

Consent

Continue only when consent is Yes, or end the flow with instructions when consent is No.

Support triage

Ask if a condition applies, then show a more specific follow-up question only when needed.

Rules evaluate top-to-bottom and can use the Yes/No response, custom tags, scores, or variables from earlier blocks. See the Logic & Branching guide for supported operators and guardrails.

Troubleshooting

Why should I use Yes / No instead of Choice Buttons?
Use Yes / No when the decision is truly binary and the labels should remain Yes and No. Use Choice Buttons when the two answers need custom labels such as Book a call and Send me details.
Do I need custom tags for every Yes / No question?
No. Add custom tags only when exports, outcome copy, routing, or automations need a more specific signal than the visible Yes or No answer.
Can Yes and No have different scores?
Yes. When scoring is enabled, assign separate integer values to Yes and No so the answer contributes correctly to the participant's total score.
Can Yes and No go to different pages?
Yes. Use Jump Logic to route Yes and No to different future questions, lead capture steps, outcome screens, or other available destinations.

Tips

  • Use a Yes / No block only when the participant can answer confidently without more options.
  • Keep the prompt specific so participants understand what Yes means.
  • Use custom tags when the answer will drive routing, automations, or personalized outcome copy.
  • Test Jump Logic after changing tags, scoring, or answer key settings.
  • Use Choice Buttons instead when the two answers need branded or action-oriented labels.
Share