A call disposition is a short label that an agent assigns to a phone call after it ends, summarizing what happened. Think of it as a tag: “left voicemail,” “sale completed,” “caller requested refund,” or “wrong number.” Every call gets exactly one disposition, creating a searchable record that the team can use to spot trends, trigger follow-up actions, and measure performance.
How Call Dispositions Work
At the end of a call, the agent selects a disposition from a predefined dropdown list inside the phone system or CRM. The selection is typically required before the agent can move on to the next call. That single tag then becomes part of the contact’s history, and in many setups it also feeds into reports and automated workflows.
Dispositions serve both inbound and outbound calling. A customer service team might use labels like “billing question,” “complaint,” “refund,” or “requires escalation.” A sales team might use “demo scheduled,” “not interested,” “callback requested,” or “no answer.” The labels differ, but the purpose is the same: turn every conversation into a data point the business can act on.
Common Disposition Codes
Most organizations draw from a mix of these standard categories, customized to fit their workflow:
- Billing question
- New order
- Product question
- Complaint
- Refund
- Cancellation
- Callback requested
- Call transfer
- Requires escalation
- Requires follow-up
- Not interested
- No answer
- Left voicemail
- Caller hung up / line dropped
- Wrong number
- Do not call
Sales-focused teams often add outcome-specific labels like “demo completed,” “proposal sent,” or “closed-won.” Support teams might add “issue resolved” or “warranty replacement.” The key is that each label maps to a clear, distinct outcome so there’s no confusion about what it means.
Why Dispositions Matter for Reporting
Disposition data feeds directly into the metrics managers use to run a call center or sales floor. When every call is tagged, you can calculate things that would otherwise require manual review of call recordings.
First-contact resolution (FCR) is one of the most watched numbers in customer service. It measures what percentage of callers had their issue solved on the first call, without needing to call back. You calculate it by dividing the total calls resolved on the first attempt by the total calls received. If your disposition list distinguishes “issue resolved” from “requires follow-up” or “requires escalation,” FCR practically calculates itself.
Repeat call rate works in the opposite direction. It tracks how often customers call back about the same issue, which highlights problems your team isn’t solving cleanly the first time. Dispositions make it easy to filter repeat contacts by topic and identify patterns, like a recurring billing error or a confusing product feature.
Managers also use disposition data to understand the mix of call types their team handles. If 40% of incoming calls are tagged “billing question” and only 10% are “complaint,” that tells you something about staffing needs, training priorities, and where self-service tools might reduce volume. Seeing these breakdowns over time reveals whether a new product launch is generating more support calls or whether a policy change actually reduced cancellations.
Triggering Automations in Your CRM
One of the most practical uses of dispositions is kicking off automated workflows the moment an agent logs a result. Most modern CRMs, including HubSpot, Salesforce, Pipedrive, and Zoho, support this.
Here’s what that looks like in practice. A sales rep finishes a product demo and selects “demo completed” as the disposition. That tag automatically triggers the CRM to send the prospect a follow-up email with next steps and moves the deal to the next pipeline stage. No one has to remember to do it manually.
The same logic works for filtering contacts. If a rep logs “do not call” as the disposition, the CRM can automatically remove that contact from future outbound call lists. If “left voicemail” is selected, a workflow might schedule a follow-up attempt three days later. The disposition becomes the starting signal for whatever should happen next, which reduces the chance of leads falling through the cracks or compliance rules being broken.
Do Not Call Compliance
Speaking of compliance, dispositions play a specific role in telemarketing regulations. Under the Telephone Consumer Protection Act (TCPA), businesses that make outbound calls must maintain an internal do-not-call list, honor opt-out requests within 30 days, and keep those numbers on the list for five years. Employees need to be trained on the process, and there must be a written procedure for maintaining the list.
A “do not call” disposition code is the front line of that process. When a prospect says “stop calling me,” the agent tags the call with that disposition, and the system should automatically flag the number. Without a reliable disposition workflow, it’s easy for opt-out requests to get lost, and the penalties for calling someone who asked to be removed can be significant.
Designing an Effective Disposition List
A poorly designed list creates bad data. If agents can’t find a label that fits, they’ll pick whatever is closest or default to a catch-all like “other,” which tells you nothing. A few guidelines keep the list useful.
Keep the total number of options at or below 20 per interaction type. More than that and agents waste time scrolling, or worse, pick the wrong one because they’re rushing. Each disposition should represent a single, specific outcome. Avoid overlapping labels: if you have both “billing inquiry” and “general inquiry,” agents will split similar calls between them inconsistently, and your data becomes unreliable.
Use full, descriptive names rather than abbreviations or acronyms. “CSAT Esc” might make sense to the person who built the list, but it confuses new hires and any AI tools analyzing the data. “Customer satisfaction escalation” is clearer. Along the same lines, skip vague parent categories. Having both “financial inquiries” and “billing question” on the same list creates ambiguity about which one to choose.
Each disposition should come with a short written description that explains exactly what qualifies. Instead of just “complaint,” define it as “complaint about product quality” and spell out the criteria. This keeps tagging consistent across a team of dozens or hundreds of agents. And design the list so only one disposition applies per call. If an agent could reasonably pick two or three labels for the same interaction, the categories need to be reworked.
Finally, avoid dispositions based on information that isn’t part of the conversation itself. Labels like “VIP customer” or “West region” depend on system metadata, not what the agent heard on the call. Those belong in separate CRM fields, not the disposition list.
Getting Value From Disposition Data
The real payoff comes when dispositions are logged consistently over weeks and months. You start seeing which products generate the most support calls, which sales objections come up most often, and whether your first-contact resolution rate is improving or slipping. Teams that track dispositions rigorously can reallocate staff based on actual call mix data, build targeted training around the most common escalation reasons, and identify process failures before they become customer retention problems.
If you’re setting up dispositions for the first time, start with a short list of 10 to 15 codes that cover your most common outcomes. Review the data monthly, and adjust the list when you notice agents consistently picking “other” or when a new call pattern emerges that doesn’t have a label. The list should evolve with the business, but changes should be deliberate so your historical data stays comparable.