The auto-reply is usually the last thing switched on when a form is built, and it usually goes out with the default wording — one line saying the enquiry has been received.
Look at where that message sits, though. The customer has just decided to trust you, handed over a contact detail, and started waiting. The first document to arrive bearing your name is this one. That is far too good a position to spend on a receipt.
Three jobs this message has to do
First, confirm arrival. When nothing happens after a form is submitted, people either submit again or go and look elsewhere. The mail landing is itself the signal that it worked.
Second, set expectations by saying when they will hear back. What matters here is not a fast promise but a keepable one. Write “within one working day” and that becomes your operating standard; miss it and the very first message you sent becomes the first crack in the relationship.
Third, offer a next step: one line about what is worth reading while they wait, or what to prepare so the first conversation moves faster. For us, that role belongs to the process page — the wait becomes preparation rather than dead time.
Writing the thing
Write the subject line assuming it will be searched for later. Your company name and the topic beat “Auto-reply” or “Thank you” when someone digs through their inbox three weeks on.
In the first sentence, reflect back what they sent. Including a single value captured by the form — their name, or the type of enquiry — is enough to stop the automation reading as indifference.
Send it from a person. Use a named sender alongside the company name, and sign off with a contact route that genuinely reaches someone.
What to avoid
A no-reply address is the most common mistake. Hitting reply is an entirely natural thing to do, and blocking it amounts to telling a customer to come back to the website to speak to you. Send from a mailbox that accepts replies and the conversation simply continues.
Avoid attaching a long company introduction as well. They have just read your site. What this message owes them is not an introduction but an account of what is happening now.
Finally, do not slip marketing consent into the auto-reply. Treating an enquiry as agreement to receive a newsletter creates disputes later and runs against the data principles in the next part but one.
Turning customer communication into a repeatable procedure is covered further in the development workflow archive, and the sequence we follow after an enquiry arrives is written out step by step on our optimization program page.
Next part
Once a form works well, less welcome visitors find it too. The next part is spam — and there are several ways to reduce it without the conversion cost of a CAPTCHA.