A “sent” message does not confirm inbox delivery
Someone completes your website’s contact form, sees a confirmation and waits for a reply. You receive nothing. Before replacing the form, establish which part of the enquiry’s journey needs checking: collecting the details, preparing a notification, sending it or receiving it.
WordPress uses an internal tool called wp_mail() for many email requests. Its official documentation explains that a positive result does not guarantee the recipient received the email. A confirmation on screen and an empty inbox can therefore occur together.
The notification sent to your business and the confirmation sent to the visitor are separate messages. Establish which is missing. Do not assume WordPress stores every enquiry either: that depends on the form and its configuration.
Make a test you can trace from start to finish
Prepare a test enquiry using your own details and an identifiable reference, such as “Contact test — form review”. Record the time and page address. Use wording that distinguishes it from a real enquiry.
- Complete the form as a visitor would, without an administrator login unless necessary.
- Keep the message displayed by the website and the expected notification recipient.
- Search for your reference in the inbox, spam folder and other folders or mailbox filters.
- Ask the website team whether there is a record of the enquiry and attempted notification.
A form that never finishes submitting needs a different investigation from one that confirms submission without delivering a notification. Preserve that distinction when reporting the issue. Avoid repeatedly submitting tests: one or two clearly identified messages are more useful than many indistinguishable ones.
Check the recipient and recent changes
Establish which address is configured in the form. It may still point to someone who no longer handles enquiries, contain a typing error or use forwarding that has stopped working. Normal business email working does not establish that website notifications arrive too.
Record whether the issue began after a hosting, mailbox, domain, plugin or configuration change. That is a lead to investigate rather than proof of the cause. If it followed an update, see our guide to WordPress update problems.
Report whether only one recipient is affected. An agreed test to another mailbox may help a comparison, but should not involve customer information or an uncontrolled change to the public form’s destination.
A worksheet for finding the outstanding check
| Stage | Record | What it establishes |
|---|---|---|
| Page | Address, date and test reference. | Which form and submission are under review. |
| Visible response | Confirmation, error or submission that never completes. | How the visitor’s interaction ended. |
| Stored enquiry | Whether a record exists and who can check it. | Whether the request was retained another way. |
| Notification | Expected recipient and available record. | Whether the intended email was prepared. |
| Sending | Email service result or message identifier. | How far the message progressed. |
| Mailbox | Arrival, folder, rejection or missing evidence. | What the email administrator should review. |
Write “not checked” where access or records are unavailable. Not finding a record does not establish that the corresponding stage failed.
What the technical team should investigate
Using the test reference, the website team can review the form, its recipients and sending configuration. The email administrator can check whether the service accepted, rejected or held the message and review the relevant filters.
If someone recommends “adding SMTP”, ask which finding it would address. SMTP is a way of passing a message to a mail server. A different sending setup may be appropriate, but does not itself fix an incorrect recipient or an enquiry that was never generated.
You do not need to edit domain records, disable spam filters or share passwords to prepare this review. Those checks belong with the responsible team and should preserve the email service’s protections.
An example: the visitor gets confirmation, but the business gets no enquiry
Fictional worksheet example. It does not describe a client incident or a test that has been carried out.
A business tests its form. The person submitting it receives a copy, but the sales team cannot find the enquiry. The worksheet separates the two notifications and records each recipient.
If the sales notification pointed to an old address, that configuration would need reviewing. If the address were correct, the next step would be to trace the attempted delivery to that mailbox. The visitor’s copy arriving does not establish which explanation applies.
Look after enquiries that may be affected
Agree which period is affected and whether another copy of submissions exists. Without a retained record, nobody can promise to recover messages that were never stored. Consider a visible alternative contact method while the issue is investigated, and check that it works.
Before changing plugins or their storage, establish what information they retain. Our guide to removing a plugin explains why replacing or deleting a component may affect data. If changes are needed, prepare a backup with a checked recovery process.
Prepare the details of one test submission
The useful starting details are straightforward: the form’s page, test time, website response and missing notification. They help establish what to review on the website and what the email provider needs to check.
If you would like help, tell us what happens with your form. We can assess the case and propose the necessary checks or work, agreeing the scope before starting.