If a contact form says "sent" but no email arrives, the problem could be in form processing, message sending or the receiving email service's filtering. A thank-you message in the browser does not, on its own, prove that the email arrived.
Narrow down the problem step by step instead of changing everything at once.
First test: what actually happens?
Send a test message yourself and record:
- the time of the test
- the email address used
- what the form displayed after submission
- whether any automatic confirmation arrived
- whether the message reached the business inbox
- whether it appeared in spam
If you have another email address available, run a second test with that too.
This gives you much more information than simply saying "the form does not work".
The symptom tells you where to start
| Observation | Possible cause | Next check |
|---|---|---|
| The submit button does nothing | The form interface or script is not working | Test on another device and browser |
| The form shows an error | Form processing fails | Check the technical error and form service |
| A thank-you message appears, but no email | The message is not sent or gets filtered along the way | Check the recipient, spam and sending service |
| Messages arrive only sometimes | Delivery problem or filtering | Check sending logs and email authentication |
| The message arrives at the wrong address | The recipient is configured incorrectly | Correct the destination address |
| The form works but nobody replies | An internal business process | Assign a responsible person and follow-up process |
Check spam before a technical overhaul
It sounds obvious, but some form messages land in spam or a separate filtered folder.
Check:
- spam
- quarantine, if the business email service has it
- any email rules
- that the receiving address is still in use
If the message is in spam, the form may have sent it correctly. The issue is then deliverability, rather than the form fields themselves.
Why can email authentication affect form messages?
When a website sends email on behalf of the business's domain, the receiving service may check whether the sender is genuine.
Common terms include:
- SPF (Sender Policy Framework), which specifies which servers may send on behalf of the domain
- DKIM (DomainKeys Identified Mail), which adds a verifiable digital signature to the message
- DMARC (Domain-based Message Authentication, Reporting and Conformance), which tells the recipient how to treat a message that fails authentication
Gmail recommends setting up email authentication because unauthenticated messages may go to spam or be rejected.
Business owners do not need to build these settings themselves. But whoever investigates the form problem must understand that "the form sent it" and "the message reached the inbox" are two different stages.
Do not change email DNS settings blindly
DNS (Domain Name System) also contains records related to email.
If a form message does not arrive, do not start removing or adding MX, SPF, DKIM or DMARC records by guesswork. A wrong change could affect the business's regular email too.
First establish which system sends the form message and which email service receives it.
What should you ask the website provider to check?
A useful technical check answers these questions:
- did the website receive the form submission
- did the form service or server accept the message
- which address was the message sent to
- did sending produce an error code
- is the sender's domain correctly authenticated
- does the receiving email service show a spam or quarantine flag
You do not need access to the entire technical implementation. You need to know where the chain breaks.
What if the form receives lots of spam?
That is a different problem.
Spam can be reduced with measures such as:
- technical bot detection
- invisible trap fields
- submission limits
- form field design
CAPTCHA (Completely Automated Public Turing test to tell Computers and Humans Apart) is one familiar way to distinguish people from automated traffic, but a visible CAPTCHA is not the only option.
The solution should reduce spam without making it unnecessarily difficult for a real customer to get in touch.
How does GC's website service handle the form?
GC's service includes one standard contact form. The ongoing technical service includes monitoring the contact form's operation, troubleshooting and fixing technical faults on the website.
This is separate from faults in the customer's email service or incorrect user settings, but narrowing down the problem is part of checking the form sensibly.
To understand the whole chain first, read how a website contact form works. If the form works but you still receive no enquiries, read why your website is not generating enquiries.
Sources: Gmail Help, Email sender guidelines. Cloudflare Email Service, Email authentication and Email deliverability. GC's terms of service.