A contact form can look perfect and still lose business. The page loads, the button works, the thank-you message appears — and the enquiry lands in a spam folder, an old inbox or a CRM nobody checks.
Checking the whole journey takes less than an hour. Doing it regularly is what turns “I think the form works” into “I know enquiries reach us”.
Map the journey first.
Before testing, write down where an enquiry is supposed to go. For most business websites the path looks something like this:
- A visitor fills in the form on the website.
- The website or form service sends a notification email, stores the entry, or both.
- The message arrives in a mailbox, a shared inbox or a CRM.
- A named person sees it and replies.
Each arrow is a place where things can break: an email address that changed, a mail setting on the server, a spam filter, an automation that stopped running, a person who left the company.
Send a recognisable test.
Use data nobody could mistake for a real customer: your own name, a mailbox you control and a subject such as “TEST – website form check”. Avoid anything that could trigger a real process, like booking a paid slot or starting an order.
Then follow the message through every step. Did the notification arrive? How long did it take? Did it land in the inbox or spam? Did the CRM record appear with the right fields? Who would have seen it first?
Common reasons enquiries go missing.
- Email sent without proper authentication. Messages sent directly from a web server often fail SPF or DKIM checks and end up in spam. Sending through a proper email service or SMTP connection usually fixes this.
- An outdated recipient. The form still sends to a former employee or an old shared address.
- A broken integration. A CRM connection or automation stopped after a password change, a plan change or an API update.
- Spam protection that is too strict. Real enquiries are blocked or quietly filtered along with bots.
- No one owns the inbox. Everything technically works, but the messages sit unread.
Keep a copy on the website where possible.
If your form tool can store entries as well as emailing them, switch that on. A stored copy means a delivery problem delays a reply instead of losing the enquiry entirely. Agree how long entries are kept, and mention it in your privacy notice.
Make it a routine, not a one-off.
Forms rarely break on the day they are built. They break after a plugin update, a new CRM, a domain change or a team change. A short monthly test catches most of these. It also makes sense to test straight after any change to the site, the email setup or the tools that receive enquiries.
- Once a month: send one test through each important form and confirm it reached the right person.
- After changes: repeat the test the same day.
- Every few months: check that the recipients are still the right people.
An automated check can confirm that a form loads and shows its confirmation. Inbox and CRM delivery need an agreed test setup, so it helps to decide who checks what. If you’d like someone to look after this for you, tell us about your website.
