Measure website enquiries that help your business learn

Define the stages before counting

Use separate labels for a contact interaction, a successfully received enquiry, a relevant enquiry and a confirmed next step. Agree what each label means. A visitor opening WhatsApp is an interaction; it does not prove that a message arrived. A successfully submitted form may still be a duplicate or unrelated request.

Choose a reporting period and keep its definitions stable. If the definitions change, mark the change rather than pretending the new totals are directly comparable with earlier reports.

Keep a small enquiry register

Create a record that supports follow-up and learning. Use an internal reference instead of copying personal details into every reporting document. Ask the handling colleague to record the actual outcome, not an optimistic prediction about the opportunity.

Keep source information as unknown when it is unavailable. Guessing that every direct message came from the latest campaign makes the report look complete while making its conclusions weaker.

• Date received, relevant service and contact route.
• Whether the request fits the published service scope.
• Next action, responsible person and current status.
• Main reason when a request cannot move forward.

Compare the full journey

For a fictional monthly review, imagine twelve received enquiries, eight relevant requests and four agreed discovery conversations. Inspect why the other relevant requests paused: missing details, unavailable capacity or a visitor who stopped replying are different situations.

Do not call all twelve enquiries sales, and do not treat the four conversations as completed revenue. Review a few actual messages alongside the numbers. This helps distinguish a confusing service page from an internal follow-up problem and gives the next website improvement a specific purpose.