How to Test Your Enquiry Form End to End

For many businesses the enquiry form is the point of the website. If it fails quietly, the site still looks healthy, visitors still arrive and nobody tells you what they wanted. The only fix is to test the whole journey yourself, from the page to the record.

Quick answer: submit a real test enquiry on a phone and on a desktop, then follow it all the way through. Check the validation messages, the thank-you page, the stored record, the notification email, the analytics event (which should fire once and only once), any hidden fields and the spam protection. Repeat after every change to the site or form, and on a regular schedule. Write down what you found each time.

Why a form that looks fine can still lose enquiries

The visible form is only the first part. Behind it sit a host that receives the data, a place where records are stored, an email that alerts you and an analytics tag that counts the result. Each can fail without changing how the page looks. Typical faults:

• a submit button that does nothing on certain phones
• notification emails that land in spam or go to an address nobody reads
• a conversion counted twice, or not at all
• spam protection that blocks real people
• information the page collects that the stored record never receives

An example from our own site

This is our own site, not a client’s. On 30 September 2026 we inspected the stored records behind our own contact form, without sending a test enquiry. The page had a hidden field for the package a visitor chose, and the links passed it correctly. But none of the recent stored enquiries carried it, and the form host’s list of registered fields did not include it. The form host builds that list from a second, hidden copy of the form in the site template, and that copy did not include the field, so the value was dropped on arrival.

Six service pages also linked to the form with a service name it did not list, so it opened with nothing selected. The fix added the field to the registered form, corrected the links and added a build check that fails if any contact link names a service the form does not list. Reading the records found the fault, but it is not the full test below: following a real enquiry through to the inbox is still the only way to confirm the whole journey.

The end-to-end test

Use real details, and make the test easy to spot later, for example by putting “TEST” in the name.

1. The visible form, on a phone and a desktop. Use an actual phone, not only a resized browser window. Check every field is reachable, the keyboard suits the field, the labels are readable and the button can be tapped.
2. Validation and error messages. Submit the form empty, then with a bad email address, then with one field missing. Each message should say what is wrong, sit beside the field and keep the rest of the entry in place.
3. The submit step. Send a valid enquiry. The button should show that something is happening and should not allow an accidental double send.
4. The thank-you page. It should confirm the enquiry and say what happens next. Check that it loads at its own address, since analytics often counts that.
5. The stored record. Open wherever enquiries are kept and read the test enquiry field by field. It should hold everything the visitor typed and the details they did not type.
6. The notification email. Check it arrived, how long it took, which inbox it reached and whether it has what you need to reply. Check spam as well.
7. The analytics event. In Google Analytics 4, use the real-time or debug view. Submit one enquiry and count the events. Zero means enquiries are missing from your reports. Two means you are overcounting. Refreshing the thank-you page should not add another.
8. Hidden fields. If the form records the service or package asked about, click every link that leads to it, submit, and check the stored record carries the right value and the form opens with the right option selected.
9. Spam protection. It should stop automated junk and let people through. Test as a normal visitor, on a phone and with a browser that blocks trackers.

How often to repeat it

• After every change to the site or the form: a redesign, a new plugin, an analytics tag update, a change of email provider or any edit to the form’s fields.
• On a regular schedule. Monthly suits most small sites. A site with few enquiries should test more often, because each lost one is a larger share of the total.

What to record

Keep one short log with a line for each test.

Date	Device	What was tested	Result	Fixed by
Date of test	Phone or desktop	Form, record, email, event, fields	Pass or fail, with detail	Name and date

Attach a screenshot when something fails. Over time the log shows which part of the journey breaks most often.

If you would like help

A conversion audit starts from £1,500 plus VAT. Ongoing CRO is part of our SEO and AI search retainer at £1,750 a month plus VAT, with a three-month minimum. Our marketing analytics service covers the tracking side, and the conversion scenario calculator shows what a recovered enquiry is worth on your own figures. See the pricing page, or conversion rate optimisation in Manchester if you are in the North West.