An ending is the screen a visitor lands on after their last question. It decides what they see (a thank-you, another page, or a booking calendar), whether they count as qualified, and which tags go to your CRM. Every form has at least one ending, and most funnels use several: book qualified leads on a calendar, thank or redirect the rest.
Endings live in the Endings section at the bottom left of the form builder. Click the + icon to add one, and click an ending to edit it; its settings appear in the right-side panel.
Success Message: a headline and text on your form's design. The usual choice for unqualified leads or simple thank-you screens. Click into the text on the canvas to edit it.
Redirect: sends the visitor to a URL of yours, for example a thank-you page carrying your tracking pixel. You can append the lead's answers to the URL as query parameters; see How to Pass Form Field Values as URL Parameters in Redirects. On an embedded form, the redirect takes over the whole page, not just the form box.
Calendar: a booking widget inside the form, pulling live availability from GoHighLevel or Calendly, so qualified leads book without leaving the form. After a booking you choose what happens next: show a confirmation message or redirect to a URL. GoHighLevel calendar endings can also add booking tags that fire only when a call is actually booked.
Each ending carries a qualification: Qualified, Unqualified, or No qualification. Whoever reaches the ending gets that status. It drives your analytics (qualified vs unqualified counts), lets you filter leads, and sets the default tag when the ending is created: a qualified ending starts with roas-qualified, an unqualified one with roas-unqualified.
The ending's Tags section lists the CRM tags applied when a lead completes the form at this ending. Edit them freely; the full picture of when tags are added and removed is in How ROASForm Tags Work with GoHighLevel.
Want to celebrate? Turn on the Confetti switch in an ending's settings to play a celebration animation when the visitor lands there. It is available on Success Message endings, and on Calendar endings that show a confirmation after booking, where the confetti plays on the booking confirmed screen. Redirect endings don't offer it, since the page navigates away. The builder preview replays the animation whenever you select the ending, so you can see it without submitting the form.
Logic rules decide first. In the Logic tab you route leads to endings based on their answers or score, for example budget above your minimum goes to the Calendar ending, everyone else to the thank-you.
The default ending is the fallback. Exactly one ending is marked as default, and it is shown whenever no logic rule points somewhere else. Use the Default switch in an ending's settings to change which one it is; step-by-step in How to Change The Default Ending.
You can mix as many endings as you need, including several calendars (even GoHighLevel and Calendly in the same form) booking into different calendars based on the lead's answers.
Calendar endings need a contact field. Booking requires at least one of email or phone, and the builder enforces it: it marks the field required or adds it for you, and stops you deleting the last one. A red warning badge on a calendar ending means it has a configuration issue (no calendar selected, or the contact field is missing).
An ending with an issue can't be the default. Fix the warning first, then flip the Default switch.
Endings mark completion. Reaching any ending counts the submission as complete: ending tags are applied, abandon tags are removed, and the lead stops counting as a partial.
