"Called" is not data. Neither is a blank note field, a thumbs-up emoji in Slack, or a rep's confident memory of a conversation from Tuesday. If your reporting cannot answer "what happened on our calls last week" in twelve buckets or fewer, you don't have a pipeline problem. You have a taxonomy problem.
Outcome vs disposition: the distinction that fixes reporting
Two different things happen on every call, and conflating them corrupts everything downstream.
Call outcomes are network facts, detected automatically: connected, voicemail, no answer, busy, failed. They answer "did we speak to a human."
Dispositions are human judgments, confirmed by the rep in one click: conversation, booked, qualified, callback, gatekeeper, wrong number, not interested, do-not-call. They answer "what did it mean, and what happens next."
Keep both. Outcomes drive retry automation (no-answer requeues, voicemail gets an SMS). Dispositions drive pipeline (booked creates meetings, callbacks create tasks, not-interested retires the contact). The moment a rep has to type what a dropdown should say, your data is already dirty.
The twelve
- Conversation. Spoke properly, no next step agreed. Log it, move on.
- Booked. Meeting or appointment agreed. Creates the booking plus CRM task. Terminal for the campaign.
- Qualified. Real opportunity, needs proposal or next step. Creates follow-up.
- Callback. They named a time. Creates a timed task; punctuality is the tactic.
- Voicemail. Left a message. Requeues per cadence, optionally with SMS.
- No answer. Rang out. Requeues per cadence.
- Busy. Line busy. Short-gap retry.
- Gatekeeper. Blocked. Note the route in, retry with a different angle.
- Wrong number. Retire the contact. Terminal.
- Not interested. Declined for now. Retire gracefully; recycle lists quarterly, not weekly.
- Do not call. Explicit opt-out. Suppresses the number across every campaign, permanently, automatically. Legal shield.
- Failed. Technical failure. Retry without counting against attempt limits.
Ten to twelve is the workable band. Five buckets ("good/bad/VM/NA/other") destroys analysis. Thirty buckets means reps pick randomly to clear the screen. Plain words, no codes, no abbreviations a new starter must memorise.
Each disposition must trigger something
A taxonomy without automation is a survey. Wire every value: booked → calendar + CRM; callback → timed task; retryables → requeue with gap and cap; opt-outs → suppression; terminal outcomes → removal from rotation. Then measure disposition rate: the share of calls with a recorded disposition. Under 90% means reps are skipping the taxonomy, and every downstream number is fiction. Above 95% with a ten-option list means the system is working.
Ringby ships this taxonomy built in, with the triggers wired: dispositions requeue, raise tasks, suppress opt-outs and sync to HubSpot. See how it works.