Does your website tell customers what happens after they click Send?

A customer sends an enquiry and sees “Thank you”. Has the message arrived? Is the appointment booked? Should they wait for a call or check their email? Your confirmation message should answer these questions while the customer is still on the page.

This check focuses on the words and next steps after a successful submission. For the wider delivery check, use our guide to testing a website contact form from start to finish.

1. Name the action that succeeded

Replace a vague “Done” with a short, accurate statement such as “Your enquiry has been received”. Use that wording only when your system has accepted the enquiry. A click on the Send button alone does not prove success.

Keep different stages separate. A request for an appointment is not necessarily a confirmed appointment. A request for a quote is not an accepted order. Ask the person who handles enquiries to check that the website describes the actual process.

The W3C guidance on form notifications recommends clear feedback on whether a submission succeeded. It also describes using a page heading and title to communicate the result.

2. Explain the next step in plain English

Write down who acts next, how they will contact the customer and the response time your business can support. Avoid copying a reply promise from another website. If your team does not work at weekends, a promise measured in hours may give the wrong impression.

For example, a fictional repair business might write:

Your repair enquiry has been received. Our team will review the details and email you within two working days. Your repair appointment is not booked yet; we will agree a time with you first.

This is example wording, not a Host Hobbit response-time promise. Use your own verified process and timing. If the next step is a phone call, say so. If the customer must do something else, make that action easy to find.

3. Give customers a way to follow up

Place a useful contact link below the main confirmation. If your system creates a reference number, show it and explain when to use it. Do not invent a reference that your team cannot look up.

The GOV.UK Design System confirmation-page pattern brings together the outcome, next steps, timings and contact details. These are useful prompts for a small-business page too; you do not need to copy its government branding.

If you send an acknowledgement email, check that its wording agrees with the page. Do not tell customers an email has been sent unless that action is part of the working process. Consider whether the page still makes sense to someone who returns to it later.

4. Keep the confirmation easy to notice

Read the message on a phone. It should be easy to find without searching through promotions or a long menu. Keep the outcome first and supporting detail below it. A tick icon can support the wording, but should not replace it.

Ask your developer to check how the result is announced to people using a screen reader, especially if the message appears without loading a new page. A visual check alone does not verify that behaviour.

A short review to do this week

• Choose one important enquiry journey and arrange a clearly labelled test with the team that receives it.
• Record the exact success message and any acknowledgement email.
• Ask a colleague what they think has happened and what they would do next.
• Compare their answer with your real process, then correct any gap in the wording.
• Repeat the check after the change and record who will keep the response-time wording up to date.

The aim is a clear handover: the customer understands the result, and your team can deliver the next step the page describes.

Want to discuss the enquiry journey on your website? Contact Hobbit Web Design and tell us which page you would like to improve.