Qualification
Part of Improving an underperforming lead funnel
Investigating many leads but few accepted opportunities
Reconcile lead counts with genuine requests, pending reviews and sales decision reasons to find the acceptance gap.
High lead counts with few sales-accepted opportunities: inspect requests and sales decisions before changing acquisition. The gap may include duplicate or non-sales submissions, work outside service scope, cases awaiting review and suitable requests not yet accepted.
Rebuild the count from requests
Choose a received-date period and begin with what reached the business. Report raw submissions, confirmed tests or spam, repeated submissions about the same need, and distinct genuine enquiries separately. Then show how many genuine enquiries were assessed, accepted, declined or left pending. Pending cases are not rejections.
Define the outcome in the business's own terms. Here, sales acceptance means a reviewer agreed to a specific next action under a stated rule. Assignment to a queue does not prove that decision. If the CRM creates an opportunity only after a later conversation, report acceptance and opportunity creation as separate stages.
Ask which requests failed to progress, the recorded reason and who made the decision. Put counts, denominators and the rule's effective date beside any rate.
Group reasons by the change they suggest
Read requests in each outcome group alongside the reviewer's recorded reason.
| Finding in the record | Check before changing acquisition |
|---|---|
| Requested work is outside the service offered | Compare the arrival promise with the actual service boundary |
| A relevant request lacks one decisive fact | Check whether a focused clarification was sent and answered |
| A genuine request still awaits review | Check ownership, capacity and assessment timing |
| Sales declined work the stated rule would accept | Resolve the rule or classification disagreement |
| Several records concern one request | Correct the count and preserve any new detail for the responder |
A label such as 'poor quality' hides these differences. It cannot show whether to change targeting, explain the service more clearly or repair an internal handoff.
Reasons for Unaccepted Requests and Suggested Actions
- Out of service scope
- Clarify service boundaries in marketing promises; review inbound requests from high-impact channels
- Missing key detail
- Implement automated clarification templates; track response rates by source
- Awaiting review
- Assign ownership and set review deadlines; monitor queue times in CRM
- Rule conflict (declined but should be accepted)
- Audit acceptance rules; align classification logic with sales team decisions
- Duplicate submissions
- Use deduplication tools; update lead capture forms to prevent re-entry
Keep analytics counts in their place
A GA4 Lead acquisition report is not automatically a request-level acceptance measure. Reconcile its measurement with received records before you use it to assess acceptance.
Act on the recorded pattern
If out-of-scope requests cluster around one promise, clarify it and review later requests from the same route. If suitable requests lack context, improve the clarification process. If requests wait unassessed, give them an owner and a review window before judging acquisition quality.
Compare later received-date groups under the same acceptance rule and with similar review time. Show accepted counts, pending cases and reasons. An acceptance percentage can rise because fewer genuine enquiries arrive, so also check the number of useful opportunities.
