Stage 4: decide whether there is a fit
Use shared criteria so the next action is understandable and fair.
In this article
The situation
Qualification is a decision about whether the team can help and what should happen next. A short human checklist should come before a score or automated branch.
Ask whether there is a useful fit
Qualification should identify the next helpful action for the person and the team. Define a few observable criteria tied to service capability, problem, timing or geography. Avoid an opaque score whose meaning changes by responder. Keep a route for ambiguous cases so a request is not silently rejected because a form did not capture the right detail.
Two teammates should be able to apply the rules to the same sample and explain their reasons. Disagreement reveals wording or evidence gaps. Record both clear non-fit cases and missed opportunities when reviewing the criteria.
Link the decision to action
A qualified label is incomplete unless an owner accepts the next step. A non-fit decision should also produce an appropriate, respectful answer rather than an abandoned record. State what information is needed before a call, what can be learned during it and what should not be collected at all.
Measure whether accepted inquiries receive the promised action and whether staff repeatedly override the checklist. Use the findings to improve the written rule before encoding it in automation.
Review decisions that did not advance
A useful qualification log includes the fit reason, missing facts, decision owner and the response sent to the person. Review a sample of cases marked not fit and cases left uncertain. This protects against a checklist that saves staff time by silently rejecting requests the team could have served.
If two reviewers disagree often, revise the criterion or provide an example. Adding more numerical points rarely resolves an ambiguous rule. The output should be a defensible action for the person and the team.
Work through it
- Agree on three to five criteria related to actual service scope, needs and timing. Keep them observable and avoid collecting unnecessary sensitive facts.
- Review a small sample of prior conversations with two team members and compare decisions. Resolve disagreements in the checklist, not by hiding them in a score.
- Define a respectful next step for fit, not-fit and uncertain cases. Record the reason so follow-up is not arbitrary.
What to measure
- Conversations assessed with the same checklist
- Agreement on fit decisions
- Qualified inquiries reaching the next stage
Boundaries
- A numerical score is not evidence of predictive accuracy without real validation.
- Do not use protected or sensitive personal attributes to decide who deserves a response.
Questions for your own workflow
- Which criteria change the next action?
- What happens when information is missing?
- Who reviews disagreements?