Making Sure Enquiries Actually Arrive
Last updated:
The silent failure
WordPress sends mail through the server's basic mail function by default. Messages sent that way frequently fail authentication checks and are discarded by the recipient's provider without a bounce.
The form says thank you, the visitor believes they have contacted you, and nothing arrives. It is the most common and most expensive WordPress fault we find.
The fix, in two parts
- Send through authenticated SMTP — your mail provider, a transactional service, anything with proper authentication
- Log every submission in the database, so a lost email is not a lost enquiry
The second is the one that saves you when the first eventually fails anyway.
Get the sending domain right
- Send from an address on a domain you control
- Put the visitor's address in reply-to, not in from
- Make sure your domain's mail authentication records are correct
- Test delivery to the major providers, not just to yourself
Route leads somewhere owned
A shared inbox nobody owns is where enquiries go to wait. Route to a named person, or into your CRM, with a notification.
Automatic CRM creation removes the step where somebody has to remember to copy it across.
Test it monthly
Submit your own form once a month and confirm the notification arrives. It takes two minutes.
Mail configurations break silently — a provider changes something, a record expires — and the monthly test is how you find out in days rather than months.
Frequently asked questions
How do we know if we are losing enquiries?
Which SMTP service should we use?
What about spam on forms?
Should the visitor get a confirmation?
Enquiries that never arrived?
It is almost always the default mail function. Two hours fixes it permanently.