A form thank-you page has one immediate job: confirm that the submission went through. It can also tell people what happens next, when to expect a response, and where to go if they need help. Done well, it prevents uncertainty for the person who filled out the form and reduces avoidable follow-up for your team.
The right content depends on what the form collects. Someone requesting a service quote needs different information from someone signing up for a newsletter or applying for a place in a course. This guide explains what to put on a form thank-you page, with examples and a checklist you can adapt to your own process.
What a form thank-you page should accomplish
Think of the page as the first step after submission, not a decorative ending. A useful page should:
- Confirm the action. Say plainly that the form was received.
- Set expectations. Explain what will happen next, and give a realistic timeframe if you can.
- Offer a relevant next step. This might be checking an inbox, preparing a document, or booking a time.
- Provide a route for problems. Tell people how to contact you if they made a mistake or do not receive a confirmation.
GOV.UK’s guidance on confirmation pages similarly treats confirmation as a place to reassure people and explain what happens next. Keep the page focused on the completed task; extra promotions or navigation should not obscure that message.
What to put on a form thank-you page
1. A specific confirmation message
Use a clear heading such as “Your request has been sent” or “You’re registered for the workshop.” Specific language is more reassuring than a vague “Thank you” because it names the action the visitor just took.
Avoid saying the request is approved, booked, or complete if it still needs review. For example, an application form submission is not the same as an accepted application. Say “We’ve received your application” rather than “You’re accepted.”
2. A realistic explanation of what happens next
Describe the next step in terms your team can reliably meet. A small repair business might say, “We’ll review your details and call you within two business days.” A research team might say, “We’ll check your responses for eligibility and email you if you qualify.”
If timing varies, avoid promising a precise deadline. You can say, “Our team will review your message during business hours. Response times may be longer on weekends.” The important thing is to set an expectation without creating a commitment your workflow cannot keep.
3. Useful details the person may need
Include information that helps them complete the next step or keep a record. Depending on the form, that could be:
- A reference number or booking date.
- The address, meeting link, or location for an appointment.
- A reminder to check email, including the sender name to look for.
- Instructions for bringing documents or preparing for a call.
- A brief explanation of how to correct information they submitted.
Do not display sensitive answers just to make the page feel personalized. If the form collects health, financial, employment, or other private information, keep the confirmation generic and show only details necessary for the next step.
4. A clear contact option
Give people a way to get help if the confirmation does not match what they intended. Use a monitored email address, phone number, or support page—not a dead-end “contact us” label that leads to another confusing form.
If the visitor may need to refer to their submission, explain what to include when contacting you, such as the email address they used or a reference number. Avoid asking them to send sensitive information through an unsecured channel.
5. One relevant next action
A thank-you page can guide people forward, but the next action should fit the reason they came. A person who requested a consultation might be offered a calendar link. A donor might see a receipt explanation and a link to learn how funds are used. A newsletter subscriber might be told to confirm their email if your signup process requires it.
Keep the primary next step obvious. A row of unrelated buttons—follow us, browse products, read our blog, refer a friend—can distract from the confirmation and leave people unsure what matters.
Thank-you page examples for common forms
Contact or quote request
We’ve received your request.
Our team will review the details and get back to you within two business days. If your project has a fixed deadline, reply to the confirmation email with the date. For urgent questions, call us at [phone number] during business hours.
This works when the business can stand behind the response window. If inquiries are handled in order, say so. If the form asks for an uploaded brief or photos, make sure the page confirms whether those files arrived; see our guide to adding file uploads without creating friction.
Appointment or consultation request
Your appointment request is in.
This is a request, not a confirmed booking. We’ll email you to confirm a time within one business day. If you already selected a confirmed slot, add the date, time zone, location or video link, and any rescheduling instructions here.
Make the distinction between requested and confirmed explicit. Otherwise, someone may assume a tentative appointment is on the calendar.
Newsletter signup
Thanks for signing up.
If you need to confirm your email address, look for a message from [organization name] and follow the instructions. Once confirmed, you’ll receive [brief description of content] about [frequency, if known]. You can unsubscribe using the link in any email.
Only say that a confirmation email is coming if your system actually sends one. If the signup is complete immediately, say that instead. For promotional email, follow applicable rules for consent and unsubscribe requests. The FTC’s CAN-SPAM compliance guide explains requirements for commercial email in the United States.
Application or eligibility form
Your application has been received.
We’ll review submissions after the deadline of [date]. Applicants will receive an update by [date or timeframe]. Submitting this form does not guarantee a place. If you need to correct a response, contact [email] and include your name and application reference.
State what the submission does and does not mean. This is especially important when applicants are waiting on a decision or may need to meet another deadline.
Accessibility and mobile checks
Make the confirmation easy to find and understand. Use a descriptive page heading, concise text, readable contrast, and links with meaningful labels. If submission replaces the form with a success message without loading a new page, ensure assistive technology users are notified of the status change. The W3C explains how status messages should be exposed to assistive technologies.
Check that the page works on a phone, where people may be reading it in a hurry or switching between the page and email. Keep the main confirmation near the top, make phone numbers tappable, and avoid tiny secondary links. Our mobile form design checklist covers related checks for the form itself.
What not to put on a thank-you page
- Unverified promises: Do not guarantee a response time, approval, or delivery date unless the process supports it.
- Another request for the same information: Do not ask someone to repeat details they just submitted unless there is a clear reason.
- Unnecessary personal data: Avoid echoing sensitive answers or exposing information on a shared screen.
- Irrelevant promotions: A secondary offer is fine when it helps, but it should not compete with confirmation and next steps.
- Ambiguous status: “Thanks, we’ll be in touch” is not enough if the person needs to know whether a booking is confirmed or a request is pending.
Form thank-you page checklist
Before publishing, check each item against the actual process behind the form:
- Does the headline confirm exactly what was submitted?
- Is the submission received, pending review, or fully confirmed—and does the page say which?
- Are the next steps and timing accurate and achievable?
- Does the person need a reference number, preparation instructions, or a record of a date?
- Is there a monitored contact route for corrections or problems?
- Are email, consent, and unsubscribe instructions accurate for this form?
- Does the page avoid revealing sensitive answers?
- Can someone understand and use it with a keyboard, a screen reader, and a mobile device?
- Have you tested the full path, including what happens if a notification email is delayed or not received?
FAQ
Should every form redirect to a thank-you page?
No. A separate page is useful when you need room for next steps, reference details, or a clear record of completion. A short inline confirmation can work for a simple form, provided it is visible and accessible and does not leave the person wondering whether submission succeeded.
Should I include a confirmation number?
Include one when it helps someone track a request or contact your team about it. Make sure the number is stored with the submission and can be looked up by staff. A decorative number that your team cannot use adds little value.
Should the page say when someone will hear back?
Yes, if you can give a dependable estimate. Use business days when that is how your team works, and explain any relevant conditions. If you cannot predict timing, say what determines the next step and provide a way to ask about a delay.
Can I use the thank-you page to promote another offer?
You can, but keep it secondary and closely related to the visitor’s reason for submitting. First confirm the submission and explain what happens next. Avoid making a promotional action look like a required step.
What if the form submission fails?
Do not show a success message unless the submission was accepted. Provide a clear error state and tell the person whether their answers are still available or need to be entered again. For better recovery messages, see our guide to writing form error messages that help people fix mistakes.