Website contact form not sending emails? How to trace where the enquiry went

Your contact form says "Thank you, your message has been sent". Nobody can find the enquiry. Or it turns up a day later in someone's junk folder.

Before anyone changes the form, the website or your email settings, find out where the enquiry stopped. Otherwise you might fix something that was working and leave the real problem in place.

This guide is for owners and office leads in small service businesses. It splits an enquiry's journey into four stages, shows you how to check each one with a single marked test, and explains what to give your web supplier or email administrator. It includes a form trace card you can copy.

A success message proves less than it seems

A success message tells the visitor that the website responded to their click. It does not prove that anyone received the enquiry.

Between the visitor pressing "Send" and a person replying, an enquiry passes through four separate stages. Each one can fail on its own:

1. Accepted. The website recorded the submission.
2. Sent. The website tried to send a notification, from one address to another.
3. Received. The notification arrived in the agreed inbox or queue.
4. Owned. A named person found it and took on the next step.

Keep the evidence for each stage separate. A pass at one stage tells you nothing about the next. If the website accepted the enquiry, that does not mean an email was sent. If an email arrived, that does not mean anyone saw it.

Before you start

• Stop resubmitting. Each extra attempt, real or test, adds another entry to sort through and makes it harder to tell what happened.
• Change one thing at a time. If several settings change at once, you will not know which change fixed the problem, or which one broke something else.
• Use invented details. Use a clearly marked test message and an email address or phone number you control. Never use a real customer's details.
• Know who to involve. That usually means whoever manages the website, whoever manages your email, and the person who should be receiving enquiries. In a small business, two of those may be the same person.

Stage 1: did the website accept the submission?

Some website platforms and form tools keep a record of each submission, often called entries or submissions. Others simply send an email and keep nothing. Find out which kind you have. If you are not sure, ask your web supplier.

• Your test appears in the entries. Stage 1 has passed. The problem is further along.
• The platform keeps entries, but your test is not there. The problem is most likely on the website itself, for example in the form's settings. This is one for your web supplier.
• The platform keeps no entries. Record "not available". Don't mark it as a pass. Without a record, you can't tell whether a missing enquiry was ever accepted.

Also note exactly what the visitor saw after pressing "Send": a success message, an error, or nothing at all.

If your form does store entries, those entries are copies of people's personal details. Decide who can see them and how long you keep them.

Stage 2: did the website try to send a notification?

The next question is whether the website tried to send an email about the enquiry, and to whom. Ask your web supplier:

• Is a notification set up for this form?
• Which address or addresses does it go to?
• Which address does it come from?
• Is there a log showing that a message was sent? Some platforms and sending services keep one.
• Did a bounce or error message come back?

When you see the actual "to" address, check it letter by letter. It might contain a typo. It might belong to someone who has left, or to a mailbox that has since been renamed or moved. It is also possible the notification was switched off during an update.

Stage 3: did it arrive where it should?

Stage 3 passes only if the notification arrived in the agreed destination: the inbox, folder or queue your team actually watches. To find out where it went, search for your test marker across the whole mailbox, and check:

• junk or spam folders
• any quarantine your email administrator uses for suspicious messages
• rules or filters that move, forward or delete messages
• other folders, shared mailboxes or old addresses that forward somewhere else
• the inbox of anyone else the notification is copied to

If you find it somewhere nobody watches, such as junk, record exactly where. The notification was delivered, but not to the agreed destination, so stage 3 is a fail.

Where email authentication fits

Email authentication is one possible reason a notification goes missing or lands in junk. It is not the only one, and you shouldn't assume it's the cause before you've checked the other stages.

Here is the short version:

• Email does not check who the sender is by design. Microsoft's explanation of email authentication notes that standard internet email makes no effort to confirm that a sender is who they claim to be.
• A message has more than one sender address. One is used behind the scenes while email servers pass the message along, and is where bounce messages go. The other is the "From" address you see in your email program. They don't have to match.
• Receiving services run checks. SPF and DKIM are two standard checks. A third, DMARC, asks whether a check that passed relates to the same domain as the visible "From" address. Google's DMARC set-up guide says a message passes DMARC only if SPF or DKIM passes and also aligns with that domain.

