An inquiry count cannot explain whether the website is attracting suitable work. A simple record of why requests do or do not fit can reveal unclear service boundaries, missing pricing context, or capacity constraints. The reasons need to be consistent enough to compare and specific enough to act on.
Separate fit from outcome
A suitable inquiry may not proceed because the business is fully booked. An unsuitable inquiry may arrive because the visitor misunderstood the service. Treating both as “lost” hides different problems and leads to different website changes.
Choose a small set of operational reasons such as service mismatch, location outside coverage, timing mismatch, or insufficient information. Use only categories relevant to the business, and avoid unnecessary sensitive or discriminatory classifications.
Keep room for uncertainty
For a hypothetical reporting service, a customer may request a dashboard before their source data is ready. That could mean a preliminary data review is appropriate, not that the customer is permanently unsuitable. A “needs clarification” state can preserve that distinction.
Do not infer a rejection reason from silence alone. Record what the team actually knows and distinguish customer-reported reasons from staff interpretation. Make the classification reviewable.
Turn patterns into useful changes
If many requests concern a service the business does not offer, clarify the relevant page. If timing is the recurring issue, review availability messaging. If budget expectations differ, explain scope and pricing assumptions more clearly.
Check the underlying cases before changing the website. A small number of unusual requests can distort a short reporting window, and categories may be applied inconsistently.
Start with the next set of inquiries the team already reviews. Add one reason field and a clear owner, then discuss what it reveals. The objective is better fit and more helpful information, not a complicated lead score that nobody can explain.

