Outcomes

Published July 23, 2026 • Updated July 25, 2026

Outcomes is step three of the Flow Builder. It is organized into Default outcome, Actions, and Conditional outcomes so you can build the final participant experience from top to bottom.

This guide will walk you through:

• Writing the outcome title and body copy with rich text and variables.
• Toggling whether the total score or submitted answers appear on the report card.
• Using the variable picker and inline autocomplete to echo total score, variables, tags, and lead capture fields.
• Adding CTA buttons or richer cards that open a link or an existing Lead Capture form.
• Configuring link behavior, lead attribution, and analytics goals.
• Building score-, variable-, and intent-based conditional outcomes with clear precedence.
• Saving your changes or moving to the final publish step.

When to use this

Configure Outcomes after arranging your Flow Blocks and any lead capture. The page combines the final UI components participants see after submitting the flow.

How it works

• Outcome title and message: Both fields include outcome-focused default copy, which you can edit with the rich text editor on Basic and above. The editor caps input at 5,000 characters and allows placeholders through the variable picker.

• Show total score: Toggle this switch to show the summed score on the outcome card. Score display requires Basic and is useful after scoring is enabled on at least one question. For a live score while participants answer, use Running score in Appearance → Modality & Experience.

• Show submitted responses: Turning this on shows the questions and answers the participant actually encountered on their routed path. Questions hidden by another intent or skipped by Jump Logic are excluded. Turn it off when you prefer to keep answers private while still showing the custom message and optional score.

• Actions: Add up to two CTAs to the default outcome and up to two replacement CTAs for each conditional outcome. Each CTA supports:

  • Open a link: Add button text and a web address beginning with HTTP or HTTPS. Use Open in new tab to keep the completed quiz available.
  • Open a lead form: Select an existing Lead Capture block from Build Flow. If the flow has multiple lead forms, the selector shows both the block position and title, such as Step 4: Business Address.
  • Button or card presentation: Buttons are compact. Cards can also include a supporting description and an optional image selected or uploaded through the Asset Library. Image alt text is managed with the asset.
  • Primary or secondary style: Use primary for the main next step and secondary for an alternative.

• Button action: Choose Open a link, Open a lead form, or Schedule a meeting. Booking actions use a connected Calendly event type and open the scheduler directly on the Outcome.

• Tracking and behavior: Link actions can optionally use Track click as a lead. When enabled, choose a standard goal—Booking, Request call, Purchase, Download, or Other—or select Create custom goal.... Lead-form actions track form opens and successful submissions automatically. Booking actions automatically track the scheduler opening and completed booking with the Booking goal.

• Conditional outcomes: Pro users can add score, answer/variable, or intent conditions. Each condition can override the title, message, and actions. Rules are evaluated by type (variable override, then intent, then score) and by list order within each type; the first match wins. This allows safety or operational flags—such as hardship, an accepted transaction, or another complexity—to override a general path result. See Intent Paths for path-specific outcomes.

The condition chooser distinguishes setup requirements from plan access:

• Score is available only after scoring is enabled on at least one question.
• Answer or variable is available only after an answer is saved to a variable or a custom variable exists.
• Intent is available only after at least one intent is defined.
• A disabled option explains what must be configured. A lock icon indicates that the plan does not include Conditional Outcomes; select the locked option to see the upgrade explanation.

• Navigation: Use Back to flow to adjust blocks. The sticky footer shows whether changes are unsaved; choose Save changes to remain on the page or Save and continue to move to Appearance.

Step-by-step

1. Update the outcome title or keep the outcome-focused default copy.
2. Write the outcome message and insert placeholders ({{total_score}}, {{tag:<questionId>}}, or any custom variable) with the variable picker or inline {{... autocomplete.
3. Choose whether to display the total score and the full list of responses; score visibility requires Basic+.
4. Optional: under Actions, add a CTA and choose whether it opens a link or an existing Lead Capture form.
5. Choose a compact button or a card. For a card, add supporting copy and choose or upload its image through the Asset Library.
6. For link actions, choose same-tab or new-tab behavior and optionally enable lead tracking with a standard or custom goal.
7. Optional: under Conditional outcomes, add an available score, answer/variable, or intent condition and configure its override copy and actions.
8. Choose Save changes or Save and continue to move to Appearance.

Tips / Gotchas

• If you leave the outcome title or message blank, the builder falls back to default text, so every flow has useful next-step copy.
• Score-based rules only run when scoring is enabled, and numeric inputs are clamped between -9,999 and 9,999 for consistency.
• A disabled condition means the quiz does not yet contain the required scoring, variable, or intent setup. A lock means Conditional Outcomes are not included in the current plan.
• Use the between operator to cover a range of totals; ensure the min is lower than the max before saving.
• Turning Show submitted responses off keeps answers out of the report card while still showing the title, message, and optional score.
• Show total score controls the outcome card only; live score visibility is managed separately by Running score in Appearance.
• Variable-match rules run before intent and score rules. Use them for explicit safety, status, or complexity overrides that must win regardless of the active path.
• Intent rules run after variable overrides and before score rules, which makes them useful for path-specific outcome messages when no higher-priority override matches.
• When Show submitted responses is enabled, the report includes only questions encountered on the participant's actual route.
• Goal type only affects analytics grouping; it does not change CTA behavior for participants.
• If Track click as a lead is off, CTA clicks are still tracked as exits/clicks, but they are not counted as lead captures.
• An outcome lead-form action reuses the original Lead Capture block. Edit its fields, consent, and copy in Build Flow rather than creating a second form configuration.