A customer says they sent an enquiry yesterday. Your website displayed a success message, but your team has no record of receiving the email. Before changing settings, follow one test enquiry through the systems involved.
What does the success message actually confirm?
A form submission has several stages. The website validates the fields, passes the notification to a sending service, and that service attempts delivery. The receiving system then processes the message before it appears in a mailbox. A problem can occur at any stage.
The meaning of “sent” depends on the form and its integration. Some sites show success once the submission is saved or queued. Others wait for a sending service to accept it. Neither confirms that somebody has received and read the notification.
In WordPress, a successful wp_mail() result means the configured method processed the request without reporting an error. Delivery still needs to be checked further along the route.
Reference guidance from WordPress on wp_mail().
Start with one traceable test enquiry
Consider a fictional business whose contact form shows a thank-you message, but whose office team cannot find the enquiry. The useful starting point is a fresh test that everyone can identify.
- Submit through the public form as a visitor would, including any consent and verification steps.
- Use a unique reference such as Enquiry test 18 November 10.30 in the message. Use test details you control.
- Record the exact time and timezone, form URL, recipient and any submission reference displayed.
- Capture the confirmation or error message, then follow that same submission through the available logs.
If the form stores entries, check for the reference there. An entry with no notification points you towards notification rules, queues or sending. If it is absent, check validation, spam handling and whether that form saves entries at all. Notification recipients may also depend on the selected service, location or other answers.
Follow the handoff to the sending service
Look for the test in the form’s notification log, the application’s mail log and the SMTP or transactional provider’s activity. Record the recipient, timestamp, provider reference and any error. If background jobs send the messages, check that the queue is being processed.
A connection failure, expired credential, sending restriction or invalid recipient may prevent the provider accepting the message. If the provider accepted it, inspect its subsequent delivery, deferral or bounce event. An initial acceptance and a later receiving-server rejection can both occur for the same enquiry.
“Delivered” in a sending provider’s dashboard commonly records acceptance by the receiving mail system. Check that provider’s definition, then investigate the recipient side if the message is still missing. Capture the message ID where available so support can match records across systems.
For WordPress, review the configured mail integration and whether the form uses it. For a static website, review its form handler and sending provider. Installing an SMTP plugin is only relevant if it addresses how that application sends mail.
Use your domain as the sender and the visitor in Reply-To
A common configuration sends the notification “From” whichever address the visitor typed into the form. If a customer enters a Gmail or Outlook address, your website then tries to send a message claiming to come from that domain.
Use a stable sender address on a domain you control and have authorised with your sending provider. Put the visitor’s validated email address in Reply-To so the team can reply to the enquiry directly.
A fictional configuration
- From — Website enquiries <[email protected]>
- To — [email protected]
- Reply-To — the visitor’s validated address
The domain and addresses above are examples. The sending service must be configured to send for the actual domain you use.
Send another test after the change and verify where a reply goes. Confirm that the form validates submitted addresses and uses its supported mail fields, including when optional fields are empty.
Reference guidance from Contact Form 7 on mail setup and Reply-To.
Check SPF, DKIM and DMARC for the actual sending route
Authentication helps the recipient assess whether the sending system is authorised. Your website may use a different sending service from the one used by staff mailboxes, even when both use the same domain.
- SPF checks the sending server against the policy for the envelope-sender domain used during delivery.
- DKIM uses a domain signature to let the recipient verify the signed message content.
- DMARC checks whether a passing SPF or DKIM result aligns with the visible From domain. Either aligned method can satisfy DMARC.
Inspect the actual test message and provider setup before changing DNS. Follow the sending provider’s domain-verification instructions and coordinate changes with whoever manages the domain. Your staff email, website and other legitimate senders all need consideration.
Successful authentication supports delivery, while filtering can also consider reputation, content and recipient policies. Review a failed message’s recorded results alongside the delivery response. Changing the incoming MX records is a separate decision that needs evidence about inbound routing.
Reference guidance from Microsoft on SPF, DKIM alignment and DMARC.
Trace the message through Microsoft 365
Ask the recipient to search for the unique reference across their mailbox, including Junk Email and Deleted Items. If the destination is a shared mailbox, check that mailbox directly and confirm the notification’s exact recipient.
An authorised Microsoft 365 administrator can use Exchange Online message trace to follow the message through the organisation. Provide the sender, recipient, timestamp and message ID when available. Review the recorded events to understand whether Microsoft received, deferred, rejected, quarantined or delivered it.
Check Microsoft Defender quarantine when indicated. Access and release options depend on permissions and policy, so the mailbox owner may need help from an administrator.
If the trace records delivery, investigate inbox rules, forwarding, other folders and any later handling. If the trace has no matching result, confirm the search details and reporting availability, then compare with the sender’s logs and any mail gateway in front of Microsoft 365.
Ask IT to assess the specific message and any proposed policy change. Broadly allowing a sender or turning off filtering can expose the mailbox to other messages using the same identity.
Reference guidance from Microsoft on Exchange Online message trace and managing quarantined messages.
An enquiry checklist for launches and migrations
Test forms after a rebuild, hosting move, DNS change or replacement email integration. A functioning homepage says little about the enquiry route.
- Check every public form and each conditional recipient route.
- Confirm the real production recipient, sender and Reply-To settings.
- Submit with desktop and mobile browsers through the normal verification flow.
- Follow the test through the application, sending provider and destination mailbox.
- Check autoresponders separately, including the address to which they are sent.
- Check that attachments arrive where supported and replies reach the intended address.
- Review submission storage, who can access it and how long it is retained.
- Agree who receives delivery alerts and how failed notifications are investigated.
Where appropriate, a protected submission record provides another way to recover an enquiry if its notification fails. Choose storage and retention around the information collected, and keep it consistent with your privacy information.
What to send your support team
Provide the form URL, test reference, exact time and timezone, intended recipient and confirmation message. Add the provider’s message ID or error if you have it, and explain whether other forms or recipients are affected.
Use a secure support route for logs or message samples containing personal information. Your support team can then compare the same test across the website, sending service and recipient system and identify where the next action belongs.
Spidrweb can help investigate form delivery through Website Rescue, review DNS and email authentication, and work through Microsoft 365 delivery and mailbox issues.
Missing website enquiries?
Tell us what you have tested and where the message stops. We can help investigate the website, sending setup and mailbox delivery.
Talk to Spidrweb ↗
