What Is Service Level at a Car Dealership's Phone System?
Service level measures the percentage of calls answered within a set time threshold, not an average wait time. Here is how it's calculated, how it differs from answer rate and average speed of answer, and what a realistic target looks like.
Service level is the percentage of inbound calls answered within a set time threshold, commonly twenty to thirty seconds. It is a target-based metric, not an average. A store either hits its service level goal for a given period or it does not, with nothing in between.
Dealermate is an AI call facilitation platform for Canadian automotive dealerships. Most phone systems and BDC platforms can report service level, but few dealerships set an actual target for it. The number tends to sit unused next to answer rate and call volume on a dashboard nobody checks closely.
How Service Level Is Calculated
Service level is the count of calls answered inside the threshold, divided by the total number of calls offered, over a chosen period. It is usually written as a pair, such as "80/20," meaning 80 percent of calls answered within 20 seconds. The pairing is borrowed directly from general call center practice, where it originated as a staffing planning tool rather than a customer experience score.
The threshold is a choice, not a fixed standard. Some phone systems default to twenty seconds, others to thirty, and a few let a store set any number it wants. Two dealerships can both report "90 percent service level" while using thresholds ten seconds apart, which makes the raw figure hard to compare across stores unless the threshold is stated alongside it.
Service Level, Answer Rate, and ASA Are Not the Same Metric
These three numbers get used interchangeably in casual conversation at a dealership, but each one answers a different question.
| Metric | What it measures | What it misses |
|---|---|---|
| Service level | Share of calls answered within a fixed threshold | Says nothing about calls answered just outside the threshold |
| Answer rate | Share of calls that connected to a person at all | Ignores how long the caller waited to get there |
| Average speed of answer | Average wait time across answered calls only | An average can look fine while a chunk of calls wait far longer |
A store can post a strong answer rate and a passable ASA while still failing its service level target, because a meaningful share of callers waited past the cutoff before someone finally picked up.
Why a Hard Threshold Reveals More Than an Average
An average wait time can hide a pattern that matters more to the person on the phone: whether their specific call happened to land during a calm minute or a backed-up one.
A caller does not experience the average. They experience their own wait, and they either got someone before they were ready to hang up or they did not.
Two identical days can produce the same ASA with very different service level outcomes. One day might have wait times spread evenly around fifteen seconds. Another might have most calls answered in five seconds with a smaller cluster left waiting well past a minute during a single busy stretch. The average looks similar. The threshold-based service level number exposes the second pattern, because it counts how many calls actually cleared the bar rather than smoothing them into one figure.
Where Service Level Slips at a Dealership
Service level is not steady across a service day. It tracks the same predictable windows that drive most call coverage problems: the morning write-up period, the lunch rotation, and Saturday mornings, when advisor and BDC availability drops at the exact moment call volume rises.
A dealership measuring service level only as a daily or weekly average will not see this. The number can look acceptable in aggregate while a specific hour of the day consistently misses the target, because the good hours in the same period pull the blended figure back up. Service level is only useful when it is checked against the abandonment rate for the same window, since a high abandonment rate during a low-service-level hour is usually the same underlying gap showing up in two different numbers.
Setting a Realistic Service Level Target
General call center guidance points to an 80/20 threshold as a common industry default, though it was built around centralized contact centers rather than a dealership's mixed sales, service, and parts call mix. Dealership-specific benchmarking data is limited, so 80/20 is best treated as a reasonable starting reference rather than a number to defend without adjustment.
What matters more than the specific target is whether a store tracks service level by hour rather than only by day. A single daily figure hides exactly the windows where a service level target is most likely to be missed.
Frequently Asked Questions
What is service level at a car dealership? Service level is the percentage of inbound calls answered within a set time threshold, commonly twenty to thirty seconds, over a chosen period. It is a target-based figure rather than an average.
What is the difference between service level and answer rate? Answer rate measures whether a call eventually connected to a person, regardless of how long the caller waited. Service level measures whether the call was answered within a specific time cutoff, so a call can count toward answer rate while still failing service level.
What is a good service level for a dealership phone system? General call center guidance treats an 80/20 threshold, meaning 80 percent of calls answered within 20 seconds, as a common default. Dealership-specific data is limited, so this is best used as a starting reference and checked hourly rather than only as a daily average.