A form can display “message sent” without delivering anything. For a business, the damage is silent: the visitor thinks they have been heard, but the lead enters no system and nobody knows how many enquiries have been lost.
Separate sending from delivery
The plugin records that it passed the message to WordPress; WordPress may pass it to the server; the server may attempt delivery; the recipient’s provider may reject, delay or mark it as spam. Each stage needs a different check.
Initial checks
- The recipient address and conditional form rules.
- Sending logs, where available.
- Spam, filters and mailbox forwarding.
- Website and server errors.
- The sender domain.
- SPF, DKIM and DMARC records.
- Hosting provider limits or blocks.
Why the wrong sender causes problems
Using the visitor’s domain as the sender may seem convenient for replies, but creates messages claiming to come from a domain the website is not authorised to use. A sender on the website’s domain, with the visitor’s address as Reply-To and consistent authentication, is more reliable.
SMTP is not a magic solution
An SMTP or transactional service can improve traceability and reputation, but needs correct credentials, domain settings and records. Installing several mail plugins without reading the logs may introduce conflicts and hide the cause.
Do not entrust a lead to one email
Important enquiries should also be recorded on the website or in a CRM, with appropriate privacy information and retention. The email becomes a notification rather than the only copy of a business opportunity.
A check that can prevent months of losses
Periodically submit a test enquiry and verify receipt, recording and response. Ongoing support can include checks of critical functions; SOS support addresses forms that are already blocked or problems involving servers and configuration.