Thank you page design: say what happens next

The thank you page is sometimes the only confirmation a visitor gets. You built it after the form worked, so you know the order exists, and you see it from your own account. A new visitor has none of that. They see a short thanks, a logo and a button to the homepage. If the page shows no order number and no email address, they cannot match it to what they just did. If the next step is an email, and the page does not say so, they wait, then write in, or they search their inbox for a message from a sender the page never named.

• The page names the order number, or the account email, so the visitor can match it to what they did.
• It says what arrives next, from which sender, and roughly when.
• The next step is one link that opens without a second login.
• A refresh or the back button shows the same confirmation, not an empty page or a second form.

A visitor who has just paid or signed up wants one detail to check later, against the receipt in their inbox or the bank statement. Give them the order number, the plan name or the account email they entered. A line that says thanks for your order gives them nothing to match. Compare a bare thanks for your order with this: Order 1043 for two bowls. The receipt goes to ruth@example.com. The first version makes the visitor guess whether anything exists. The second lets them check the address on screen before they leave. Keep the reference short enough to read on a phone without sideways scrolling.

A vague next step costs more than a missing one. We will be in touch leaves the visitor unsure whether to wait, check spam or act on the site. Name the sender the message comes from, then give the one action to take if nothing arrives, such as a resend button. If the account only works after the visitor confirms the address, say so on the page, not only in the email, because some visitors close the email before they reach the second line.

Visitors refresh a page that looks stuck, and they press back from the next screen. On some sites the thank you page is simply another step in the form, so back returns to a blank form and refresh asks whether to submit again. Test both on the page itself. After the form completes, reload the thank you page, then press back and forward. The page should show the same confirmation each time, with no form, no second submit prompt and no empty state. If the page loads the order from a lookup, a lookup that is not ready yet should show a waiting line, not an error that reads as a failure.

A new visitor can reach this page after a free signup form, since no card is needed and the visitor has a working inbox for the confirmation. The report shows the page's text, the step where the visitor stopped, what they did next and a screenshot, so you can read the page the way a stranger does. A purchase is different. The test stops at the payment step and never submits a card, so it cannot reach the thank you page that follows a paid order. Check that page yourself, with a real order you refund, or a test order if your store has a test mode, and read the email it sends.

Signup flow testing

An owner who changes the signup form, the email sender or the redirect after a purchase needs this check again. A page that worked last month can name the old sender, or show nothing after a redirect change. After each change, send a new visitor through the signup, read the text, then reload and press back. With paid credits, a test account lets visitors reach a signup behind a login, and each preview deploy can be checked first.