When you run a survey or form, the End page is what people see after they finish—your thank-you message, next steps, or a redirect to your site. With multiple End pages and Branch logic, you can show a different closing experience depending on answers: promoters vs detractors, qualified leads vs “not a fit”, consent declines, or regional follow-up links.
This guide explains how to add End pages, customize each one, and route respondents using logic—plus how rules are ordered and how this differs from simply reordering questions.
When different End pages help
Typical use cases:
- Customer satisfaction: Detractors see an apology, link to support, and optional redirect; promoters see a review or referral ask.
- Lead forms: “Book a call” End page for high intent, a short “We’ll be in touch” End page for everyone else.
- Screening: Early disqualification—if someone picks “Not employed in this industry”, jump straight to a polite End page without exposing the full questionnaire.
- Compliance / opt-out: A dedicated End page copy when someone declines consent or marketing permission.
Before you start
You need:
- Editor access to the form in Responsly.
- More than one End page if you want truly different screens—use Add End Page in the left panel (under END PAGES). Note: some plans prompt an upgrade when adding extra End pages; at least one End page is always available.
- Branch logic (Essential plan and above) to define Go to jumps—including jumps to a specific End page.
If logic controls are locked, upgrade the workspace or ask your account owner to adjust the plan.
Add and edit End pages
- Open your form in the builder and stay on the Create tab in the top bar (Connect, Share, and Analyse are the other main tabs).
- In the narrow toolbar on the far left, select Edit (pencil icon)—that is the mode where you manage questions and End pages.
- In the left panel, scroll past your question list and Add question until you reach the END PAGES section. Existing End pages appear as thumbnails (for example Thank you!).
- To add another closing screen, click Add End Page (the dashed tile with the plus icon under END PAGES). You must keep at least one End page; you can remove extras only when more than one exists.
- Click an End page thumbnail to select it: the canvas in the middle shows a live preview, and the right END PAGE panel lets you turn on Image/Video, Comment, Add redirect button, Automatic redirect, open layout settings, and related options—same building blocks as for a single thank-you screen, but configured separately per End page.

Give each End page a clear internal title (e.g. “Detractor – support”) so you can pick the right target in logic dropdowns.
Route people with Branch logic
Branch logic runs per question (and follows the same idea on group pages that evaluate child questions—match what you see in the builder).
- Select the question that should decide what happens next.
- Open Branch logic (sometimes labeled Logic in the builder).
- Add a rule: set conditions (for example “Score is less than 7” or “Choice is Product B”).
- Set the action to Go to (or equivalent) and choose either another question/page or an End page from the list—End pages appear numbered with their titles.
- Optionally add “In all other cases go to” so every respondent has a defined path when no condition matches.
- Use “Always go to” only when you want that question to always override the default linear flow (use sparingly—it forces one destination every time).
After publishing, test with Preview and a few answer combinations to confirm each path lands on the intended End page.
Rule order matters
Rules are checked from top to bottom. The first jump whose conditions are true is applied for that step. Design tips:
- Put narrow conditions (specific segments) above broad ones.
- Avoid overlapping conditions that both match the same answers unless you intend the higher rule to win.
- If results feel “random”, reorder rules or simplify conditions.
Quotas and early completion
If you use response quotas, the system can still redirect respondents to an End page when a quota closes—treat that as a separate distribution concern from manual Branch logic, but expect the same End page components to display when a quota forces an early finish.
Translations and branding
If the form uses Translations, translate each End page’s title and description like any other visible text so every language version shows the correct closing message. Keep variable names consistent across languages.
Related ideas
- Variables and calculations: combine with logic for scored quizzes or weighted routing before choosing an End page.
- Exports: responses still store normally; different End pages do not break reporting—they change what the respondent sees, not whether the response is stored.
For step-by-step export options, see How do I export survey data?. For in-product Analysis, use your workspace help once paths are live.



