A person has sent an enquiry from your website. The button has stopped spinning, a new message appears, and they need to decide what to do next. A page that says only “Thank you” leaves several reasonable questions unanswered: did the request arrive, is anything booked, and should they expect a reply?
Plan this moment as part of the service. Start with what the website can truthfully confirm, then explain the next step your business actually follows. A polished confirmation page cannot make an unreliable process reliable, but it can describe the process clearly.
Name the step that has finished
Ask your developer what event makes the success message appear. Is the enquiry saved in the system that your team checks, or has the browser merely attempted to send it? The wording should match the confirmed event. Avoid showing success simply because someone pressed the button.
Submission, review and acceptance are different stages. A request for a visit does not reserve a time unless your booking process actually does that. A quote enquiry does not mean the business has agreed to a price or accepted the work. Make the distinction visible when a customer could reasonably misunderstand it.
The GOV.UK confirmation-page pattern recommends explaining completion, what happens next and when, and how to contact the service. It also suggests including a reference where one exists and helping people keep a record. These are useful design prompts for a business website, not a prescribed commercial workflow or Canadian legal guidance.
Write the next step from real business facts
Before drafting the page, speak to the person who handles enquiries. Find out which team receives them, how replies are usually sent, and whether the business has a response commitment it can maintain. Confirm what happens on weekends or during closures if those differences affect the wording.
Do not add “within 24 hours” because it sounds reassuring. If there is an agreed response window, state it accurately, including whether it means business days. If there is no reliable window, settle the internal process rather than inventing a promise for the design.
Also ask what customers should do if they need to correct something. A monitored contact route can be useful; asking everyone to submit the entire form again may create avoidable duplicate records. Give the route your team is prepared to handle, and explain what identifying information it needs without requesting unnecessary personal details.
Use a fictional example to check the meaning
Imagine a garden-maintenance business whose team reviews requests before arranging visits. The following example is invented. It describes neither a ZXP client nor a tested improvement, and its operational facts would need confirmation before any business used it.
A suitable heading might be “Your visit request has been received.” The supporting message could say, “Our team will review your request and contact you by email about availability. No visit has been booked yet.” That wording assumes the system has confirmed receipt and that email is genuinely the next contact method.
If the business can support a specific reply window, it can add that separately. If it issues a usable request reference, show it and explain when to mention it. Do not generate a decorative reference that staff cannot use to find the enquiry.
Now read the page as the customer. Could you mistake it for a booking confirmation? Would you wait for an email or turn up somewhere? Does it tell you to complete another task? These questions expose ambiguity more directly than asking whether the page feels friendly.
Keep the useful information ahead of promotion
The customer has just completed a task. Give the result and next step the most prominent positions. A newsletter invitation or another service offer should not make it hard to see whether the enquiry worked.
Choose any additional link around a likely next need. For the fictional garden business, a page explaining how visits are arranged might be useful if that information exists and is current. A long set of unrelated offers adds decisions at a moment when the customer mainly needs certainty.
Review the confirmation email alongside the website message if one is sent. Their descriptions of the request, next step and response window should agree. Only say an email has been sent when that statement matches the system's confirmed behaviour; generating a message and knowing it reached an inbox are different things.
Make the result perceivable
A new page and an inline success message need different implementation checks. Ask a reviewer to complete the enquiry with a keyboard and screen reader, then explain what they heard and where focus went. Do the same on a narrow screen and at increased zoom.
W3C's Status Messages guidance addresses status updates that occur without a change of context. Its examples include a success message added to an existing form. Such information needs to be available to assistive technology, not merely displayed visually. A full page navigation is a different case, so the developer should test the actual pattern used. This check alone does not establish accessibility conformance.
Include failure and uncertainty in the brief
Test the successful route, but also ask what happens when the service cannot confirm the outcome. The page should not claim that an enquiry failed or succeeded when the system does not know. Agree an honest explanation and a practical way for the customer to check before retrying.
For a known input problem, keep the correction route distinct from confirmation. The GOV.UK error-summary component demonstrates a summary linked to the affected fields, alongside messages at those fields. That is a useful reference for reviewing recovery, not a reason to display success before the errors are resolved.
Finally, revisit the confirmation route after changes to forms, enquiry tools or staffing arrangements. Check that the team's real process still matches the public explanation. To discuss a website project with ZXP, bring the current submission message and a description of what your team does after an enquiry arrives. Those two pieces are a practical starting point for deciding what the customer should see next.
Sources & references
- 01Confirmation pages
GOV.UK Design System
- 02Understanding Success Criterion 4.1.3: Status Messages
W3C Web Accessibility Initiative
- 03Error summary
GOV.UK Design System
A perspective from the ZXP team.
Designed to help you ask better questions and take a clearer next step.



