The service advisor workflow and where each step breaks
The eight steps of a service advisor's workflow, from the check the day before to the hand-over, where each hand-off fails and what to change.
- By
- Thilo Krause
- Published
- Reading time
- 7 min read
A service advisor's workflow has eight steps for every car: preparation the day before, check-in and write-up, agreeing the promise time, pricing what the technician finds, getting the customer's approval, keeping the customer informed, reviewing the invoice and handing the car back. The advisor owns the customer through all of it. The car itself passes through other hands at every step, and most bad days start at one of those passes. The part nobody ordered and the customer who rang at four to ask whether the car was ready both go back to a hand-off between two people.
This article goes through the steps in order, names the hand-off that usually fails at each one, and gives a fix you can try next week with the tools you already have.
The service advisor workflow in eight steps
| Step | Hands off to | What usually breaks |
|---|---|---|
| Preparation | Parts, warranty, mobility | Parts missing at 8:00 |
| Check-in and write-up | Controller, technician | Vague concern on the job card |
| Promise time | The whole workshop | Agreed once, never checked |
| Pricing findings | Advisor, parts | Findings wait for a quiet moment |
| Approval | Customer | No answer and nobody chases |
| Keeping informed | Customer | The customer calls first |
| Invoice review | Back office | Missing lines, wrong payer |
| Hand-over | Customer | Work explained in a rush |
Read down the right-hand column and the same pattern repeats. Everyone knows what the next task is. Nobody owns when it has to be done by. Most of the fixes below come down to putting a time and a name on a hand-off that currently has neither.
Preparation and a write-up the technician can work from
Preparation the day before decides how the morning goes. For each of tomorrow's appointments, check four things. Are the parts for the booked work reserved or on order? Is the concern clear enough for a technician to start? Does warranty, a service contract or an open recall apply? Is the courtesy car or the pick-up arranged? An appointment that fails one of these needs a call today, while there is still time to order the part or ask the customer when the noise happens.
Run this check at a fixed time in the early afternoon and give the parts desk its list before the last order of the day goes to the supplier. A car whose parts arrive at 11:00 blocks a ramp for the whole morning.
Check-in is the second hand-off, and the write-up is the only thing the technician will read about the customer's concern. "Noise from the front" sends a technician on a test drive with no plan. "Knocking from the front left over speed bumps, since last week, louder when the engine is cold" gives a starting point. Ask the same questions every time: when it happens, how often, under which conditions and since when. Write the answers in the customer's words.
Before the keys go on the board, agree two more things and put them on the signed order. The first is the promise time. The second is how the customer wants to be reached about extra work, and whether they will be at a desk or on a building site at eleven.
Agree the promise time, then check it twice a day
The promise time is the one number the whole workshop works towards. Build it from the planned job time plus a margin for the health check and for extra work the customer may approve. The customer's preferred time is an input. If the two do not fit, say so at the desk, when the customer can still choose a courtesy car or a later collection.
The usual failure is that the time is agreed at 8:00 and nobody looks at it again until the customer arrives at 17:00. Pick two fixed points in the day, for example 11:00 and 14:00, and compare every open order against its promise time and the work still left on it. If a part is late or a job is running over, call the customer then with a new time. A customer told at 11:00 can rearrange the afternoon. One told at 17:00 has already left the office.
In Prompt CRM, a promise time at risk raises an alert with a proposed new time, and a part delivery that slips flags the promise time on the order. The advisor gets a task to agree the new time with the customer within 15 minutes.
Pricing findings and getting the approval
This hand-off has the most money in it, and it is often the slowest of the day. The technician submits the health check and moves on to the next job. The findings wait until the advisor has a quiet moment, and at 10:00 on a Monday that moment does not come. By the time the customer gets a price, they are in a meeting, and the car is still on the ramp with the wheels off.
What helps:
- Give pricing a target time and write it down. Fifteen minutes after the health check is submitted is a workable default.
- Price common findings from a menu per model group, with the labour time and the parts kit fixed. The advisor then prices only the unusual findings by hand.
- Send the customer something they can decide on from their phone: each item with a photo, one plain sentence, the urgency and the price including VAT. A short video from the technician makes the case better than any description. The digital vehicle health check article covers how to set that up.
- Chase silence on a timer. Prompt CRM's defaults send the customer a reminder after 20 minutes and give the advisor a call task after 45.
Record every decision: what the customer saw, which items they approved or declined, at which price, when and through which channel. The rules behind this differ by country. In Germany, if a non-binding estimate will be exceeded substantially, the workshop has to tell the customer without undue delay (§ 649 BGB). In the UK, garages accredited to The Motor Ombudsman's Service and Repair Code commit to contacting the customer for authorisation before they start additional work, and the final invoice should match a quotation unless the customer authorised the extra costs (clauses 3.2 and 4.2). A note on the job card saying "customer OK" will not carry much weight if the invoice is disputed three weeks later.
Keeping the customer informed without phoning all day
Customers ring to ask about their car when they have heard nothing. Each of those calls pulls the advisor away from the desk, from the next customer and from the findings waiting to be priced. The fix is to send a short message at fixed points before the customer has a reason to ask: when the car is checked in, when the estimate is ready, when the promise time changes and when the car is ready to collect.
Bad news goes out first and early. A late part, a car that has to stay overnight and a finding that changes the price all belong in a call or a message as soon as the advisor knows. Keep the tone plain and give the new time or the new price in the same message, so the customer has something to plan with.
If you want to see which roles hold the order at each point of a visit, the eleven stages on our how-it-works page map them out.
Invoice review and hand-over
The invoice is the advisor's last chance to catch a mistake before it reaches the customer. Check it against the order before it is issued. Every approved item is on it and every declined item is off it. Warranty and internal lines sit with the right payer. Sold time matches the menu or the estimate the customer approved. Once an invoice is issued, a mistake usually means a credit note, a new invoice and a second conversation with the customer. Five minutes of checking before is cheaper.
The hand-over is where the customer decides whether to come back. Walk them through what was done, in the same plain sentences used in the approval. Then go through what they declined or postponed, with a date for when each item becomes due, and write that date on the customer record. That list is where the next visit starts. In Prompt CRM, an order that is ready for collection gives the service advisor a hand-over task with a checklist.
A service advisor's workflow fails at the hand-offs. In nearly every case the next task is known and its deadline is not. Write a target time next to each of the eight steps, put one name on each, and at the end of the day look at which ones were missed. That list will show you where tomorrow is going to go wrong.