Contact forms: how to check that messages reach your business

1. Follow the whole path of an enquiry

A contact form may be a prospective customer's first interaction with your business. Before changing settings, record which page contains it, which application handles it, which service sends the notification and which mailbox should receive it. Identify who monitors that mailbox and who covers their absence.

In WordPress, for example, a true result from wp_mail() does not prove receipt. Its documentation says that the sending request was processed without an error. Check submission, sending and arrival at the destination separately. Even receipt does not establish that someone read the enquiry.

2. Use a consistent sender and the correct Reply-To

Use a From address on your own domain that is permitted to send through the chosen service. Do not replace it with the visitor's Gmail or other provider address. To direct replies to the visitor, use Reply-To through the form plugin's supported fields and validation.

Check the To recipient separately. An old address can remain after testing or a change of contractor. Also check what happens when an optional field is left empty. Contact Form 7 documents a sender on the website's domain and a separate Reply-To; follow the equivalent settings for other applications.

3. Confirm the sending route and authentication

Ask your administrator to confirm the route the application actually uses. For SMTP, record the approved hostname, port and TLS setting supplied by the provider, without copying passwords into notes or tickets. Avoid settings copied from guides for a different service, and do not disable certificate verification to hide an error.

Have the administrator check that SPF and DKIM cover the actual sending source and that DMARC domain alignment is correct. Google's guidance explains alignment between the From domain and the SPF or DKIM domain for the relevant DMARC check. An SMTP change can require a DNS review. Authentication supports delivery but does not guarantee inbox placement. Preserve records needed by other authorised services.

4. Run a controlled check through the public page

The site owner can arrange a test using their own address and harmless content. Use a recognisable subject, such as “Contact form check – 1 November”, and record the time and time zone. Avoid real customer details. Test the normal public form, not only an SMTP plugin's test button.

Record the browser result and obtain confirmation from the person monitoring the destination. If a second destination is necessary, use only a mailbox you control or a recipient participating in the test. A successful check covers that route at that time; it cannot guarantee every future delivery.

• Look in the inbox and spam folder, and check rules or forwarding.
• Confirm that Greek characters, the subject and required fields arrive correctly.
• Open a reply without sending it and check that the proposed recipient is the test address.
• Keep only the result and the technical details needed to identify the test.

5. Use evidence to locate a failure

If the email is missing, compare the submission time with the application log and, through the administrator, the sending service log. Look for a message or queue identifier and the exact SMTP response. A 250 reply after DATA completes means the server accepted responsibility for delivery or relay; it does not prove inbox placement. Responses beginning with 4 indicate a temporary failure; those beginning with 5 call for review and correction before repeating the same request.

Avoid repeated submissions while you do not know whether the first message is queued. Ask for that attempt to be traced. This prevents identical enquiries from obscuring the diagnosis. Do not disable spam filtering across the service or publish complete logs or customer messages.

6. Make the check part of site maintenance

Arrange a short recheck after changes to the form, sending plugin, hosting, DNS or SMTP credentials. Agree a regular check based on how important the form is to the business. Record the last confirmed receipt and the responsible person, so the process survives a change of contractor.

If the application can store submissions, consider whether that feature is needed as a second way to find outstanding enquiries. Limit access, stored information and retention according to your business process. Confirm the feature exists before relying on it. Provide a clear alternative contact method on the page as well.

7. What to include in a support request

A specific example is more useful than “the form is broken”. To investigate the hosting and business email path, collect the following in a private support request. The scope of application and mail management depends on the service you ordered.

• The page address, application or plugin, and any recent change.
• The test time and time zone, with a recognisable subject or identifier.
• The last confirmed stage and any browser or SMTP error.
• The outcome of destination and spam-folder checks, without passwords, access secrets or unnecessary message content.