How to test whether website enquiries reach your inbox

A form can look finished while delivering nothing. Test the whole route, from entering the message to receiving it in the intended inbox, before putting it in front of customers.

Identify what the button does

Ask whether the page uses an email draft, a hosted form service or a custom backend. An email draft depends on the visitor sending it from their own app. A server-submitted form needs a delivery mechanism. The visible success message must match what actually happened.

Write a safe test message

Use a clear test identifier and a reply address you control. Avoid real customer data. For example: “Launch test 08 October, contact page, mobile browser.” Get permission from the receiving business before sending test messages if you do not own the inbox.

Verify both sides

Submit once, inspect the confirmation and check the inbox, spam folder and any form-service logs you are authorised to see. Confirm that the message contains the agreed fields and that replying reaches the entered address. Record delivery time as an observation, not a guaranteed response time.

Test failure conditions

Try an empty required field and an invalid email format. Ask the developer how outages, delivery failures and repeated submissions are handled. A visitor should receive understandable instructions instead of a silent reset. MDN notes that client-side validation is not a replacement for server-side security checks.

Confirm ongoing responsibilities

Identify the provider account owner, any quota or subscription and who checks delivery after launch. Keep a visible alternative email route. Make sure the privacy information reflects the provider and the data actually collected.

Accept the form when a test reaches the correct destination, the reply route works and failure states are understandable. Keep the test record in the handover. If delivery remains uncertain, say so explicitly and use a working alternative instead of displaying an unverified success message.

Practical guidance with illustrative examples. Read our editorial standards or send a correction.