Marketing

How to measure enquiry quality, not just clicks

A practical way to record useful enquiries and interpret phone, form and search data without overstating results.

By Graphic Core   /   Published
Monthly guide series: March 2026

A hand sorting cards beside a phone and illustrative charts.

Define a useful enquiry before counting it

More website activity is encouraging only if it supports work your business can actually take on. Agree what makes an enquiry relevant: the requested service, genuine coverage area, practical timing and whether the customer is seeking a type of project you offer. The definition will differ between a local shop, a trade business and a consultant.

Keep the definition simple enough for the person answering calls to apply. An enquiry can be relevant without becoming a sale, and an unsuitable enquiry is not necessarily the caller's fault. The distinction is a tool for improving the information people see before they contact you.

Separate actions from outcomes

A click on a phone number is an indication of intent, not proof of a connected call. A form submission is not automatically a qualified opportunity, and a quote is not the same as an accepted project. Recording these stages separately prevents a marketing report from turning several measures of the same journey into several supposed leads.

For an initial record, count enquiries received, those relevant to the agreed criteria, quotes or consultations offered, and work accepted. Include a period and note where information is incomplete. If one person enquires by phone and email, decide how you will recognise and avoid counting the same opportunity twice.

Use a simple, privacy-conscious record

A spreadsheet or existing customer management system can be enough for a small team. Keep only what is useful for handling the enquiry and reviewing patterns: date, requested service, broad area, enquiry route, suitability and outcome. Follow your own retention and access rules, and avoid placing unnecessary personal or sensitive details in a shared reporting sheet.

Use consistent categories. For example, 'outside coverage', 'service not offered', 'suitable but no quote' and 'quote sent' reveal different problems. Keep a short note of why an enquiry was categorised where it was, without recording confidential details that the report does not need.

Treat source information as a clue

Ask 'How did you hear about us?' when it is natural, but offer more than one answer or a free-text option. Someone may see a social post, later search for the business and finally call after a recommendation. A single source field cannot capture that entire journey reliably.

Website analytics, advertising reports and Search Console each answer different questions. Search Console describes performance in Google Search; an advertising conversion report reflects its own measurement setup; your enquiry record shows what staff received. Keep their definitions separate rather than expecting totals to match exactly.

Check tracking and consent

Before adding a tracking tool, identify what it collects, whether it stores or accesses information on a visitor's device, which providers receive data and what choices are required. Some measurement technologies require consent and some situations have specific rules or exceptions; check current ICO guidance for your implementation rather than assuming that all analytics are automatically exempt.

If a visitor declines an optional tool, the report may miss some activity. Tell decision-makers about that limitation. Test any form or call tracking with a controlled, authorised test and compare it with a known enquiry, while keeping customer information out of reports unless it is needed and appropriately protected.

Build a simple example report

Suppose a team receives ten enquiries in a month. It identifies six as within its service and area, sends four quotes and learns that two have been accepted so far. These are illustrative counts, not a benchmark. The remaining enquiries or quotes may still need follow-up, so the final outcome should not be assumed.

Alongside the numbers, record what the team learned: two people requested an unavailable service, for example, or several asked the same question about timing. That context helps distinguish a volume issue from a messaging issue. Use broad categories in the report and keep identifying details in the appropriate customer system instead.

At the next review, compare the same definitions and note changes in staffing, availability or promotions. If the period contains only a handful of enquiries, describe the individual pattern rather than presenting a dramatic percentage. Make the report useful for a decision, such as improving one page or changing how quickly calls are returned.

Review patterns and take one action

At a monthly review, consider a short list: which services received suitable enquiries, which areas produced requests you could not serve, what questions recur and how many genuine opportunities reached the next stage. Small numbers can move sharply from month to month, so avoid drawing broad conclusions from one quiet week.

Choose one improvement and record when it was made. You might clarify a service boundary, fix a confusing form or add a useful answer to a key page. At the next review, look for a change in the pattern, while recognising that season, referrals and other activities can also affect the result.

YOUR NEXT MOVE / 01

Ready to make
more of your business?

Tell us about your website, your services and where you want to grow.

START A CONVERSATION