- Published
- Byline
- GoHighLevel Partners Editorial
- Filed under
- GoHighLevel Automation
The most attentive moment a visitor will give you, spent on ‘thanks, we’ll be in touch’ — here are the three jobs the page should be doing.
Thank you step setup: the page in your funnel doing the least work
The thank-you step is the page every funnel has and almost nobody designs. It usually says some version of “Thanks, we’ll be in touch”, and then does nothing with the most attentive moment the visitor will ever give you — the seconds immediately after they committed to something.
That page has three jobs, and most implementations do only the first. It has to confirm what just happened, tell the person what to do next, and record the event so the rest of your system knows it occurred.
Job one: confirm, specifically
Vague confirmation creates support enquiries. Say what was received, what happens next, and when — “your request is with us; someone will call within one working day on the number ending 4471” answers the three questions a person is holding, where “thank you for your submission” answers none of them.
Where the next step depends on the person doing something, say so plainly and immediately. A form protected by a double opt in step is the clearest case: if the subscription does not exist until they click a link in an email, the thank-you page is the only place they will learn that, and a page that omits it is the main reason confirmations go unclicked.
Job two: give them something to do
The visitor is engaged and has a few seconds of attention. What to offer depends on what they just did, and the useful principle is that the next action should reduce the work still outstanding rather than start something new.
| What they just did | The best next action | What to avoid |
|---|---|---|
| Requested a call | Book the time themselves, on a real calendar | Leaving the scheduling to a phone tag exchange |
| Booked an appointment | Add it to their calendar; prepare what they need to bring | An unrelated offer, which reads as a sales page |
| Bought something | Access, delivery expectations, and how to get help | A further purchase before the first is even delivered |
| Downloaded something | The file itself, plus a single relevant next step | A page whose only content is “check your email” |
| Subscribed | What arrives, how often, and how to reply | Silence until the first campaign, weeks later |
Turning a call request into a booked appointment on this page removes the whole back-and-forth that would otherwise follow, which is why it is worth doing before anything else on the list. Embedding the booking step here means the calendar configuration matters — durations, notice and ownership, as set out in a calendar clients can book into — and the appointment then inherits the confirmation and reminder path described in an automated reminder system, which is where the levers for reducing no-show appointments live.
Where a further offer genuinely belongs, keep it subordinate to the confirmation and make it relevant to what was just bought. A post-purchase offer is a different mechanism from downsell branching, which runs on a decline; putting a declined offer’s downsell on the thank-you page confuses both.
Job three: record that it happened
The thank-you step is where conversions are usually counted, and where tracking most often breaks. Three things need to be true.
- The page is reachable only after the action. A thank-you URL anyone can visit will be visited — by you, by crawlers, by a client showing someone the site — and every visit counts as a conversion.
- The source survives. Whatever carried the visitor in has to reach the record, so a conversion can be attributed weeks later. That is what UTM parameters does, and it has to be preserved through the form rather than lost at the redirect.
- The tags actually fire. Conversion tags on this page are the ones most often blocked, misordered or duplicated, and the causes are usually in code in the page header rather than in the tag itself.
Verify by completing a real submission and looking at what arrived, not by assuming. A funnel fed by a paid social funnel depends entirely on this page reporting honestly; a thank-you page that fires twice teaches the ad platform to optimise towards a number that does not exist.
The failure modes worth designing out
A dead end. A page with no navigation and no next step leaves the visitor to close the tab. Give them a way back into the site.
Content that contradicts the sequence. If the page says “we will call today” and the automation waits until tomorrow, the page is generating the complaint. Write the page and the follow-up together.
A redirect that loses the record. Sending the visitor to an external page after submission frequently drops the parameters and sometimes the tracking. Confirm on your own page first.
No path for someone who prefers to talk. A proportion of people will want a person immediately. A visible number, with missed call text back behind it, catches them.
Nothing for the people who go quiet. The page is the start of a sequence rather than the end of one; what follows is a nurture sequence, and it should begin from what the person actually did rather than from a generic welcome.
Then measure it like a step
Thank-you pages are treated as terminal, which is why nobody optimises them. Treat the page as a transition with its own rate: of the people who reached it, how many took the next action offered? That figure belongs alongside your other stage rates, in the manner measuring conversion by stage describes, and it is usually low enough to be worth attention.
It is also a good candidate for a test, because the changes available are structural rather than cosmetic — offering a booking versus promising a call, one next step versus three. The method, and the reason to judge it on the downstream outcome rather than on clicks from this page, is in testing a funnel step.
Frequently Asked Questions
What should a thank-you page actually say?
What was received, what happens next, and when — specifically. ‘Someone will call within one working day on the number ending 4471’ answers the questions a person is holding; ‘thank you for your submission’ answers none of them and generates support enquiries.
What is the highest-value next step to offer?
Usually letting the person book a time themselves rather than waiting for a call. It removes the entire back-and-forth that follows a call request, and the appointment then inherits the confirmation and reminder path that protects attendance.
Should a thank-you page contain another offer?
Only if it is subordinate to the confirmation and relevant to what was just done. A further purchase presented before the first is delivered reads as a sales page rather than a confirmation, and it undermines the reassurance the page exists to provide.
Why do conversions get over-counted on a thank-you page?
Because the page is usually reachable by anyone with the URL. Every visit by you, a crawler or a client showing someone the site counts as a conversion. Duplicate tag firing, often caused by header code, is the other common source.
Why does campaign attribution break at this step?
Because whatever carried the visitor in has to survive the form and the redirect to reach the record. If it is lost there, the conversion cannot be attributed weeks later, and the ad platform optimises against an incomplete picture.
Should a thank-you page be tested?
Yes, and it is a good candidate because the available changes are structural rather than cosmetic — offering a booking against promising a call, one next step against three. Treat the page as a transition with its own rate and judge changes on the downstream outcome.
We build your GoHighLevel account for you
CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.
- Setup (one-time)$850
- Ongoing (per month)$38.80
No obligation quote · reply within 1 business day
This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.