A contact form is only useful if the enquiry reaches somebody who can answer it. I test the whole handover, not just whether the submit button produces a green message. The page, application, mail service and recipient inbox each tell you something different.
Keep a small test record for every important form: its page, intended recipient, confirmation message and the last successful delivery check. This makes future hosting and plugin changes much easier to verify.
Begin with a controlled enquiry
Use a clearly labelled test message and a mailbox you control. Include a unique reference in the subject or message so you can follow it through the system. Tell the receiving team when a test will arrive, and avoid using real customer details.
Check required fields, email validation and the recovery path after an error. Does the form preserve what the visitor already typed? Can somebody using a keyboard reach the error and correct it? These checks matter before the server sends anything.
Then submit a valid enquiry from the public page while signed out. A form that works in an administrator’s session is not sufficient evidence that the public journey works.
Separate acceptance from delivery
WordPress documents that a successful return from wp_mail() does not establish that the recipient received the message. Treat that result as one stage of the handover, not a delivery receipt.
Check the mail service’s status or logs for the test reference, then confirm the message in the intended inbox. Look at spam and quarantine too. A relay accepting a message and a person receiving it are different observations; record which you have actually checked.
If the message is absent, follow the stages in order. Was the submission accepted? Did the application attempt to send? Did the relay accept or reject it? Did the recipient system filter it? Changing random form settings before locating the failing stage makes the next test harder to interpret.
Check the recipient and reply journey
A copied site can retain a demonstration address or another team’s recipient. Inspect the destination for each site and each form, including conditional routes. Do not assume that one successful form proves every subsite is configured correctly.
Open the delivered message and try the intended reply action using your test address. Confirm that the subject, message and contact details are readable. Where a confirmation email is part of the design, check that separately rather than assuming the internal notification proves both messages were sent.
Review what the website promises. A confirmation should explain the next step without claiming a delivery result that the application has not observed.
Repeat the check after meaningful changes
Retest after moving hosts, changing the mail service, replacing the form plugin or altering recipient rules. Use the same small checklist so results remain comparable. For multisite, include a representative public form from every site with its own configuration.
Avoid saving full enquiry bodies in diagnostic logs unless there is a clear reason and a suitable retention policy. A timestamp, test reference and delivery stage will often be enough for routine checks.
The final sign-off should be concrete: the public form accepted the test, the expected message arrived in the correct inbox and the reply went to the test sender. If a stage remains unverified, say which one.
Further reading: the WordPress documentation for wp_mail().