Call dispositions: a short taxonomy that stays useful
Published
Ryan Erkal
Founder, Redialler
Call dispositions are structured labels for what happened on an attempt and what should happen next. They work when they stay separate from technical call status and sales stage. A short taxonomy with clear definitions lets reps choose one result, route the next action, and keep reporting and do-not-call suppression accurate.
1. Separate disposition, call status and sales stage
A call disposition is the business result of one attempt. A technical call status is the provider's transport state, such as ringing, in-progress, completed, busy, failed or no-answer. A sales stage is the record's wider lifecycle position. One call can have one value in each category.
Twilio says a completed call can mean a person, an IVR or voicemail answered and audio was transferred. That status does not tell you whether the intended contact spoke, showed interest or asked not to be called. Keep the provider status for operations and use a disposition for the rep's observed result.
A sales stage should change only when the mapped business rule calls for it. “Callback requested” can leave a lead in the same stage while creating an owned task. “Interested” can move a stage while also creating a follow-up. “Do not call” must activate suppression even if a stage value is also written.
2. Use a small taxonomy with mutually exclusive definitions
A useful taxonomy gives each attempt one primary result and one next action. The definitions must answer the same question every time: what is the strongest verified thing that happened, and what must the team do next? Avoid options that describe different layers, such as “connected decision maker” beside “interested”, unless the form has separate fields.
Keep technical failures out of a human conversation bucket. If a provider error prevented a call, keep that technical state or route it to operations. If a person answered but no more specific verified disposition applies, use Connected with a note that says what remains unknown. Connected is the fallback, not a second label to combine with Interested, Callback requested, Not interested or Do not call.
The eight examples below are a starting point for an outbound team. They are design guidance, not an Attio default taxonomy. Each example has one definition and one next action so a rep can choose it without inventing a private interpretation.
3. Define eight outcomes and their next actions
Connected means the intended person answered and a live conversation took place, but no more specific verified disposition applies. Next action: save a short factual note and keep the record at its current stage unless a written rule says otherwise. Do not use Connected merely because the provider returned completed.
Interested means the person expressed a relevant need or asked to continue. Next action: create the agreed follow-up or meeting task, then move the stage only under the team's written rule. It is not a promise that a deal will close.
Callback requested means the person asked for contact at a stated future time. Next action: save the exact date, local timezone and owner, and create or update one linked callback task. A vague “try later” needs clarification before it becomes a dated commitment.
Not interested means the person declined the offer without a request to stop calling. Next action: record the reason when appropriate and follow the team's policy for whether a later, permitted touch remains eligible. Do not treat it as Do not call by assumption.
No answer means the intended person did not answer before the call ended. Next action: follow the attempt policy or leave the record pending without creating a conversation note. Do not claim that a voicemail was left unless the rep knows it happened.
Left voicemail means the rep reached voicemail and left a message. Next action: record the message purpose and the permitted next attempt, if any. Keep this separate from No answer so the team can tell an unanswered ring from a deliberate message.
Wrong number means the number reached someone or a service that is not the intended person, or the number is invalid. Next action: pause the number from calling work, route the record for correction, and preserve the evidence. Do not keep the suspect number callable while waiting for review.
Do not call means the person or authorized source requested no further calls from the organization. Next action: write the request to the durable suppression process immediately, record its source and time, and keep the number out of future queues. If a human answer includes an opt-out, the final disposition is Do not call, not Connected or Not interested.
4. Pair every outcome with required fields
Keep the required form small. Every outcome should carry the call ID, record ID, provider status, timestamp, selected number and rep. Connected, Interested and Not interested need a factual note. Callback requested needs a due date, timezone and owner. Wrong number needs a correction route. Do not call needs the suppression source and effective time.
Map each disposition to a writable CRM field after checking the field type and options. Attio record updates use a specific record ID and require record and object configuration permissions. A list-based call can also need a list entry ID because the list entry may hold a campaign outcome or stage that is separate from the Person.
Do not put all next actions in the disposition label. Use a linked task for owned work and a durable suppression record for opt-outs. A free-text note can explain the event, but it should not be the only control that prevents another dial.
5. Train reps on ambiguous cases
Train from short examples, not a long glossary. Ask reps to identify the strongest verified event. A busy signal remains a technical provider status and does not silently add a ninth business disposition. A recorded message left after the beep is Left voicemail, not merely Connected. An IVR that answered is a provider connection, but it is not a human Connected disposition unless the intended person spoke.
Teach the opt-out rule as a hard stop. If a human answer says “please do not call me again”, the rep records Do not call, confirms the number, and sends it to suppression. The rep does not also report a successful Connected outcome as the final disposition and does not add the number to a later callback list.
Run calibration sessions with a small set of anonymized call descriptions. Have two reps choose outcomes independently, discuss only the definitions, then update the policy when the same ambiguity repeats. Keep the final descriptions visible beside the picker.
6. Audit missing outcomes and taxonomy changes
Review calls with no disposition, conflicting status and outcome, missing next action, or a failed CRM writeback. Start with counts by provider status and disposition. A rise in Completed with a fall in Connected can mean the team is recording transport events instead of conversations. A rise in Do not call without matching suppression rows is an operational incident.
When you add, rename or retire a value, record the effective date and mapping. Decide how historic reports should treat the old value, and test the new option on one controlled record. Attio select values must exist in the target field, and a retry should not silently write a stale label.
Rate limits also need a clear retry rule. Attio documents a 429 response with Retry-After and says that request was not processed. Wait for the reset, retry the same operation, and use an operation marker when a create response is uncertain. For list preparation and field checks, pair this guide with the linked guide about preparing an outbound calling list.
Sources and review
Reviewed 2026-09-08. Product details and provider policies can change.
- Call resource (checked 2026-09-08)
- Update a person Record (checked 2026-09-08)
- Handling rate limits (checked 2026-09-08)
- Complying with the Telemarketing Sales Rule (checked 2026-09-08)
- Outcomes (checked 2026-09-08)
- Calls (checked 2026-09-08)