What service advisors do all day — and how to get 30 minutes back per shift

The typical 8-hour advisor day, broken down

Spend a Tuesday standing behind a service advisor with a stopwatch, and the breakdown looks roughly like this. Numbers below are averages from time-and-motion observations across stores running 12-18 ROs per advisor per day.

Activity	Time per shift	% of 8 hours
Customer greeting & walk-around	50 min	10%
RO authoring (write-up in DMS)	2 hr 15 min	28%
Parts coordination & lookup	40 min	8%
Status calls & customer follow-up	55 min	11%
Cashier handoff & key return	35 min	7%
Tech consultation (price-up, additional work)	40 min	8%
Queue management (the topic of this post)	30-45 min	6-9%
Manager / huddle / unproductive interruptions	25 min	5%
Lunch and breaks	50 min	10%

The numbers don't add to exactly 8 hours because real shifts always overflow; advisors stay 15-30 minutes past close to finish ROs. The interesting row is the queue-management one, because nobody writes it on the work schedule. It just happens.

The queue-management tax

"Queue management" is the term we use for everything an advisor does that isn't actually working an RO but is required because the store doesn't have a real queue. Specifically:

1. Figuring out who's next

If your store runs paper sign-in or first-come-first-served, every time an advisor finishes a customer they have to figure out who's next. This means glancing at the sign-in sheet, scanning the lobby, sometimes asking the receptionist. Average time per occurrence: 60-90 seconds. If your advisor handles 15 customers per day, that's 15-22 minutes/day on this single task.

2. Walking the lobby to find the customer

Once you know it's "Mr. Patel next," you have to find Mr. Patel. He might be in the lobby. He might be in the lounge. He might be standing outside on a phone call. Some stores have an intercom; most don't. Average time per occurrence: 90-120 seconds. Across 15 customers, that's another 22-30 minutes.

3. Fielding "how much longer?" questions

A customer in the lobby with no information about their wait will ask the advisor. Often more than once. Each interruption is 30-90 seconds, and worse, it pulls the advisor out of whatever they were doing — which has its own context-switching cost. Conservative estimate: 8-12 minutes/day per advisor.

4. Handling escalations from frustrated customers

When wait times stretch, customers don't blame the tech. They blame the advisor. Defusing a frustrated customer is a 5-15 minute event. Most stores have at least one of these per day per advisor. Average: 8-15 minutes/day.

Add it up. The queue-management tax is 30-45 minutes per advisor per shift. In a 3-advisor store, that's 90-135 minutes/day — roughly 1.5 to 2.25 advisor-hours/day — spent on work that adds zero value to the customer or the store.

A worked example: 25 customers, 3 advisors, one shift

Here's a realistic day at a mid-size domestic store. 25 customers come through the drive across an 8-hour shift. Three advisors share the desk.

Activity	Per customer	Per advisor (8.3 customers)	Per shift (3 advisors)
Productive RO work	~16 min	~133 min	~6.6 hrs
Queue management overhead	~3-4 min	~28 min	~1.4 hrs
Customer-facing time	~12 min	~100 min	~5.0 hrs

The 1.4 hours of queue-management overhead, at a fully-loaded advisor cost of ~$40/hr (wage + benefits + payroll tax), is ~$56/day, or about $14,500/year per store. And that's just labor cost. It doesn't include the customer-experience cost of advisors looking flustered, missed upsells because the advisor was too rushed for the multi-point review, or recall captures lost because the advisor didn't have time to check the OEM portal.

The opportunity-cost angle

Now the real number. If each advisor gets 30 minutes back per shift and uses it to handle one additional RO, you've added 3 ROs/day to the store's throughput. Average gross profit per RO in 2026 is $180-280. 3 ROs × $200 = $600/day in gross profit. Across a 22-day work month, that's $13,200/mo, or roughly $158k/year per store.

This is why the productivity case for a queue platform is hard to argue against. Even if you only capture half of the recovered time as additional throughput, the math still works easily.

What changes when you put a real queue in

The activities that compose the queue-management tax don't disappear because of magic. They disappear because each one gets handled by software instead of by an advisor's brain.

"Who's next?" — answered by the dashboard

The advisor dashboard shows the queue in priority order. The advisor clicks the next customer. Time elapsed: 2-5 seconds. Net savings: 15-22 min/day.

"Where is the customer?" — handled by SMS

When the advisor is ready, they tap "Call up" on the dashboard. The customer gets an SMS: "Mr. Patel — please come to advisor desk 2." The customer arrives at the desk in 30-60 seconds. The advisor stays at their desk and starts the next walk-around. Net savings: 22-30 min/day.

"How much longer?" — answered by the lobby display

The lobby TV shows each customer their position, ETA, and (if applicable) their flagged recalls. Customers who can see their position rarely ask the advisor. The reduction isn't 100% but it's reliably 70-80%. Net savings: 6-9 min/day.

Escalations — defused before they happen

The biggest factor in escalation is a customer feeling ignored. A customer with a clear position display, an SMS thread updating them, and a manager-alert system that catches outliers before they become outliers is dramatically less likely to escalate. Escalation rate typically drops 60-75% in the first 90 days. Net savings: 5-10 min/day.

Sum: 48-71 minutes/day per advisor recovered. We round to "30 minutes" in the headline because not all stores see the full benefit and not all of the recovered time gets used for additional throughput. But the 30-min/day figure is conservative.

The impact on advisor pay

