
The contact form used to bring in a steady trickle of jobs, and lately it has gone quiet. Or a customer tells you they filled in your form last week and nobody called. Either way, the worry is the same: how many people wrote in and heard nothing back? When a website contact form is not sending email, the page usually looks perfectly normal, which is what makes the problem easy to miss for weeks. The good news is that you can find out tonight whether the form works, and you can often find out where it stopped. A form has several links in its chain, from the button a visitor presses to the inbox you check, and a failure at any one of them looks the same from your desk: silence. One careful test tells you which link broke. It may also lead you to messages you thought were gone, so start with the test before you change anything.
Key Takeaways
Send one submission from an outside email address with a unique marker in the message, note the time, and save the confirmation screen.
If the form saved the submission but no email arrived, the form worked. The failure is in sending or receiving the notification.
An old address, a switched-off notification, spam filtering, a missing mail path on WordPress, a host block and missing SPF or DKIM each have a different fix. No single plugin fixes all of them.
Keep a stored copy of every submission, send notices to a second person where your platform allows it, and repeat the test after every site, email or DNS change.
How do you test a contact form that has gone quiet?
Run one real submission, the way a customer would, and then look in four places. The whole check takes about fifteen minutes, and it gives you evidence you can act on or hand to whoever manages your site. Do it in this order, and resist the urge to change settings until you have your result.
The fifteen-minute contact form test
- 1
Minutes 1 to 3, submit a real test
Open your contact page in a private or incognito window. Fill in the form using a personal email address outside your business domain, and put a unique marker in the message, such as FORM-TEST followed by today's date and the time.
- 2
Minutes 4 to 6, check the inbox
Save or screenshot the thank-you message. Then search the notification inbox for your marker, including Spam or Junk, any quarantine area and any mail rules that move messages into folders.
- 3
Minutes 7 to 10, check stored entries
Sign in to your website platform or form plugin and find its list of submissions. Look for your test.
- 4
Minutes 11 to 13, compare the record
Match the name, email, time and form name in the stored entry against what you typed.
- 5
Minutes 14 to 15, check the address
Open the form's notification settings and read the "send to" address one character at a time. Write down what you found.
Two details make the test worth running. First, use an address outside your business. A test sent from your own company mailbox can be caught by internal rules or treated differently because you are writing to yourself, so it tells you less. Second, submit once. Repeated test entries, changed DNS records or deleted submissions make the trail harder to read before you have preserved it.
The thank-you message on screen is not proof that anyone received the lead. It only means the visitor's browser got a response from the form. WordPress makes the same point about its own mail function: the wp_mail() reference notes that a successful result does not mean the recipient actually received the message.

What does your test result mean?
Your fifteen minutes give you one of a few results, and each points to a different part of the chain. Read it like a relay race: the question is where the baton was dropped.
| What you found | What it means | Your next step |
|---|---|---|
| No stored entry, no email | The submission never reached the form system. The form, a validation rule, a CAPTCHA, a script or the platform failed. | Record the browser, device, page address, time and any error message, then get the form itself checked. |
| Stored entry, no email anywhere | The form worked. Sending or receiving the notification failed. | Keep the entry. Check the notification address and switch, then ask the host or mail administrator for mail logs. |
| Stored entry, email in Spam or quarantine | The notification was sent and reached your mail system, which filtered it. | Release the message, allow-list the sender your platform documents, and check your mail rules. |
| Email arrived in the inbox | This test passed. | Look at what changed recently, and read the section on stopping silent failures below. |
If your form does not store entries at all, you only have the inbox result. That is worth knowing on its own, because it means every lead your form has ever received exists in exactly one place.
Where are the messages people already sent?
Before you fix anything, check whether the leads you feared were lost are sitting somewhere you have not looked. Where submissions live depends on the exact form product, not just on the website platform. The table below lists where the common platforms keep them, based on each provider's own help pages.
| Platform | Where to look |
|---|---|
| WordPress | WordPress itself has no built-in inbox for form entries. It depends on the form plugin. WPForms has an Entries area in its dashboard. Contact Form 7 needs a separate storage add-on, such as Flamingo, so without one the email may be the only record. |
| Wix | Site dashboard, then Forms and Submissions, then the submissions table for that form, as covered in managing your Wix forms. |
| Squarespace | The storage option chosen for the form block, the Form Submitters or Contacts panel when the form has a required email field, or an export from the form block, per Squarespace form storage. |
| Netlify | The site's Forms area, where verified submissions and notification settings are managed, per Netlify Forms setup. |
| Shopify | The Forms app keeps its submissions in the Shopify admin, per managing Shopify Forms. A theme contact form works differently: it sends to the store's sender email, per adding a [Contact Us page](https://help.shopify.com/en/manual/online-store/themes/customizing-themes/common-customizations/add-contact-page), so its history lives in that mailbox. |
If you find entries you never saw, reply to them now, before you start repairs. A short, direct note that says you just found their message and want to help can still win back a job.

