Some paths through a bot shouldn’t reach the last question. A respondent might be disqualified halfway through, or they’ve confirmed everything you need by step three. Forcing them to a fixed ending creates friction and, in disqualification cases, a worse experience than just stopping cleanly where it makes sense.
Any content block can now be toggled as the intake’s endpoint. When a respondent reaches it, that block delivers the closing message and the submission is finalized right there. No redirect, no “please wait” screen.
Ending early doesn’t skip anything on the back end. Contact creation, record mapping, the process board card, and any routing rules all fire exactly as they would for a standard submission. The difference is where the conversation stops for the respondent, not what happens with the data.
Each early-ended submission also carries an outcome label you define. It shows up on the submission detail view and is available as an export column, so you can filter and report on which path each case took.
Pair an early-ending block with a condition and you get branch-specific closings. One branch says “You’re all set, we’ll be in touch.” Another says “Based on your answers, this isn’t the right fit right now.” Each ends the intake at exactly the right point, with the right message.
Available on Free, Pro, and Business plans.
Any content block can now be marked as the end of a path. When a respondent reaches it, that block becomes the closing message and the submission is finalized right there — the rest of the flow is skipped and the full pipeline (contact, record, card, routing) still runs. Pairs with conditional logic for branch-specific endings like disqualification or 'you're all set'. Each early-ended submission stores an outcome label you choose, shown on the submission and available as an export column.