Advisors are paid two ways in most stores: a base hourly or salary, plus a commission tied to gross profit and (often) CSI. Both move in the right direction with a queue platform.

Gross profit per RO: stable to slightly up

The advisor still does the walk-around and the additional-work conversation. The queue platform doesn't change the upsell skill set. What it changes is whether the advisor has time to do the multi-point review properly. A rushed multi-point review captures fewer additional services. A well-paced one captures more.

RO count per day: up 1-3

The recovered 30-45 minutes typically translates into one to three additional ROs per advisor per day. At $200 average gross per RO, this is $200-600/day in additional gross profit through the desk, of which the advisor's commission piece is typically 8-12%, so $16-72/day in additional commission. Annualized: $4,000-18,000 per advisor.

CSI scores: up

CSI improvements after queue rollout are well-documented. A typical store sees a 4-7 point CSI lift in the first 6 months, driven mostly by reduced perceived wait time and more consistent communication. CSI bonuses, where the OEM ties them to advisor pay, kick in at this point.

Net: a queue platform is one of the few operational changes where advisor pay and store profit move in the same direction. There's no "advisor takes a haircut so the store wins" tradeoff — they both win.

Common objections from advisors

"I don't want a screen telling me who to help next"

The dashboard suggests; the advisor clicks. It doesn't auto-route customers to advisors. When an advisor wants to take a particular customer (regular, complex history, language preference), they pick that customer. The system supports the advisor's judgment, it doesn't replace it.

"My regulars expect me to greet them personally"

A queue platform helps with this, not against it. The kiosk captures the customer's preferred advisor. The dashboard shows the advisor when their regular has arrived. The advisor can call them up first or set their position manually. Advisors lose nothing on the relationship side.

"I'll lose hours if I'm faster"

This is the one to take seriously. If an advisor is paid hourly and you compress their workload by 30 minutes/day, they will (correctly) worry about losing hours. The fix is structural: either (a) they take on additional ROs and earn more commission, (b) they take on auxiliary work like follow-up calls and warranty rework that previously got skipped, or (c) for stores genuinely seasonal, they get a guaranteed-hours commitment for the rollout period. The queue rollout cannot reduce advisor take-home, full stop. If your plan does, it's the wrong plan.

"This will dehumanize the experience"

The opposite. A flustered advisor scrambling between the lobby and the desk is not a humane experience for either side. A calm advisor who has time to do a proper walk-around, ask real questions, and explain the multi-point review is the humane experience. Software handling the logistics frees the advisor to do the human work.

What to do Monday morning

1. Time-and-motion one shift. Pick your busiest advisor. Stand behind them with a phone and a notepad. Categorize every minute for one full shift. You'll see your store's actual breakdown.
2. Count the queue-management tasks. "Who's next?" lookups. Lobby walks. Repeated "how much longer?" interactions. Escalations. Tally them.
3. Multiply by your advisor count. The aggregate number is what matters. 30 min/day × 3 advisors = 1.5 hours/day. 30 min/day × 8 advisors = 4 hours/day. Different stores, different stakes.
4. Talk to the advisors. Not "we're putting in a system." Ask them where their day disappears. They'll tell you, often with more detail than your time-and-motion captured.
5. Pilot for 30 days. Pick one advisor desk. Run the queue alongside the existing process. Compare. Most stores have their answer in 2-3 weeks.

For the customer side of this same story, see our piece on the psychology of waiting. For the bay/throughput side, see bay throughput as a metric. And for the integration question — how the queue plugs into your DMS without disrupting RO authoring — see the DMS integration strategy piece.

Frequently asked questions

How many ROs should one service advisor handle per day?

The benchmark range in 2026 is 12-18 ROs per advisor per day, depending on store mix. Express-heavy advisors run higher (15-22). Main-shop advisors with longer cycle ROs run lower (8-14). Anything below 10 in a busy store usually signals a productivity problem; anything above 22 usually signals customers aren't getting full attention.

How long does writing an RO actually take?

Real RO write-up time, when measured with a timer, runs 8-14 minutes for a typical service visit. This includes greeting, walk-around, concern documentation, OEM history pull, recall check, op-code selection, customer authorization, and key handoff. The fast advisors aren't typing faster — they have systems and reusable templates.

What's the biggest hidden time-waster in an advisor's day?

It's almost always queue management: figuring out who's next, walking the lobby to find the next customer, fielding "how much longer" questions from waiting customers, and triaging escalations when waits get long. These tasks add up to 25-45 minutes per advisor per shift in a typical store, and they don't appear on any RO.

Does adding a kiosk reduce or increase advisor workload?

Net reduction. The kiosk takes the customer's name, vehicle info, and concern off the advisor's plate. The advisor still does the walk-around and write-up, but starts from a populated record instead of a blank one. Typical time savings is 2-3 minutes per RO, which compounds across a 15-RO day to ~45 minutes. See our kiosk placement piece for where to put it.

How does ClickQueue affect advisor pay?

Advisors are typically paid on gross profit and CSI. Both move in the right direction with a queue platform: more ROs per advisor (gross up), faster handling (CSI up), and less customer frustration (CSI up). We have not seen a deployment where advisor pay decreased after rollout. The most common outcome is advisors taking on 1-2 more ROs per day at the same pay rate, which translates to higher take-home. Full pricing detail is on our general FAQ.

Related reading: The psychology of waiting · DMS integration strategy · Data-driven bay routing