Why is a website form not sending email?
Once you know which link broke, the cause usually falls into one of six documented failures. They are listed below in a practical order to check, starting with the ones that take minutes. No published study ranks these causes by how often they happen across small businesses, so treat the order as a checking sequence rather than a league table. Each one has its own fix, and applying the wrong fix can waste a week.
The notification goes to an old or misspelled address
This is the quickest one to rule out. A form may still send notices to a former employee, an address you stopped checking, or an address with one letter wrong. Changing your account email does not always change where forms send. Squarespace, for example, says that updating your account email address does not automatically update form storage. The fix is to correct the address in the form's own settings, then run the test again.
The notification or automation is switched off
Hosted platforms let you turn a form's notification or automation off, and it can happen during a redesign, a plan change or a template swap. The fix is to switch it back on in the form's settings. One platform detail is easy to miss: Squarespace documents that form emails on trial sites are disabled, except for Circle members, in its form storage help.
The email arrives, then gets filtered
Sometimes everything works up to your own inbox, and your mail provider decides the notice looks like spam. It may land in Junk, in a quarantine area only an administrator sees, or in a folder a mail rule sends it to. Wix's form troubleshooting page tells owners who miss notifications to check Spam and Junk and to allow-list the Wix sender domains it names. The fix is to release the message, add the documented sender to your allowed list, and review the rules on the mailbox.

WordPress has no working mail path
WordPress sends form notices through the server it runs on, and that server has to be set up to send mail. The WordPress server mail documentation says WordPress "has never provided either a MUA or an MTA by default," meaning it has never shipped its own mail program. Without properly configured local mail or a remote SMTP connection, outgoing mail will not be sent. The fix is to route the site's mail through an authenticated SMTP or transactional mail service, or to have your host set up its mail server correctly. Several tools can do this, and the right one depends on your form, your host and the email provider you send through.
The host blocks or limits outgoing mail
A host may block or cap the mail a website sends, and from your side it looks the same as any other failure. Only the host can confirm it, because the evidence is in the server's mail logs. The fix starts with a support ticket that includes your test time, your marker and whether the entry was stored. That evidence saves a round of back-and-forth.
The sending domain fails SPF or DKIM
SPF and DKIM are records in your domain's DNS that tell receiving mail systems a message really came from you. Google's email sender guidelines say that from February 1, 2024, anyone sending to personal Gmail accounts needs SPF or DKIM, and bulk senders need SPF, DKIM and DMARC. Mail that fails can be sent to spam or rejected. The fix is to add your email provider's SPF and DKIM records and publish DMARC as appropriate. You cannot tell from the outside that authentication is the cause, though. It shows up in the message headers or in rejection logs, so ask for those before changing DNS.
Can you fix it yourself, or do you need help?
Often, you can fix it yourself. If your test found a stored entry and the email went to an old address, a switched-off notification or a spam folder, the repair is a settings change. You do not need a redesign, a new form plugin or a move to a different host. If you have administrator access to the form and the mailbox, you may be done within the hour.
The table below gives a rough sense of each job's size. These are ranges for planning, not quotes, because the real time depends on your setup and who holds the passwords.
| Repair | What it involves | Rough size |
|---|---|---|
| Correct the notification address | A settings change by an administrator | Minutes once you have access |
| Turn the notification back on | A settings change on the platform | Minutes |
| Release and allow-list the sender | A change by whoever runs your email | Minutes to a business day |
| Add a second storage destination | A settings task; plan limits may apply | Usually short |
| Set up authenticated sending and DNS records | Access to the mail provider, DNS and sometimes the host | An hour to several business days, allowing for DNS changes and testing |
| Repair a broken custom form, script or webhook | Developer diagnosis | A focused fix up to a rebuild, depending on what is found |
Help makes sense when you cannot reach the affected system, when the fix needs your host, your DNS and your email provider to line up, or when the form itself is failing. It also makes sense if you want someone to test the form on a schedule and tell you when it breaks. Nobody can promise that every email will reach every inbox, because the receiving mail systems are outside any website provider's control. What you can get is a form that keeps a record and tells a real person when something goes wrong.
How do you stop a contact form from failing silently again?
The goal is simple: an empty inbox should mean no leads, never missing leads. Right now, a quiet inbox cannot tell those two apart. Four habits close the gap.
- Keep a stored copy of every submission: Turn on entry storage in your platform or form plugin, so each lead exists somewhere other than the inbox. On WordPress, confirm your form plugin actually saves entries.
- Send notices to a second person: Where your platform allows it, add a backup recipient whose mailbox is run separately from the first. Netlify supports form notifications by email, webhook and Slack. Squarespace lets you use more than one storage option, though its email storage accepts one address.
- Test on a schedule and after every change: Repeat the fifteen-minute test regularly, and always after a site update, a theme or form change, a new email provider or any DNS edit. A platform move is a common moment for forms to break, so add it to your list if you are switching website builders.
- Watch for an unexpected silence: Where a monitoring service or your platform supports it, check the form with a scheduled test submission and alert someone when it fails, or when no submissions have been recorded for longer than usual.
Keep a unique marker in every test so each one is easy to find later. A human test still matters even with monitoring in place, because an uptime check only proves the page loads. It cannot prove the notice reached a person.

