Call dispositions are the handoff between a phone attempt and the work that follows. The record should tell the next person what happened, where the lead stands overall, and what should happen next, with each point recorded separately.1 A single label cannot do all three jobs well. Keep them separate, then use the patterns to find where calls are failing and what to change. That turns a checkbox into a feedback loop.
Define the fields
Before building the menu, give each field a clear job so the person filling the record knows what belongs in the outcome, relationship, and follow-up fields.
Use labels that describe what happened clearly enough to guide the next action.2 Treat the examples as suggested operating labels for your campaign, separate from default fields in a particular platform.3 Adapt them to the campaign and test them in the setup you use.4
A call result describes one attempt.5 A lead stage summarizes the broader relationship.6 A task describes future work.7 Treating these as the same field can make the record misleading.8
The latest call can be unanswered while the lead still has an active evaluation, so the call result should not overwrite the broader lead stage.9
Capture the call
Close every call by recording the outcome while the details are fresh. Leave a usable record for whoever reviews the account or takes the next action.
People who follow the sales process select a disposition at the end of every call.10 A practical menu can include "left voicemail," "not interested," "connected," and "meeting booked".11 Choose the label that describes the call you just finished. Update the lead stage and task fields only when those fields have changed. The result can feed reporting while the stage and task preserve the wider context.
Separate relationship from follow-up
Use the lead stage to preserve the account's position over time. Use the task to state what someone needs to do next, without putting either meaning into the call result.
If the latest call goes unanswered during an active evaluation, retain the evaluation in the lead stage.9 Changing the overall stage to "no answer" hides that ongoing evaluation.12 The task can carry the next attempt or agreed follow-up, while the call result records the unanswered attempt.
The review should show what happened on the attempt, where the lead stands, and what work follows. A call marked "connected" still does not show whether the prospect requested further action.13
Read the analytics
Read the report from activity to reach, conversation, and outcome. That order helps you locate the part of the call motion that needs attention.
A dial is an outbound call attempt logged in the dialer, with one number counted per dial regardless of outcome.14 Connect rate is live connects divided by all dials.15 Measure that rate by week and campaign so a total does not hide a weak segment.16
Use Calling to review calls made, overall answer rate, human or target pickup rate, qualified conversation rate, speed to talk, meetings from calls, cumulative call depth, and available caller-ID or destination scorecards.17 Qualified Conversation is a client-performance metric that includes Referral, Not Interested, and Unqualified outcomes.18 Call analytics can report connect rate and talk time, and provide disposition reporting.19
Check coverage before reading averages. Call coverage is the share of the active roster with at least one call, and the average uses contacted leads only.20 That keeps an average from being read as a measure of the whole roster.
The disposition records should appear on a report that lets you see the mix of outcomes.21 A pie chart can show how often each disposition occurs.22 Segment that view by industry or persona when you need to find where the pattern changes.23
Basic outcome labels do not explain why a campaign is underperforming.24 Use the segment view to compare reach, conversation, and meeting outcomes across the groups you are calling. When connect rate falls while call volume holds, inspect reach by segment. When qualified conversations fall while connects hold, inspect what happens inside the conversation. When meetings from calls fall while conversations hold, inspect the follow-up task.
Turn patterns into changes
Use analytics to decide what to inspect next. Match each pattern to the field or step that could explain it, then test the change against the same outcome view.
A reach problem belongs in the connect-rate and campaign view. A conversation problem belongs in qualified conversation and talk-time data. A follow-up problem belongs in meeting and task records. Keep the diagnosis attached to the field that can show whether the change worked.
Review the result after enough activity has accumulated to reveal a pattern, then change one part of the call motion. If the pattern points to a particular industry or persona, keep that segment visible in the next review. If it cuts across segments, inspect the common call result and follow-up process.
What not to do
Keep these failure modes out of the workflow:
- Most teams treat dispositioning as annoying but necessary bookkeeping.25
- A label such as "good call," does not say whether the intended person was reached, a question was answered, or a callback was agreed.26
- Treat "connected" as proof that follow-up exists. The label only says that a line picked up.27
- A disposition report has a problem when it tells you only what already happened.28