A customer says they sent a quote request through our website, but we never got it. Why?
Usually the form worked and the email it sends didn't arrive. The thank-you message only means your website accepted the submission. The notification is a separate email, often sent from the web server in a way your mail system can't verify as yours, or made to look like it came from the visitor's own address, so it lands in spam, sits in quarantine or gets refused. Test it from an outside address, then check the inbox, spam, quarantine and the form's own entry list, about half an hour in all.
What it usually means
A form submission is two events, and the visitor only sees the first. The website accepts what was typed, maybe saves it, and shows the thank-you. Then it sends an email about it, which your mail system has to accept like any other message from outside. WordPress's developer reference for its mail function says a successful result doesn't automatically mean the email was received. Hardly anyone sets this up to fail. The form was tested at launch, then things around it changed: company email moved to Microsoft 365 or Google Workspace, someone rewrote the DNS records, the person the form emails left. Nothing alerts anyone when the notifications stop.
There are three common causes, and they're checkable: mail sent straight from the web server, a form that sends from the visitor's own address, and an address nobody checks anymore. The cards below set out what each one looks like and what the documentation says about it.
Rule out two other problems before blaming email. Form plugins run their own spam checks, and a real buyer can trip one. Gravity Forms' documentation says a flagged submission is still saved, under a Spam link above the entries list, but its notifications aren't processed, so no email goes out. That's the risk covered in what spam protection can break. And if the request isn't in the entries or the spam view, it never got through the form: a broken page, or an upload over the size limit. Timing is a clue too. Requests vanishing some of the time points to filtering that judges each message, or to a form that sends as the visitor, which fails for some buyers' email providers and not others. All of the time points to the sending setup, or to an address that no longer exists.
- On the websiteThe form accepts the request
The thank-you shows. A copy is saved only if the form tool keeps entries.
- On the web serverThe site sends a notification
Sent by the server or through a mail service, from an address someone chose at launch.
- At your mail systemYour mail system checks it
Unverified mail claiming your domain can go to spam, quarantine or be refused.
- In the inboxSomeone reads it
Only if the address it goes to belongs to a person who still checks it.
WordPress sends through PHP's mail function from wordpress@ plus your domain, which WPForms says some servers don't support. If your records only authorize your email provider, it fails the check. After an email move, cPanel's Local Mail Exchanger setting can leave it in a mailbox on the web server.
The From address is the buyer's own, so hitting reply reaches them. WPForms says the From address should be on your website's domain, and yahoo.com publishes a DMARC policy of reject for its own domain, asking receiving servers to refuse mail with a yahoo.com sender that doesn't pass the check.
The form emails an address that no longer belongs to anyone who checks it, such as a person who has since left.
What it costs while it stays this way
The website shows no error to anyone. The buyer saw thank you and assumes you have it. Any bounce goes back to the sending side, usually an address on the web server that hardly anyone reads. The only signal is the one in the question: a customer who mentions it, and most don't. A buyer often sends the same job out to two or three suppliers in parallel, and the first useful reply often becomes the reference point for the rest, which is how the first reply shapes the comparison.
On some setups the email is the only copy. Contact Form 7 doesn't store submitted messages, according to the WordPress.org listing for Flamingo, the storage plugin built for it, and WPForms' documentation says WPForms Lite doesn't save entries to your WordPress database. On those setups a refused notification takes the request with it. More than once on calls this year, owners have mentioned a form that had quietly stopped sending, or quote requests going to the wrong person.
How to confirm it yourself
- Step 1Send a test request from an outside address
From a personal Gmail account, fill in your quote form the way a buyer would, with a message you'll recognize, such as TEST quote request plus today's date, and a file if the form takes drawings. Write down the time. If you have a Yahoo or Outlook.com address, send a second test from it, because a form that sends as the visitor can fail for one provider and not another. Watch the test account for any confirmation email too.
- Step 2Look in the inbox, then spam, then quarantine
While you wait, run steps 4 and 6, which don't need the test to arrive. After 15 minutes, check the inbox the form should reach and its Junk or Spam folder (in Gmail, More, then Spam, in the left menu). On Microsoft 365, quarantine is separate from Junk: open security.microsoft.com/quarantine and look on the Email tab. Per Microsoft's documentation, users can release spam there, high-confidence phishing is admin-only, and messages are deleted after the Expires date. Note where each test landed, or that it landed nowhere.
- Step 3Admin step: ask your mail system what it did with the test
This is the one step that needs whoever runs your email; the others stand without it. On Microsoft 365: the Exchange admin center at admin.exchange.microsoft.com, then Mail flow, then Message trace, searching the last two days by subject or sender. It needs the Exchange Administrator role or Organization Management, and reports statuses including Delivered, Failed, Quarantined and Filtered as spam. On Google Workspace: the Admin console, then Menu, Reporting, Email Log Search, which needs the Gmail Settings administrator privilege, covers the past 30 days and shows whether a message was marked as spam. No record at all means the message never reached your mail system. Ask your web host whether the site's server still delivers your domain's mail locally; in cPanel that's Email, then Email Routing, which should be set to Remote Mail Exchanger, or Automatically Detect, once your email lives with Microsoft 365 or Google Workspace.
- Step 4Read the form's notification settings
This works even if nothing arrived. In the WordPress admin, open the form's notifications: in WPForms, the form builder's Settings, then Notifications; in Gravity Forms, Forms, then the form, then Settings, then Notifications. Read Send To. Does every address belong to someone who still works here and checks it, and is it spelled right? WPForms' troubleshooting page names misspelled addresses and missing commas as causes. Then read the From Email. If it's filled from the visitor's email field rather than a fixed address on your domain, the form is sending as the visitor.
- Step 5Check whose domain the email was sent as
Open the confirmation in your Gmail test account, or a notification that reached Gmail, and click the Down arrow below the sender's name. Google's help says an authenticated message shows mailed-by and signed-by lines with the sending domain, and a question mark next to the sender's name means it isn't authenticated. At least the signed-by domain should be your own; mailed-by may show a sending service. If neither line shows your domain, or mailed-by shows your hosting company's server, the site is sending as someone else.
- Step 6Check whether the form kept its own copy
In the WordPress admin, look for an Entries screen under the form plugin's menu, and its spam view. In Gravity Forms it's Forms, then Entries, with a Spam link above the list. If your test is in Spam, the form's own check caught it and sent nothing: mark it Not Spam, resend it with the bulk action Resend Notifications, and ask the developer what flagged it. If it's in the entries but not in any inbox, the problem is sending. If it's nowhere, the problem is the form. If there's no entry list at all, the email is the only copy you have.
What you'll hear about it
These come from web developers, hosting support and IT providers. Each one is partly true.
“The form's working. We tested it.”
Usually true of the form, and silent on the email. Ask when it was tested, from which address, and which inbox it reached. A test at launch, or one sent to the developer's own inbox, says nothing about whether your mail system accepts the notification today.
“It's going to spam. Just add the sender to your safe list.”
That can rescue one mailbox and leaves the cause in place. It does nothing for the buyer's confirmation email or a colleague's inbox.
“That's an email problem, not a website problem.”
Half right. The records that authorize senders live in your domain's DNS, and the filtering belongs to whoever runs your email. But the From address and the way the site sends are website settings. The fix needs both people in one thread, which the message below sets up.
“We'll install an SMTP plugin.”
Usually the right direction, and what WPForms' documentation recommends. It only works if the plugin sends through an account your domain authorizes, such as Microsoft 365, Google Workspace or a sending service, with the From address on your domain. Ask which service it will use, and whether DKIM is set up for your domain on it.
| Setting | What healthy looks like | Where it's set |
|---|---|---|
| From addressWebsite | An address on your own domain, such as website@ | The form's notification settings |
| Reply addressWebsite | The visitor, so hitting reply reaches the buyer | The form's notification settings |
| Sending routeWebsite | A mail service your domain authorizes, through an SMTP plugin | The site's mail plugin |
| SPF, DKIM, DMARCEmail and DNS | SPF lists that service, DKIM signs for your domain on it, DMARC is published | Your domain's DNS |
| Mail routingWeb host | Remote Mail Exchanger once email lives with Microsoft 365 or Google Workspace | cPanel, Email, then Email Routing |
| Saved copyWebsite | Every submission in the form's entry list or your CRM | The form tool or the CRM |
| RecipientsYou | Two named people who still check that inbox | The form's notification settings |
What actually fixes it
A healthy form sends its notification through a mail service your domain authorizes, from an address on your own domain such as website@, with the reply address set to the visitor so hitting reply still reaches the buyer. Your SPF record lists that service, DKIM signs for your domain on it, and a DMARC record is published, so the domain in the From line lines up with SPF or DKIM, the test Google's sender guidelines set for bulk senders. Those records live in DNS, so first confirm the company controls the account they sit in, the question behind an agency holding your domain.
Then make sure no request depends on one email. Save every submission somewhere a second person can see: the form tool's entry list, switched on and kept, or a record in your CRM, the first thing worth doing in a CRM website integration. Send the notification to two named people. And add a delivery test to routine website maintenance: one request from an outside address each month, and after any change to email, DNS, hosting or the form, followed all the way to the inbox. It's the only alarm this problem has. Every few months, let it double as the response-time test, with a real drawing and a name your team won't recognize.
Recover what you can. If the form keeps entries, export the last few months and match them against what your team answered; a late reply beats none. If it doesn't, message trace in Microsoft 365 reaches back 90 days, though past 10 days the results come as a downloadable report that can take hours, without the Quarantined and Filtered as spam statuses. Email Log Search in Google Workspace covers the past 30 days. Either shows that a notification came and when, not the request itself. If the site is due for a rebuild, put the form's path in the brief, from submission to saved record to named owner, as part of a B2B website redesign scope.
The message to send
To whoever maintains the website, with your IT or email provider copied, so the website side and the DNS side are answered in one thread. Run the test first so you can quote what happened.
Hi [name],
Some quote requests from our website form aren't reaching us. We sent a test on [date] from an outside Gmail address, and the notification [landed in spam / was quarantined / never arrived / showed the visitor's address as the sender].
By [date one week out], could you tell us how the form sends its notification (from the web server, or through which mail service), what the From address is, and whether the reply address is set to the visitor? We'd like the From address on our own domain, sending through [our Microsoft 365 / Google Workspace account or a sending service].
[IT contact], could you confirm that our SPF record includes that service and that DKIM is set up for it, and send us the message trace for our test?
We'd also like every submission saved in [the form's entry list / our CRM], not only emailed, and the notifications going to [two names]. Once the change is made, we'll repeat the same test and confirm it arrives.
Common questions
Why are confirmation emails not coming through?
Usually for the same reason notifications go missing: the website sends them in a way the buyer's provider can't verify. Since February 1, 2024, Google's sender guidelines have required senders to Gmail accounts to set up SPF or DKIM. Send a test to a Gmail address, check its Spam folder, then check that the mailed-by and signed-by lines show your own domain.
Why am I not receiving an email from a specific sender?
When the sender is your own website, one thing the steps above don't cover: if the form sends as the visitor, the sender changes with every request, so a safe-sender rule or block that matches one address won't explain the others.
Should our form send emails from the customer's address?
No. Send from an address on your own domain and set the reply address to the customer, so hitting reply still reaches them. A notification that claims to come from a buyer's Gmail or Yahoo address fails the checks those providers publish.
How often should we test our website's quote form?
Monthly for delivery, and after any change to your email provider, DNS, hosting or the form itself. Send one request from an outside address and follow it to the inbox, and every few months make it the fuller response-time test. Problems usually start with a change somewhere else, not with the form.