Why does this matter for a form? Some forms put the visitor's own email address in the "From" field, so you can press Reply. The notification is still sent by your website's sending service, which may not be authorised to send for the visitor's domain. If neither SPF nor DKIM passes for a domain that aligns with that "From" address, the notification can fail DMARC. What happens next depends on the receiving service and on the policies involved.

Gmail is one example. Google's email sender guidelines set requirements for anyone sending to personal Gmail accounts, including SPF or DKIM authentication. They say messages that aren't authenticated might be marked as spam or rejected. They also say senders shouldn't impersonate other domains or senders without permission. That is Google's policy for personal Gmail accounts, not a rule for all email.

Authentication settings live in your domain's DNS records, and a wrong change there can affect all of your email, not just the form. Don't edit them yourself unless you know exactly what you're doing. Instead, ask your web supplier or email administrator:

• Which "From" address does the form notification use?
• Is the service sending the notification authenticated for that address's domain?
• Could the notification come from an address on your own domain instead, with the visitor's address used only so you can reply? Ask them to confirm what suits your set-up.

Even well-authenticated email is not guaranteed to arrive. Microsoft says so plainly for its own service. Authentication removes one reason a message might be treated as suspicious. It does not promise delivery.

Stage 4: did a named person take it on?

An enquiry that arrives in an inbox nobody watches has still been missed. Record who found your test, and whether they accepted the next step. If nobody did, the trace has found the gap. The website is working, but nobody owns the enquiry.

Who should own new enquiries, who covers when they're away, and how quickly you reply are covered in our guide to managing customer enquiries. The trace only needs to record whether ownership was accepted, by whom, and when.

Run one marked test and fill in the trace card

Run a single test enquiry that you can follow through all four stages. Our website redesign checklist includes a step-by-step manual enquiry test you can use. The same steps work on a live site that is already having problems. The points that matter most here:

• Agree a time with the person who receives enquiries, so they know to look.
• Put a unique marker in the message, such as "TEST — form trace 1".
• Note the time you sent it, including the time zone.
• If you can't tell whether it sent, check the destination before you try again.

When we tested our own website, we checked both whether the enquiry arrived and whether the confirmation was clear on mobile, and we corrected the mobile confirmation as part of that check.

How to use the trace card

1. Copy the blank card into a document or spreadsheet. Use one card for each test.
2. Fill in the details as you go, not afterwards from memory.
3. Give each stage its own result: pass, fail or unknown. Use "unknown" only when there is no evidence either way. If a stage clearly hadn't happened when you checked, for example nobody had accepted the enquiry, mark it "fail" and note the time you checked.
4. Never let one "pass" stand for the whole journey. If stage 3 is unknown, the enquiry has not passed, even if stage 1 did.
5. Finish with the next action and who owns it.

In this invented example, the website accepted the enquiry and sent the notification. It reached the enquiries mailbox, but landed in junk rather than the monitored inbox, so stage 3 fails. Nobody had taken it on by the time of the check, so stage 4 fails too. The trace points to the people who can look at why it went to junk.

What to hand to your supplier or email administrator

Send the evidence, not just "the form's broken". Include:

• the completed trace card
• the exact time and time zone of the test, and the test marker
• the address of the page the form is on
• a screenshot of what the visitor saw
• any bounce or error message, forwarded as it is
• what you have already checked, so nobody repeats it

Match each stage to the right person. Stages 1 and 2 usually sit with whoever manages the website. Stage 3 usually sits with whoever manages your email. Stage 4 is yours.

Never put passwords in the trace card or in an email. If someone needs access, give it through their own account.

Test again after any change

Once a fix is in place, run the same test again and fill in a new card. The old card shows what was wrong. The new one shows whether the fix worked, stage by stage. Repeat the test whenever you change your website, your email set-up or who receives enquiries.

ScalePass helps service businesses connect their website, enquiries and everyday work. If you would like help tracing where your form's enquiries go and putting the route right, see how we approach websites.

In short

A success message does not prove anyone received the enquiry. Trace one marked test through four stages: accepted, sent, received and owned. Record the evidence for each stage separately, and mark it pass, fail or unknown. Treat email authentication as one possible cause, not the answer. Give your supplier or email administrator the completed card, leave DNS changes to them, and test again after every fix.