A contact form can display a success message while the enquiry never reaches the person who should answer it. Start by tracing one identifiable test through the form, any stored submission, the notification mailbox and a reply. Changing email plugins before you know where that path breaks can hide the original problem.
This guide is for owners of existing business websites. The testing sequence is a practical recommendation; the WordPress.com and Contact Form 7 details below apply to those products, rather than every form service.
1. Decide what a successful enquiry means
For a business, a useful test ends when the intended colleague can read the enquiry and reply to the test sender. A green banner confirms only the behaviour that the form provider assigns to it. It is not independent evidence that a person received the message.
Keep four observations separate: the visitor sees confirmation; a submission is stored if storage is configured; a notification reaches the right destination; and a reply reaches the sender. A visitor acknowledgement email is another message, so its arrival does not prove the sales notification arrived.
Contact Form 7's FAQ specifically covers a success response with no received email. It also says the plugin does not save submitted messages by itself. Do not assume there is a hidden inbox from which old enquiries can be recovered.
2. Run one controlled test on the published page
Use a form you own or have permission to test, and a mailbox you control. Warn the receiving colleague so the message is not mistaken for a real request. Avoid customer details and confidential attachments.
Record the page URL, language, device, time with time zone, and a unique marker such as TEST-FORM-A. Enter a short, recognisable message and your controlled reply address. Submit once, then record the visible response. If the form fails, save the error before trying again; repeated submissions make the evidence harder to match.
Inspect any submission store and the intended mailbox for that same marker. Search junk, quarantine or other filtered folders as available. Check the actual recipient configured in this particular form: an old employee address or a separate branch form can explain a missing notification.
On WordPress.com, the official troubleshooting guide points owners to Jetpack → Forms, including its spam view, and explains that third-party forms may keep separate logs. Storage settings matter. A missing entry is meaningful only if that form was expected to save one.
3. Use the evidence to choose the next check
| What you can verify | What it suggests | Next action |
|---|---|---|
| The form refuses valid input or never finishes | Failure before a usable confirmation | Save the error and ask the site maintainer to inspect validation, spam checks and the submission request |
| An entry is stored, but no email arrives | Capture worked; notification delivery remains unresolved | Check the form recipient and notification settings, then ask for sending logs |
| Email arrives in junk or quarantine | Delivery reached a filter, but the working inbox missed it | Have the mail administrator investigate filtering and sender configuration |
| A notification arrives without a key field | The message template may not include that field | Compare the saved test with the email template |
| A colleague receives the enquiry, but Reply targets the wrong address | The return path is misconfigured | Check Reply-To and repeat the reply test |
No stored entry and no email do not establish a single cause. Some forms intentionally use email alone. Ask what evidence the configured service can provide before concluding that the visitor never submitted anything.
An outgoing provider's accepted or delivered status also needs careful reading. It can help locate a fault, but it does not show that the receiving colleague saw the message. Keep the provider result and the mailbox check as separate evidence.
4. Check sender, recipient and reply details separately
The recipient is who should handle the enquiry. The sender is the identity used to send the notification. Reply-To tells the email application where a reply should go. These fields have different jobs.
For Contact Form 7, the mail configuration documentation describes the To, From and message-body settings, and requires a From address on the website's domain. Its FAQ explains that adding a form field does not automatically add the corresponding value to the email template. Ask the maintainer to compare the actual configuration with the product's documentation.
Use your mail provider's approved sender configuration. Have the visitor's address placed in Reply-To where the form supports it, then verify the reply goes there. Copying the visitor's address into From is not a reliable substitute for configuring your own sending identity.
If the logs show a sending failure, give the host or mail provider the test time, marker and exact error. Ask them to check sending permissions, authentication, credentials and service limits as applicable. An SMTP service can be part of a repair; installing one does not fix a wrong recipient, missing field or blocked form submission.
5. Accept the repair with a fresh test
After a change, use a new marker. Test the public page on a phone and a computer, covering each genuinely different form or recipient route. For language versions that share one backend, still check that labels, required-field messages and confirmation text make sense in each language.
Confirm that required-field errors let the visitor recover without losing their message. Check that the recipient receives the message and the fields needed to respond. Send a reply to your controlled test mailbox and confirm it arrives. If attachments are supported, use a harmless file within the advertised rules and check that the recipient can access it.
Record each result rather than marking the whole website as tested after one route works. A passing test proves that route worked at that time. It does not prove that every future message will arrive or that an enquiry will become a sale.
6. Leave a usable handover
Keep the test record with the site maintenance information: URL, test marker, time, expected recipient, observed submission record if applicable, mailbox result, reply result, repair and person responsible. Store sensitive settings in the appropriate account manager, never in a public screenshot.
Repeat the relevant test after changes to the form, hosting, domain email, notification recipient or spam protection. Agree who checks submissions and what happens when that person is absent. If enquiries are stored, agree access and retention rather than collecting copies indefinitely by default.
While a fault is unresolved, provide an accurate alternative contact route that your team actually checks. For a broader review, use the business website self-audit checklist. For ongoing responsibilities and budget, see website maintenance costs. The immediate decision is simple: identify the last step you can prove worked, then investigate the next one.
