An enquiry form works when the customer can submit a request, the business can retrieve it and the right person can reply. A thank-you message on the website is only one part of that route. Test actual receipt and the agreed stored record before sending more traffic to the page.
Arrange the test with whoever receives enquiries. Use clearly labelled fictional details so nobody mistakes it for a customer job.
Trace the route before pressing submit
Ask the builder where the enquiry goes. It may be retained in a database or customer system, with an email notification sent separately. Some setups rely only on email. You need to know the actual arrangement, not assume a backup exists because the form looks finished.
Record who owns the next action and where they look for new requests. If several staff members receive notifications, agree how they avoid replying to the same customer independently.
| Stage | What to check | Evidence |
|---|---|---|
| Customer action | Form or contact link works | Observed result on the live page |
| Receipt | Request reaches the intended system | Actual record, not just a submit event |
| Notification | Recipient is told about the request | Inbox or agreed alert result |
| Reply | Correct customer route is available | Reply details checked |
| Recovery | A notification failure does not hide the request | Known retained record and process |
Test the page customers use
Open the live website on a phone and follow the route from a service page. Check that the telephone link calls the right number and that directions, if relevant, lead to the intended location.
For the form, confirm the labels explain what is needed. Required fields should be identifiable, and an error should tell the customer how to correct it. Keep the first step proportionate to the job: a short description and a reply route may be more useful than a detailed tender questionnaire.
Do not add sensitive information to the test. Avoid genuine residential addresses, payment details and customer documents. Use a test identifier in the message so the recipient can find the right request.
Confirm the result at both ends
After submitting, check what the customer sees and what the business receives. Confirm the service context and message content are intact. Check the reply address rather than assuming the sender shown in the notification is the customer’s address.
If the setup retains the enquiry, find that record too. Do not treat an email arriving once as proof that every future notification failure can be recovered.
Where a booking platform is involved, distinguish a general enquiry from a confirmed appointment. A contact form should not tell someone they are booked unless a real booking process completed. Use the provider’s agreed test method instead of reserving a genuine slot or making a payment.
Check failures with the builder
Agree how invalid input, duplicate submission and notification failure should be handled. Technical failure tests belong in an appropriate test environment with the builder; do not deliberately disrupt a production email service to see what happens.
Ask how the site avoids losing a request when an alert fails and how that failure becomes visible. If the answer is unclear, record the gap. A usable recovery process is more valuable than adding another marketing campaign to a fragile destination.
Keep measurement honest
A button click, successful submit event and received enquiry are different measures. A received enquiry also needs assessment before it counts as suitable work. Keep those stages separate when reviewing marketing performance.
For HVAC businesses, use the qualification guide after receipt. For plasterers, the quote-page guide helps choose useful initial questions.
Repeat after meaningful changes
Retest when forms, hosting, email routing, booking links or the receiving system change. Keep a record of the date, page tested and actual result. A previous test is useful evidence, but it does not prove a new setup behaves identically.
If the website gets traffic but few suitable contacts, read website not getting enquiries. Fix the route a customer has to use before expecting more visitors to solve the problem.