Why dispositions beat notes
Notes describe what happened. A disposition decides what happens next. Most teams write long call summaries that nobody re-reads, then wonder why the same prospect resurfaces in the pipeline weeks later with nothing attached to it.
The fix is structural. Replace the open-text note with a closed set of outcomes, so every enquiry has to leave the CRM in exactly one of a small number of states. Nothing sits in between, and nothing depends on somebody remembering to follow up.
The four disposition states
Four states is enough. Fewer creates ambiguity, more creates admin. Each state has one trigger, one owner and one deadline, and the agent records it before the call ends.
- Qualified — matches the ideal profile and a meeting is booked. Owner: the account executive.
- Disqualified — does not match the profile, or budget and timeline do not align. Owner: the lead generation team, who update the source criteria.
- Pending — more information is needed before a decision. A specific question, a deadline and an owner are recorded. No pending entry survives past 72 hours without a new event.
- Routed — assigned to a specialist for qualification, with a 48-hour handoff window.
How to record it in the call
The disposition is recorded during the call, not after it. Before the call ends, the agent selects the state. If the agent cannot decide, the answer is not a note. It is pending, with the specific question that would settle it.
The form takes three fields: state, reason from a short dropdown, and next action with a date and an owner. That is less typing than most call summaries and far more useful to everybody downstream.
What the pipeline shows
A pipeline with real dispositions answers three questions at a glance: where enquiries are stalling because a pending entry has no next date, which sources produce disqualifications, and which owners sit on qualified prospects the longest before a meeting is booked.
We review four numbers every week: qualified count, qualified-to-meeting conversion, average time from enquiry to qualification, and disqualification rate by source. Those four numbers say whether the problem is sourcing, routing or conversion, without anyone guessing.
Where the time goes
Most of the delay between an enquiry arriving and a decision being made is not selling. It is time spent in a state nobody wrote down: an enquiry that arrived after hours, a call that ended without a next step, a message forwarded to a colleague who assumed somebody else had it.
Dispositions surface that time, because every enquiry is always in exactly one state. An enquiry cannot sit unnoticed in an inbox when the CRM demands it be pending with a date, routed with an owner, or closed with a reason.
How we measure it
The metrics that matter are time-based: time from enquiry to first response, time from response to qualification, and time from qualification to booked meeting. Each stage gets a target and an owner who reviews it weekly.
Notes cannot be audited; states can. A monthly review of the pipeline by state tells you whether a drop is a sourcing problem, a routing problem or a conversion problem, and who owns the fix.
Frequently asked
A lead is qualified when it matches the ideal profile, the budget aligns, and a meeting is booked. Everything else is either pending or disqualified — never a vague middle state that nobody owns.
Yes, but the change is recorded as a new event rather than overwritten. The audit trail shows what changed and when, which is the whole point of using states instead of free-text notes.
Pending is the correct answer. A pending entry needs a specific question to resolve, a deadline and an assigned owner, and it cannot survive past 72 hours without a new event on the record.
Written by Anikaay Integration. We build lead generation, automation and AI systems for businesses that need measurable results rather than marketing claims.