Call Disposition Codes: A Practical List for Sales and Reception Teams

DialSwarm team · October 17, 2026 · 4 min read

What a call disposition is

A call disposition is the label you put on a call after it ends to record what happened. "No answer." "Left voicemail." "Booked meeting." "Not interested." Each label is a disposition code.

Dispositions sound like admin, and they are. But they are also how your team knows what to do next with every lead, how your reports know what is working, and how stop requests get honored. A sloppy disposition list creates sloppy follow-up.

Why a short list beats a long one

Many teams start with a short list and keep adding codes until there are 30 of them. Then reps pick whatever is closest, or always pick the same one, and the data becomes useless.

A good disposition list is:

• Short. Ten to fifteen codes covers most teams.
• Mutually exclusive. Each call fits exactly one code.
• Action-oriented. Each code tells you what happens next.
• Consistent across reps, AI agents, and tools.

If you need more detail, add a notes field rather than another code.

Core disposition codes for outbound sales

Here is a starting list. Rename to match your language.

Not connected - No answer. Rang out with no voicemail left. Next: retry per schedule. - Left voicemail. Next: retry per schedule. - Busy or failed. Line busy or call did not complete. Next: retry later. - Wrong number. The number does not belong to the lead. Next: remove the number, find a correct one if consent allows. - Disconnected. Number not in service. Next: remove the number.

Connected - Bad time, call back. Lead asked for a callback. Next: schedule at the time they gave. - Transferred to rep. Warm transfer completed. Next: rep owns follow-up. - Meeting booked. Next: confirm and prepare. - Not interested. Next: close the lead or move to long-term nurture if they agreed to it. - Not a fit. Does not meet your criteria. Next: close politely. - Already a customer. Next: route to the account owner. - Stop calling. Lead asked not to be called again. Next: see the next section.

Disposition codes for inbound and reception

Inbound calls need different labels:

• New inquiry, message taken. Next: callback per priority.
• Urgent, flagged. Next: callback right away.
• Existing customer, service request. Next: route to service.
• Appointment request. Next: schedule.
• Billing question. Next: route to billing.
• Vendor or sales call. Next: route or ignore.
• Spam or wrong number. Next: none.
• Returned call. A lead calling back after your voicemail. Next: route to the rep who called.

DialSwarm's AI reception answers after hours or when you miss a call, takes a clear message, and flags urgent ones, which maps naturally onto codes like these.

Codes that must trigger an action

Some dispositions are not just labels. They are instructions that must be carried out.

Stop calling. This one matters most. When a lead asks not to be called again, the disposition must remove them from every call schedule, add them to your internal do-not-call list, and reach every system that might call them. Current FCC rules allow up to ten business days to honor reasonable revocation requests (Kelley Drye summary of the FCC's revised revocation rules, accessed Oct 17, 2026). Act immediately anyway. DialSwarm agents honor stop requests on the call.

Wrong number and disconnected. Remove the number so you do not keep calling someone who is not your lead. A wrong number reaches a person who never agreed to hear from you.

Already a customer. Route to the account owner and stop sales sequences, so customers do not get prospecting calls.

Meeting booked. Stop any active call sequence so the lead does not get another attempt after agreeing to meet.

Build these actions into your workflow, not just reps' memory. In DialSwarm, call outcomes are logged in call history and sync to HubSpot. You can use webhooks, Zapier, or Make to trigger actions in other tools based on outcomes.

Using dispositions in reports

With clean dispositions, useful reports become easy:

• Connect rate by lead source and time of day: connected codes divided by all attempts.
• Transfer rate: transferred to rep divided by connected calls.
• Meeting rate: meetings booked divided by connected calls.
• Stop rate: stop calling divided by connected calls. A high number suggests your sequence or opening needs work.
• Data quality: wrong number and disconnected divided by all attempts. A high number means your list needs cleaning.

Review these monthly. If one code dominates, like "not interested" for a particular lead source, dig into those calls.

Keeping it consistent

• Write a one-line definition for each code and share it.
• Make AI agents and human reps use the same list.
• Review a sample of dispositions monthly for accuracy.
• Retire codes nobody uses.

AI calls should only go to people who agreed to be called. The FCC confirmed in February 2024 that AI-generated voices are artificial voices under the TCPA (FCC Declaratory Ruling FCC-24-17, accessed Oct 17, 2026). DialSwarm bills connected calls only, so unanswered dials don't count. You get 10 free calls with no card, and current plans are on the pricing page.

Dispositions for AI calls

When an AI agent makes calls, the same codes apply, and consistency matters even more because volume is higher. Make sure the agent's outcomes map to your code list exactly, so reports combine human and AI calls cleanly. Review a sample of AI-dispositioned calls each month, just as you would for reps. If the agent marks a call "not interested" when the lead actually asked for a callback, adjust its instructions.

Common disposition mistakes

• Using "other" as a catch-all.
• Separate codes for nearly identical outcomes.
• Codes that describe feelings, like "seemed annoyed," instead of outcomes.
• No code for stop requests, so they hide in notes.
• Never reviewing whether reps use codes correctly.

Questions