The Enquiry You Never See: Contact Form Emails Going to Spam

A roofer in Thirsk told me his summer had gone oddly quiet. Nothing wrong with the phone, nothing wrong with the van. His website form was submitting properly, the thank you message appeared every time, and each of those enquiries was dropping into a junk folder he had never once opened. Contact form emails going to spam is the most expensive fault a small business website can have, because it does not look like a fault at all.

A broken form announces itself. Someone rings and says the page threw an error, or that the button did nothing. This one says nothing to anybody. The customer thinks they have been in touch. You think nobody has been in touch. Both of you are wrong, and the job goes to whoever answered.

Contact Form Emails Going to Spam Are Rarely the Form’s Fault

The form usually does its part. It collects the fields and hands them to a mail server. The failure happens in that handover, and it almost always comes down to who the email claims to be from.

Say your form sends the notification as if it came from the customer, sarah@gmail.com, when it was really sent by your web host’s server. Every filter on the route checks whether that server is allowed to send on behalf of gmail.com. It is not. Junk folder, or silently discarded before it ever reaches you.

Two DNS records fix most of this. SPF is a public list of the servers permitted to send email using your domain. DKIM is a signature proving the message was not altered on the way. Neither is difficult to add, both are free, and most owners have never been told they exist. That is form email deliverability in plain English.

Send From Your Own Domain and Reply to Theirs

The correction costs nothing. The notification should be sent from an address on your domain, something like website@yourbusiness.co.uk, with the customer’s address set as the reply-to. You still hit reply, it still reaches them. The difference is that the message is now honestly from a domain you control and can authenticate, which is the same reasoning behind using an email address on your own domain in the first place.

While you are in there, send a copy to a second address. A joiner in Easingwold I know has enquiries going to his own inbox and to his wife’s. It has caught two outages in a year.

The Two Minute Test You Should Run Monthly

Fill in your own contact form from your phone, using a personal email address, with a name obvious enough to spot: Test Tuesday works fine. Then check the inbox. Then check junk. If nothing has arrived within five minutes, you have found the problem before a customer did.

Do it monthly, not once. Hosts move mail servers, plugins update themselves, and DNS records get edited by whoever set up the new card machine. A form that worked in March proves nothing about August.

People search for “contact form not working” when the error is visible on screen. Nobody searches for the silent version, because nobody knows it is happening.

Every other page on your site is building an argument for getting in touch, which is why contact page conversion beats homepage polish. A form that takes the enquiry and then quietly loses it undoes all of that work in one step. Test it this week. Not clever, just done.