How to tell whether your business website is generating enquiries

Short answer: Track the journey from a visit to a confirmed enquiry and then to a qualified lead. Button clicks and phone taps do not prove a connected conversation. A useful measure counts successful submissions and what happened next, not just page views.

Start with one clear next step per page

Each service page should point visitors to one obvious action: submit an enquiry, request a callback or book a time. If a page offers three competing links, it is hard to know which one counted as success. Pick the action that moves someone toward a real conversation and make that the page's main goal.

A button click is not a confirmed enquiry

A click on a contact button tells you someone showed interest. It does not tell you the form reached your team, that the fields were valid or that a person replied. Treat a server-confirmed submission as the real signal. Ask whoever set up the form to check the receiving record and not only the "thank you" page.

Phone and email clicks prove less than they seem

A tap on a phone number or email address only shows the device opened the relevant app. It does not prove the call connected or the message was sent and answered. If phone or email is your main route, pair the click with a record in your CRM or a returned call log so you can follow the enquiry to a result.

Record the lead outcome, not just the lead

A new enquiry is the start, not the finish. In your CRM, note whether the lead was qualified, booked, declined or waiting. That outcome turns a count of enquiries into a measure of what the website actually produced.

Keep personal contact details out of analytics

Customer names, emails and phone numbers belong in the enquiry record, not in a web analytics tool. Share counts and conversion rates instead of copying form text into dashboards. If you segment performance by source or page, use aggregated, anonymised labels rather than identifiable details.

Compare consistent reporting periods

Compare the same window each time, such as the last 30 days against the previous 30. Count visits to the service page, completed enquiries, qualified leads and wins. If visits rise but completed enquiries do not, check whether the traffic is relevant to your offer, whether the form is reliable and whether the follow-up is keeping up. If completed enquiries rise but qualified leads do not, check the offer fit and the qualification step rather than assuming a single cause.

An illustrative enquiry-to-outcome flow

Planning example, not a client result or a configured integration.

Actual messaging, timing and connections depend on the written scope and applicable permissions.

Watch small samples and attribution limits

Small samples can be volatile and there is no universal minimum that makes a trend. Wait for enough data before changing a page or dropping a service. Some sources cannot be attributed exactly, and ad clicks can be counted twice by different tools. Trust the direction over weeks, not a single number, and compare like with like.

Diagnose where visitors drop off

If visits rise but enquiries do not, look at where people leave: the page itself, the form or after the first reply. Remove friction where you can and test the whole path yourself rather than only the button. When reviewing the numbers, exclude your own testing, duplicate submissions and spam so they do not inflate the count, and apply the same exclusions each period.

Your next step

Write down the one action each service page should drive, where a confirmed enquiry should land and who owns the follow-up. We can help you map the enquiry journey and set up a managed website and CRM workflow that records real results. See the website enquiry follow-up guide for the handoff steps.

• Define what counts as a successful enquiry.
• Verify the form was received by the server, not just clicked.
• Separate phone and email clicks from connected conversations.
• Exclude your own testing, duplicates and spam consistently.
• Record whether each enquiry was qualified, declined or waiting.
• Compare consistent reporting periods, like for like.
• Inspect small samples and attribution limits before acting.