Tie the message to the completed action
Distinguish an enquiry received from a booking confirmed or a payment accepted. The subject and opening sentence should name that state clearly. Include a reference number only if it supports follow-up, and avoid sensitive details in the subject.
The on-page message should tell the same story as the email. The contact form guide covers entry and initial confirmation.
- Actual state named clearly.
- Page and email consistent.
- Precise subject without sensitive data.
Give the next step and a contact
State a response time the team can actually meet, documents to prepare and a way to report a mistake. If no action is required, say so. For bookings, repeat place, time and relevant conditions with the correct time zone.
Avoid a no-reply sender when people may need help. The enquiry follow-up guide helps assign responsibility after submission.
- Concrete next step stated.
- Realistic response time.
- Usable return contact.
Write for every reader
Use clear text, simple structure and descriptive links. Check reading without images, on a phone and with common assistive tools. Do not bury essential information in a button or picture.
The W3C recommends clearly confirming a submission result. Apply that principle to the page and email, with reviewed translations for each published language.
- Essential information in text.
- Descriptive links.
- Language versions checked.
Test delivery and failure
Send complete trials using valid addresses, mistyped input and repeated submissions. Check delivery time, display in several clients, broken links and duplicates. A thank-you page alone does not prove the email arrived.
Plan what the visitor sees if email delivery fails after the request was recorded. Check that the team receives and handles the enquiry without exposing private data or connection settings publicly.
- Delivery and display tested.
- Duplicates and faults handled.
- Team follow-up verified.