Write a clear form confirmation message

Name the outcome the form can actually confirm

For an enquiry, confirm that the enquiry was received. Do not describe it as a booked appointment, approved application or completed purchase unless a separate process has genuinely produced that outcome. The distinction is especially important when the form asks for a preferred date that still needs a person's review.

W3C recommends clear feedback after submission, including success confirmation. Choose a short first sentence that can stand on its own. Put the task before promotional copy so a person looking quickly at the page can find the result.

Give the visitor one useful next step

GOV.UK's confirmation-page pattern includes what happens next, when to expect it and relevant contact information. For a simple enquiry, that may be a short explanation that your team will review the message. If there is nothing else to do, say so plainly rather than inventing an action to fill the page.

Avoid an optimistic response time copied from another organisation. Agree a timeframe with the people handling enquiries and consider busy periods. Where you publish a timeframe, explain it in the same terms the team uses, such as working days, and provide a maintained contact route for someone who has waited longer.

An optional next link should help with the submitted task. A guide about preparing project details may be useful after a quote enquiry. A large collection of unrelated offers competes with the information someone needs to feel confident the form worked.

Choose an inline message or a dedicated page

An inline confirmation suits a short result that needs only a sentence or two. A separate thank-you page gives you space for a heading, next-step instructions and useful links. Decide based on the content, rather than using a new page just because it looks more elaborate.

Keep a dedicated page understandable if someone visits it directly. A general thank-you page is not a private record of an individual transaction. Do not publish personal answers there or write instructions that depend on a reference number your form does not actually provide.

Accessible Forms can display its configured success message or send visitors to a published, publicly readable WordPress thank-you page. The inline message is plain text. Use page content when you need structured headings or links, and check that the destination remains available after normal site maintenance.

Verify the result after a real test submission

A preview helps you review the wording. A normal test submission checks the actual transition. Confirm that the result is visible, that keyboard focus reaches a useful place and that the visitor can understand whether another action is required. Test the mobile page too, where a long header can push the confirmation out of view.

Check the stored submission and email notification separately. Accessible Forms stores accepted entries before notification work; receiving a successful form result does not establish that a notification reached an inbox. Do not promise “We have emailed you a copy” unless you have configured that behaviour and verified it for this form.

Finish by reading the form introduction, submit button and confirmation in sequence. They should describe the same task and the same level of commitment. If the form starts as an enquiry, its final message should still describe an enquiry.

Using Accessible Forms

Write the success text under Email & confirmation, or choose a suitable published thank-you page, and test the complete submission flow.

In Free: Free includes editable success text, a confirmation preview and an optional WordPress thank-you-page destination. Stored entries and notification status can be reviewed separately.