Thank you page best practices

The moment after someone presses submit is the only point in a form where they have given you everything and you ask for nothing back. Most forms spend it on a single word. The better ones use it to remove doubt: yes, it arrived; here is what happens now; here is the one thing worth doing next.

Those three jobs are the whole of thank you page best practice. Confirm what happened, say what comes next and when, and offer one useful action. Then make two smaller decisions on purpose rather than by habit: whether to send people somewhere else automatically, and whether the moment deserves confetti.

Confirm what happened

Nielsen Norman Group’s first usability heuristic is visibility of system status: a system should keep people informed about what is going on through appropriate feedback within a reasonable time. Its article on the heuristic describes what happens without that feedback. People are not sure their action worked, and they tap the same button again.

For a form, the thank-you screen is that feedback. Its eyebrow and title should say, in plain words, that the submission arrived and where it went. The incident report form, built for a fictional distribution centre, does it in two lines: “Report received” and “The safety officer has been emailed”. The person reporting now knows who has it, which is exactly the uncertainty they had.

GOV.UK’s confirmation page pattern is the most complete checklist for this screen. It asks for a reference number if there is one, details of what happens next and when, contact details for the service, links to what people are likely to need next, a feedback link, and a way to save a record. A form’s thank-you screen has room for a title, a short description and one button, so treat that list as a menu and pick the items that matter for this form. If your process issues a reference number later, say where it will arrive.

Say what happens next, and when

A vague “we will be in touch” produces follow up emails. A date or a time window stops them.

The waitlist signup form, for a fictional sourdough subscription, is the example this post embeds, and its thank-you screen is worth reading line by line. Eyebrow: “You are on the list”. Title: “We will email your place number today”. Description: “Places move up when someone you referred joins. Nothing is charged until we confirm your first delivery date.” In three short lines it confirms, sets a same day expectation, rewards the referral question the form just asked, and answers the money worry before anyone has it.

The incident report sets its expectation just as precisely: “You will be contacted within one working day. If anyone needs medical attention now, call 000 first and finish this later.” The second sentence is the most important line on the screen, because it is the only thing somebody might need to act on right now.

One caution about promises. The form does not email the respondent on its own. Email alerts send each submission to one address you choose, which is normally your team. If the thank-you screen says a place number or a confirm link is on its way, as the waitlist and the newsletter signup form both do, make sure something you run actually sends it.

Offer one link

The thank-you screen has one button, with a label and a Button URL. That constraint is useful. It forces you to decide the single most valuable next step.

Good choices are specific. The wedding RSVP form sends guests “Back to our wedding page”, where the venue and timings live. A booking request might send people to the timetable, an application to the programme page, a quote request to a gallery of past work. A home page is rarely the best answer; it is where people came from.

Leave the Button URL empty and the button resets the form instead. That is the right behaviour for a shared tablet, like a visitor sign in at a reception desk, where the next person is already waiting. Everywhere else a reset looks like the submission vanished.

Redirect or stay

There are two ways to move people on, and they behave differently.

The Post-Submit Redirect add-on sends the person straight to a URL the moment the submission is saved. The thank-you screen is never shown. It accepts web addresses starting with http or https, or a path on the same site. Use it when another page does the confirming better, such as a payment page for an order that is paid separately, and make sure that page says the form was received.

The thank-you screen’s Auto-redirect after setting waits a number of seconds, from 0 to 120, then follows the Button URL. It only works when a Button URL is set, and 0 or empty turns it off. The person sees your message first.

Choose by what the message carries. If it is decoration, a short timed redirect to a useful page is fine. If it carries instructions, stay. WCAG 2.2 treats timed redirects as time limits under its Timing Adjustable criterion, and lists a meta redirect with a time limit among its common failures. Its Status Messages criterion exists so that people using screen readers are told about status changes that do not move focus. A confirmation that disappears before it has been heard has not confirmed anything.

Confetti and tone

Show confetti is off by default, and that is the right default. It is a small celebration, and it fits moments people are glad about. The waitlist, the wedding RSVP and the party RSVP examples all switch it on. The incident report and the visitor sign in leave it off.

Tone follows the same rule as confetti. A waitlist can be warm. An incident report should be calm, plain and short. A health intake should say who reads the answers and nothing cheerful about it.

The newsletter example shows a subtler case. Its screen reads “Almost there” and “Check your inbox to confirm”, because the subscriber is not on the list until they click the link. It has confetti on. There is an argument for saving the celebration until the step that finishes the job, so the person does not feel done and close the tab.

Layout matters less than words, but it matters. There are four thank-you layouts: editorial, split, centered and card. Split and centered are built around an image and fall back to card when there is none, so check the preview after choosing one.

Layouts by form type

The table at the end of this article pairs ten common form types with the message the thank-you page should carry and the next action to offer. Read the “Next action” column as the decision it is: a button, a reset for a shared device, or a straight redirect.

Common mistakes

• A one word “Thanks”. It confirms nothing about what happens next.
• Promising an email nothing sends. Check the path before the screen goes live.
• Redirecting before the message is read. Especially on anything with urgent instructions.
• Using the redirect add-on on a form whose confirmation matters. The thank-you screen is skipped entirely.
• Confetti on serious forms. A celebration after a complaint reads as not listening.
• Telling people to “open the link again” to change a reply without saying what that does. Submitting again creates a new response rather than editing the first, so say that the latest reply counts.
• Turning the screen off on a personal form. A blank form reappearing looks like a failure.

Survey researchers know the last item in a list carries extra weight, the recency effect described in the note on primacy and recency. The thank-you screen is not a survey option, but it is the last thing people see, and the welcome screen at the other end of the form deserves the same care; the post on improving form completion rate covers that half.

Build it

The custom thank you page shows the screen on finished forms, and the guide to designing welcome and thank-you screens walks through the settings. Every form in the builder, classic or conversational and built from its 41 component types, ends on the same thank-you screen: eyebrow, title, description, button text, Button URL, Auto-redirect after and Show confetti. Around it sit the four add-ons (e-signing, webhooks, email alerts and the Post-Submit Redirect) and the four access types that decide who reached the form in the first place.