What Is a Call Disposition Code at a Dealership BDC?

A disposition code is the label a BDC agent or the phone system assigns to a call once it ends, describing the outcome: booked, no answer, price shopper, wrong number, callback requested. It is the raw material behind almost every phone report a dealership runs.

Dealermate is an AI call facilitation platform for Canadian automotive dealerships. Disposition codes rarely get attention on their own. They sit underneath metrics like answer rate and first call resolution, and when the code list is thin or applied inconsistently, every report built on top of it inherits the same gap.

How Disposition Codes Work

At the end of a call, whoever handled it, an agent, an advisor, or an automated system, selects a code that describes what happened. That code gets written to the CRM or the phone system's call log, tied to the customer record if one exists.

A basic dealership code set typically covers a handful of outcomes: appointment booked, message taken, no answer, wrong number, and general inquiry. Some phone systems generate a subset of these automatically based on call length and transfer activity, without any human choosing them. A call under ten seconds might auto-code as "no answer" regardless of whether the caller actually reached someone and hung up during a transfer.

That auto-coding is where the first accuracy problem starts. A code assigned by call duration is a proxy for what happened, not a record of it.

Why the Code List Is Usually Too Short

Most dealership phone systems ship with a generic code set built for a general call center, not a service drive or a sales BDC. It rarely distinguishes between the outcomes that actually matter operationally.

"No answer" on a generic system does not separate a call that never connected from a call that connected, got transferred, and rang out unanswered at the destination extension. Both land in the same bucket, even though one is a phone system failure and the other is a routing failure with a different fix. What Is a Missed Call at a Car Dealership covers this same blind spot from the reporting side.

"General inquiry" often absorbs calls that should be split into distinct categories: parts pricing, service scheduling, recall questions, and sales floor traffic. When all four collapse into one code, a manager reviewing weekly volume cannot tell which department is actually driving inbound demand, and cannot staff accordingly.

A short code list is easier to train on and faster for an agent to apply mid-call. It is also less useful for anyone trying to diagnose why calls are failing.

Who Applies the Code, and When

Disposition coding happens in one of three ways at a dealership: a live agent selects it manually after the call, the phone system infers it from call metadata, or it never gets applied at all because the call did not reach anyone who could code it.

That third case is the largest reporting gap. A call that abandons during an IVR menu, or hangs up mid-hold before reaching an agent, often has no code attached because no human interacted with it long enough to assign one. These calls exist in the raw phone system log as a timestamp and a duration, but they do not show up in any report built from disposition data, since there is nothing to disposition.

A disposition code can only describe a call that someone was present to label. Every call that ends before that point is a gap in the data, not a zero in the count.

This is also why manual coding tends to degrade during peak call windows. An agent handling back-to-back calls during a Monday morning surge is more likely to apply the fastest code available rather than the most accurate one, which quietly shifts volume toward generic buckets like "message taken" even when a more specific code existed.

What a Better Code Set Looks Like

A disposition code set built for a dealership BDC, rather than borrowed from a general call center template, usually separates outcomes along two lines: what the caller wanted, and what actually happened.

Code category	Example codes
Booking outcome	Appointment booked, appointment rescheduled, no availability offered
Resolution outcome	Question resolved, callback promised, transferred and confirmed
Non-connect outcome	No answer, IVR abandonment, hold abandonment, wrong number
Intent category	Service scheduling, parts inquiry, recall, sales, general

Splitting intent from outcome, rather than mixing both into one code, is what makes the resulting reports usable. A store can then ask two separate questions: what are people calling about, and how often does each type of call end well. A single merged code set can only answer one of those at a time.

Frequently Asked Questions

What is a call disposition code at a dealership? A disposition code is a label applied to a call after it ends, describing the outcome, such as appointment booked, no answer, or general inquiry. It is the underlying data most phone and BDC reports are built from.

Who applies the disposition code? A live agent typically applies it manually after the call. Some phone systems also auto-assign a code based on call duration or transfer activity, which is less reliable than a human describing what actually happened.

Why do dealership call reports miss so much? Because disposition codes can only describe calls that someone was present to label. Calls that abandon during an IVR menu or on hold before reaching an agent often have no code attached, so they are missing from reports built on disposition data rather than counted as a failure.

How is a disposition code different from a call outcome metric like first call resolution? The disposition code is the raw label applied to one call. Metrics like first call resolution rate are calculated by aggregating disposition codes across many calls, so an incomplete or inconsistent code set weakens every metric built on top of it.

Book a call coverage review