Key takeaways
- A practical outbound set has about a dozen codes, and each one should lead to a different next step: a retry, a follow-up, a pipeline change or removal.
- Since October 15, 2024, the Telemarketing Sales Rule has required sellers to record how each telemarketing call ended, among other call details, and keep the record for five years.
- A Do Not Call disposition must stop future calls to that number for the whole team, not only for the rep who took the request.
- Rapidialer starts every team with eight outcomes and allows up to 20 outcome buttons, each mapped to one of the eight for reporting.
Call disposition codes are the short labels a rep picks when a call ends: they record what happened and decide what happens next. A practical outbound set has about a dozen codes: Connected, Meeting booked, Callback, Not interested, No answer, Voicemail, Busy, Wrong number, Disconnected, Gatekeeper, Not the decision maker and Do not call, plus a rarely used Other. Keep them mutually exclusive and tie each one to a next step.
This guide gives the list, the action each code should trigger, a way to design your own set and the records US telemarketing rules expect. For the definition on its own, see what is a call disposition.
Which call disposition codes should an outbound team use?
Start with the thirteen below. They cover every way a sales call can end, and each leads to a different action, which is the test a code has to pass. Rename them to suit your team, but keep the split between reached and not reached: a reached code means a conversation happened and needs a next step, while a not-reached code feeds the retry queue and your connect rate.
| Code | Use it when | Reached a person? | What happens next |
|---|---|---|---|
| Connected | You spoke with the right person | Yes | Log notes; set a follow-up if there is a next step |
| Meeting booked | The person agreed to a meeting or appointment | Yes | Send the invite; move the lead forward |
| Callback | They asked you to call at a specific time | Yes | Schedule the call for that time |
| Not interested | They declined | Yes | Stop calling for this campaign |
| Gatekeeper | Someone screened the call | Yes | Note their name; retry or ask for a better time |
| Not the decision maker | You reached the wrong person at the right company | Yes | Ask for a referral; update the contact |
| Do not call | They asked not to be called again | Yes | Add the number to your do-not-call list at once |
| No answer | Nobody picked up | No | Retry later, at a different time of day |
| Voicemail | The call reached voicemail | No | Retry later; note whether you left a message |
| Busy | The line was busy | No | Retry soon |
| Wrong number | The number does not reach this contact | No | Remove the number; look for a better one |
| Disconnected | The number is not in service | No | Remove it from the list |
| Other | Nothing above fits | Depends | Require a note, and review these every week |
The third column is what makes the set useful for reporting: reach rate becomes the reached codes divided by dials, with nothing left to argue about.
How do you design a disposition set reps will actually use?
Design from decisions, not descriptions: every code should trigger a retry, a follow-up, a stage change or removal. If two codes lead to the same action and the same report, merge them.
- Keep it short. Six to twelve codes cover most outbound calling. A long list slows wrap-up, and reps start picking whichever button is nearest.
- Make codes mutually exclusive. Every call should fit exactly one. “Interested” and “Callback” overlap, so decide which one wins and write it down.
- Separate reached from not reached. Each code belongs clearly to one side.
- Treat Do not call as sacred. It must stop future calls to that number for the whole team.
- Watch Other. If more than a small share of calls end there, a code is missing; read the notes and add it.
- Review monthly. Read a sample of notes behind each code, then rename or split the codes reps use inconsistently.
- Put the codes in reach. One click or one key per code, in the same order every time, keeps wrap-up to seconds.
The spacing between attempts belongs to your retry rules, not to the codes themselves; how many times to call a lead suggests a starting cadence for each kind of lead.
How should custom codes map to standard ones?
Teams often want labels in their own language, and that works as long as each custom code maps back to a standard one. The mapping keeps reports comparable across teams, campaigns and months, even when the wording on the buttons changes.
| Team | Custom code | Maps to |
|---|---|---|
| Real estate | Listing appointment | Meeting booked |
| Real estate | Already listed with an agent | Not interested |
| Insurance | Quote requested | Connected |
| Insurance | Has coverage, renews in March | Callback |
| Recruiting | Interested in the role | Connected |
| Recruiting | Not looking right now | Not interested |
| SDR teams | Referred to a colleague | Not the decision maker |
| Solar | Renter, not the owner | Wrong number |
A custom code can also carry its own action. “Listing appointment” might move the lead to an Appointment stage in your pipeline, while the report still counts it as a booked meeting. Keep a short glossary of what each custom code means, so a new rep learns the set in an afternoon.
What numbers do dispositions give you?
Dispositions turn a calling session into data you can manage. With an outcome on every dial, five ratios fall out of the same table and point at five different fixes.
- Reach rate: reached outcomes divided by dials. A low rate points at timing or list quality; cold call connect rate benchmarks show how published studies define the same number.
- Conversion: meetings booked divided by people reached. A low rate points at the script or the offer.
- Wrong and disconnected rate: a direct measure of list quality, worth tracking for each list source.
- Voicemail rate: a high share often means you are calling at hours when people are away.
- Do-not-call rate: a rising share is an early warning about list sourcing or tone.
Compare each ratio by list, by rep and by hour of the contact’s local time. A list with a high wrong-number rate needs cleaning; a rep with a low conversion rate needs coaching; an hour with a high voicemail rate needs dropping. In Rapidialer, call analytics report these by rep and list, with a best-time-to-call heatmap.
What records do US telemarketing rules expect?
If your calls are covered by the FTC’s Telemarketing Sales Rule, keep a record of each telemarketing call for five years. The rule lists what the record must include: who placed the call and for which seller, the calling and called numbers, the date, time and duration, the script or prerecorded message used, the caller ID shown, and how the call ended, including whether it was answered, dropped or transferred (16 CFR 310.5). There is one carve-out: “for calls that an individual telemarketer makes by manually entering a single telephone number to initiate the call to that number,” the seller or telemarketer need not keep the calling and called numbers, date, time and duration, or the disposition (16 CFR 310.5(a)(2)). Calls a rep dials by typing a single number are exempt from the call-detail and disposition items; calls a dialer places from a list don’t fit that wording, so keep the full record for them. Compliance with that call-record requirement began on October 15, 2024 (Federal Register).
A consistent disposition set covers the “how it ended” item and makes the rest easier to search. It doesn’t cover everything: keep your call logs, scripts and caller-ID records too. A rule of the same kind applies to do-not-call requests, which must be honored whatever code a rep chooses. Rule text checked November 2026. This is general information, not legal advice; ask counsel which rules apply to your calls.
How do disposition codes work in Rapidialer?
Rapidialer calls them call outcomes. Every team starts with eight: Connected, No answer, Voicemail, Callback, Not interested, Wrong number, DND and Other. Owners and admins can rename and reorder them and add their own, up to 20 buttons in total, each mapped to one of the eight for reporting and optionally set to move the lead to a pipeline stage. Number keys 1 to 9 pick the first nine.
Each standard outcome does a job:
- Callback creates a follow-up for the date and time the rep picks.
- DND adds the number to your organization’s Do Not Call list, closes the lead’s open list entries and cancels its open follow-ups.
- Wrong number takes the contact out of the list queue.
- No answer, Voicemail and Other can come back automatically with retry rules, after a delay you set for each.
- Connected and Callback count as connects in analytics, and list funnels also count Not interested as reached.
Power Dial doesn’t start the next call until an outcome is logged, so every call reaches your reports. If the organization adds its own Deepgram and AI provider keys, AI call summaries also suggest an outcome, which the rep confirms.
When is Rapidialer not the right fit for dispositions?
Pick something else if your dispositions must reach a system it has no connector for without any setup: Rapidialer syncs calls natively to HubSpot, Salesforce, Pipedrive, Close and Zoho CRM, and sends other tools signed webhooks or a CSV export. It also isn’t built for nested, multi-level disposition trees of the kind large contact centers use for inbound support; outcomes are one flat list of up to 20 buttons.
Questions and answers
What is a call disposition code?
A call disposition code is the label a rep picks when a call ends to record what happened, such as Meeting booked, Voicemail or Wrong number. The phone system knows whether a call rang or connected; only the rep knows the business result. The code turns that result into data, and in a good dialer it also decides what happens next to the contact.
How many disposition codes should a team have?
Usually six to twelve. Keep enough to separate every outcome that leads to a different next step, and few enough that a rep can pick one in a second or two without scrolling. If two codes lead to the same action and the same report, merge them; if more than a small share of calls end in Other, a code is missing.
What is the difference between a disposition and a call status?
A call status comes from the phone network: ringing, answered, busy, no answer or failed. A disposition comes from the rep and records the business result, such as a meeting booked or a request not to be called again. Good reporting uses both, because a call the network marks answered can still be a voicemail or a gatekeeper.
Should voicemail and no answer be separate codes?
Yes, if you retry them differently or need to know whether a message was left. Many teams bring no-answer contacts back the same day at a different hour, and voicemails a day or two later so the message has time to work. Separate codes also show whether you are calling at hours when people are away from their phones.
Which disposition codes count as a connect?
Count the codes where a live person picked up: Connected, Meeting booked, Callback, Not interested, Gatekeeper, Not the decision maker and Do not call. Some teams count only conversations with the right person, so write your rule down before you compare reports. Connect rate is the reached codes divided by all dials over the same period.
Do US rules require call dispositions?
For telemarketing covered by the FTC’s Telemarketing Sales Rule, yes: since the 2024 amendments, the record of each call must include how it ended, such as answered, connected, dropped or transferred, kept for five years. Calls a rep places by manually entering a single number are exempt from the call-detail and disposition items; dialer-placed calls are not (16 CFR 310.5(a)(2)). This is general information, not legal advice.