Once those habits are in place, you can answer a customer who says they wrote in. Either you find their entry with a timestamp and reply, or you can see that no submission reached the system and look at the form itself.
Can you trace a missing form lead?
Pick an answer to begin.
1. Your test entry is saved in the form's submissions list, but no email arrived. What failed?
2. What is the best address to send your test submission from?
3. WordPress reports that its mail function succeeded. What does that prove?
Frequently Asked Questions About website contact form not sending email
How do I know if my contact form actually submitted?
Look for the entry in your platform's or form plugin's submissions list. The thank-you message only shows that the browser got a response, not that the lead was saved or sent.
Why did my form say sent, but I got no email?
The form can accept and save the submission while the notification fails afterward. It may have been filtered, sent to an old address, switched off, or rejected by the receiving mail system.
What should I do if emails are not sending from my website?
Send one test from an outside address with a unique marker, then check stored entries, the notification address, Spam or quarantine, and mailbox rules. The result tells you which part to fix.
Do I need SMTP for my contact form?
On WordPress, the site needs a correctly configured mail path, and authenticated SMTP is a common way to provide one. Hosted platforms such as Wix, Squarespace and Netlify send notices through their own systems.
Can two people get the form notifications?
Often, yes. Netlify supports several notification channels, and other platforms offer extra recipients or storage options. Check what your plan allows.
How often should I test my website form?
On a regular schedule you will keep, and every time the site, theme, form, email provider or DNS changes. No official standard sets a frequency.
The Bottom Line
A quiet contact form can mean fewer inquiries, or it can mean inquiries that never reached you, and an empty inbox cannot tell you which. One test from an outside address, followed by checks of stored entries, the notification address, Spam and your mail rules, shows where the chain broke. The fix then matches the break: an address, a switch, a filter, a mail path, a host setting or a DNS record.
Once the form stores every submission, alerts more than one person and gets tested after every change, you stop guessing. When a customer says they wrote in, you can find their message and call them back.
If you would rather not chase this yourself, Web Leveling can run the test with you, trace the failure through your platform, host and email, and set up the stored entries and backup alerts. Our website maintenance work includes checking that your forms still reach a person after every update. We work with small and medium businesses across the country and overseas. Tell us what your contact form is doing, and we will help you find where the leads are going.
Terms
Contact form words in this post
Tap a term to see what it means.
Notification. The email a form sends to tell you someone submitted it, separate from the stored submission itself.
Stored entry. A copy of a form submission saved by your website platform or form plugin.
SMTP. The standard way mail servers send email; an authenticated SMTP service sends mail on your site's behalf with a login.
SPF and DKIM. DNS records that let receiving mail systems check a message really came from your domain.
DMARC. A DNS record that tells receiving mail systems what to do with mail that fails SPF or DKIM checks.
Quarantine. A holding area where a mail system keeps suspicious messages, often visible only to an administrator.
Allow-list. A list of senders your mailbox always accepts, so their messages skip the spam filter.




