Small Business Contact Form Audit: 10 Tests to Catch Lost Enquiries

1. Find the form from a real customer entry point

Open the service page a customer is likely to land on from search or an ad, not just your homepage. Can you find a relevant enquiry action without hunting through menus? Does it explain what happens next?

For a dental practice, a request-an-appointment action is clearer than a generic submit. For a garage, asking for a repair estimate may fit the customer's intent better than a plain contact link.

Pass test: someone unfamiliar with your website can find the correct action from a service page and explain what to expect after using it.

2. Complete the form on a phone, not only a laptop

Use an ordinary phone on mobile data. Check that fields, labels, dropdowns, consent controls and the submit button are readable and tappable. Try portrait mode, then zoom in. Watch for a sticky banner covering the button or a keyboard obscuring the active field.

Pass test: you can complete and submit the form without sideways scrolling, accidental taps or hidden controls.

3. Challenge every required field

Ask whether each field is necessary for the first reply. Name, one reliable contact method and a short description may be enough for an initial enquiry; the exact minimum depends on your service and obligations. Avoid demanding a full address, budget or lengthy questionnaire before a person can ask a simple question.

Try leaving optional fields empty. Try a long surname, an international phone number and a short message. The form should not silently reject reasonable entries.

Pass test: every required field has a defensible purpose, and ordinary customer input is accepted.

4. Make labels and instructions unambiguous

A placeholder that disappears as soon as someone types is not a reliable substitute for a visible field label. The W3C's form guidance recommends clear labels, instructions and identification of required fields. If you require a specific format, explain it before the person submits.

For example, asking for a phone number with the country code included is more useful than a mysterious invalid-input message after the fact.

Pass test: each field has a persistent, descriptive label, required fields are identified in words or an explained symbol, and any formatting rules are visible.

5. Test mistakes and recovery

Submit an empty required field, an invalid email address and an overlong message. A useful error identifies the exact problem near the field and tells the customer how to fix it. Previously entered valid information should remain intact.

Also try keyboard-only navigation. Can you reach every field and button, see where focus is, and recover from an error? These checks help identify usability barriers, not just accessibility problems.

Pass test: errors are specific and recoverable; customers never need to retype the whole form after one mistake.

6. Verify what happens after Submit

The button should show progress while the request is being processed, prevent accidental duplicate submissions where appropriate, and display an unmistakable success state only after the server accepts the enquiry. A spinner that disappears without feedback is not proof of success.

A good confirmation might say that the request has been received and when the team usually replies. Use a response-time statement only if your team can consistently meet it.

Pass test: a successful submission produces a clear confirmation; a failed submission produces a visible, actionable error.

7. Confirm the enquiry actually arrives

This is the most important technical test. Send a unique test message and check the destination inbox, CRM or booking system. Check spam folders and any forwarding rules. Verify that the customer's message, contact details, source page and timestamp are intact.

If the website shows success but the message is missing, investigate server-side delivery logs, integration failures and spam filtering. Do not assume a front-end success screen means the business received the lead.

Pass test: a staff member can find the complete test enquiry in the real working system.

8. Check spam protection without blocking real customers

Spam controls are useful, but a challenge that repeatedly fails can block legitimate enquiries. Test on a phone and a private browsing session. If you use a CAPTCHA or rate limit, ensure errors are explained and there is a workable alternative contact route.

Avoid collecting unnecessary personal data in the form or passing message contents into analytics tools. Review retention, privacy notice and access permissions with whoever handles your website and customer data.

Pass test: ordinary users can submit, obvious automated abuse is controlled, and sensitive form contents are not copied into analytics events.

9. Decide who replies — and when

A delivered enquiry is not yet a customer. Define which person or team owns incoming requests, what happens outside opening hours, and how unanswered messages are escalated. Test with a message submitted after hours and another during a busy period.

For example, a small garage might route quote requests to the service adviser and general questions to reception. If all enquiries arrive in one unattended inbox, the form can work technically while the customer experience fails operationally.

Pass test: each new enquiry has a visible owner and a documented follow-up process.

10. Measure confirmed enquiries, not button clicks

In Google Analytics 4, Google documents the recommended generate_lead event for lead acquisition. Configure measurement to fire when the enquiry is successfully received, rather than merely when someone presses Submit. Validate the implementation in GA4 DebugView or an equivalent testing environment, subject to your consent and privacy setup.

For a simple weekly view, record eligible contact-page sessions, confirmed form submissions, qualified enquiries classified in your CRM, replies sent within your target window, and appointments or sales attributable to those enquiries where attribution is reliable.

An illustrative example, not a benchmark: if 200 eligible visits produce 8 confirmed submissions, the observed submission rate is 4%. If only 3 are qualified, do not report all 8 as qualified leads. Segment by page and source before drawing conclusions.

Pass test: analytics submissions reconcile reasonably with actual received messages, with differences investigated rather than hidden.

A 30-minute contact form audit you can run today

Spend five minutes locating the form from your highest-priority service page, ten minutes testing mobile completion and error handling, five minutes checking success confirmation and delivery, five minutes checking staff routing, and five minutes verifying that a confirmed submission is counted correctly. Write down each failure, its page URL, device, time and screenshot; assign an owner and retest after the fix.

Start with broken delivery and invisible failures, then mobile blockers and confusing errors, then unnecessary fields and copy improvements. Do not redesign the entire site before fixing a form that cannot deliver a message.

What a website audit can detect — and what still needs manual testing

A website audit can help flag wider website issues that deserve attention, but no general site check should be assumed to verify the private inbox or CRM behind your form. Run the end-to-end test yourself, then use a broader website audit to review your wider website presence and identify other priorities.