An auto repair shop handles phone calls well by sorting each call in its first sentence and giving it the one thing it needs: a status call goes to the service advisor, a new repair gets a proper intake and a drop-off time, and a price question gets the shop’s policy rather than a guess. The hard part is not the script. It is that the person who answers the phone in most shops is also the person running the counter.
The service advisor is writing up the car in front of them, a technician is waiting to ask whether the customer approved the extra work, and someone is at the desk to pick up keys. Then the phone rings, and it is somebody asking whether their car is ready — the third time today that question has pulled the advisor off the floor.
For transparency, since it shapes the framing: Reign AI builds an AI receptionist on human-grade voice AI, which is one of the options weighed here. The page is written to stay useful to a shop that reads it and chooses differently.
Why does the phone land on the service advisor?
Because in most independent shops the advisor is the front desk: they quote, write repair orders, call customers for approvals and hand back keys, and the phone is one more job on top. Every call that interrupts them also interrupts the customer standing at the counter.
The calls are not all the same, and treating them as one queue is what makes the phone feel endless:
| Call | What the caller needs | What the phone can honestly do |
|---|---|---|
| “Is my car ready?” | A status from someone who knows | Take it to the advisor with the vehicle attached; ring them if the caller asks and transfer is set up |
| A new repair | A time to bring the car in | Capture the car and the symptom; book where a calendar is connected |
| “How much will it be?” | A number nobody has yet | State the shop’s inspection policy, not a price |
| Supplier, warranty, fleet | The advisor, today | Take a message that says it is not a new customer |
The sorting question is plain: “Is the car you’re calling about already here with us?” Asked first, it stops a returning customer being walked through a new-customer script, and it tells whoever reads the message which pile it belongs in.
How should a shop answer “is my car ready?”
Honestly: whoever answers can only tell the customer what they can see, and the status of a car lives on the job board, in the shop software or in a technician’s head. A receptionist that cannot see those takes the question to the advisor with enough attached that one call back settles it.
Reign’s receptionist is not connected to shop-management software, so this is what it does. Any receptionist that claims to give live status should be asked where that status comes from; if the answer is “it estimates”, that is a guess with a confident voice. “It should be done by four” is worse than “the advisor will call you”, because the customer plans their afternoon around it.
What the advisor needs from a status message:
- The vehicle — year, make, model and colour, or the repair order number if the customer has it.
- When it was dropped off and what it came in for.
- The question in the customer’s words. “Is it ready” and “did you find out what the noise was” are different callbacks.
- When they need it back, and whether they need a ride or are planning around a pick-up time.
- The best number to reach them.
The calls themselves are easier to reduce than to answer. A shop that tells every customer at drop-off when it will next call them — after the diagnosis, and again when the car is ready — gets fewer “just checking” calls, because the customer is not left wondering.
A sample call
An illustrative example, not a recording of a real call. It assumes a shop that has not switched on live transfer, so a status question becomes a message for the service advisor.
Receptionist: Thanks for calling [Shop name]. This call may be recorded for quality and training purposes. How can I help?
Caller: Hi, I dropped my car off this morning for the brakes. Is it ready yet?
Receptionist: I can’t see where your car is in the shop from here, so I’ll get this straight to the service advisor. Can I get your name?
Caller: Dana Morris.
Receptionist: Thank you. Which vehicle is it — the year, make and model?
Caller: A 2017 Civic, the grey one.
Receptionist: Got it. Is there a time you need it back by today?
Caller: I need it by five. I have to pick up my kids.
Receptionist: Understood. What’s the best number to reach you?
(The caller gives a number.)
Receptionist: I’ve noted that you’d like an update on the brake job on the grey Civic and that you need it by five. The service advisor has your number and will call you back as soon as possible.
The advisor gets the name, the car, the job, the deadline and a callback number in one message. What the receptionist did not do is say the car “should be ready soon” — it has no way of knowing, and a promised time that slips is a worse call than the first one.
What should the first call capture for a new repair?
The car, the symptom in the caller’s words, and whether it is safe to drive. Those three decide which technician looks at it, how long the bay is tied up, and whether the car arrives under its own power or on a tow truck.
- Year, make and model, and roughly the mileage if they know it.
- The symptom, exactly as they describe it. “Grinding when I brake” and “squeal in the morning that goes away” send a technician in different directions. When it happens — cold, at speed, turning — is worth asking.
- Warning lights. Which one, and whether it is on steadily or flashing.
- Whether it is drivable right now (the next section).
- Drop-off or wait. Some work suits a customer waiting in the lobby; a diagnosis rarely does.
- When they need it back, and whether they will need a ride or a loaner, if you offer either.
- Who is paying. The customer, a fleet account, or a warranty provider changes who approves the estimate.
The same discipline that gets the model number off an appliance’s data plate on the first call applies here with a vehicle instead — the pattern is set out on the appliance repair page and not repeated. The general version of what to ask first, and what never to ask first, is in questions to ask when a customer calls for a quote.
What if the car is not safe to drive?
Then the answer is “please don’t drive it — have it towed”, and nothing more technical than that. The phone is not where a car gets diagnosed, and a receptionist that reassures a caller their brakes are probably fine is giving mechanical advice it has no business giving.
A shop should decide in advance which descriptions get that answer, and write them down:
- A brake pedal that sinks to the floor, or brakes that have stopped working properly.
- Steering that has changed suddenly — pulling hard, loose, or heavy.
- Smoke, a burning smell, or fluid pouring out under the car.
- A warning light the dashboard or owner’s manual says means stop driving.
Some situations are not a shop call at all. A crash where anyone is hurt, or a car that is on fire, is a 911 call — get away from the car first. Nothing built in tells a caller that: the 911 line and the “don’t drive it, get it towed” line are both instructions the shop writes into its setup, alongside the list above, and tests before relying on them.
After hours, the usual version is a tow-in: the car arrives on a flatbed overnight and the customer calls to say so. What the advisor needs in the morning is where the car is (your lot, or still at the tow yard), where the keys are, the plate or the vehicle, what happened, and a number for the customer. Most shops do not attend at night, so for them every after-hours call is a message — the honest setup, as long as the promise matches. Where live transfer is set up — at any hour, not only when someone is on call — the receptionist asks one fixed question when a caller describes something happening right now: “Is this an emergency right now, or is it something that can wait until the next business day?” Nothing built in sends a caller to 911 first; a yes rings whoever the transfer reaches. How that question works, and what rings on a yes, is covered in how an AI receptionist handles emergency calls after hours.
Booking a bay: what can be booked on the call?
A drop-off time for work you have decided is bookable, and nothing that promises when the car will be finished. Bays and technicians are the constraint, and a diagnosis has no known length until someone starts it.
Where calendar booking is connected, it is worth splitting the work before switching it on:
- Fixed-length jobs — a tire changeover, an oil change, a safety inspection — can usually be booked straight into a slot, because you know how long they take.
- Drop-offs for a diagnosis can be booked as a drop-off time, with the customer told plainly that the shop will call once it knows what is wrong.
- Big or uncertain jobs — an engine noise, a transmission problem, anything the advisor wants to talk through — are better taken as a request and confirmed by a person.
Without a connected calendar, the receptionist takes the request with the customer’s preferred day and time and the advisor confirms it. The decisions underneath — one calendar that is actually true, what is bookable at all, travel and buffer rules — are covered in booking a job straight into your calendar.
The price question about a car nobody has looked at
The phone states the shop’s policy, not a price. A caller asking what a brake job costs is asking something that depends on what a technician finds, and a number given now is a number the customer will hold the shop to.
What the call can cover is how pricing works at your shop: whether there is an inspection or diagnostic charge, whether it comes off the repair, and that nothing is done until the customer approves the estimate. Which of the common price policies suits which kind of work is laid out in should contractors give prices over the phone; a shop usually runs two of them, one for standard maintenance and one for anything that needs a diagnosis first.
Tire season: the changeover rush
In much of Canada, the weeks either side of the first snow and the spring thaw bring a wave of calls that are all the same: “when can you put my winter tires on?” They are short, they are bookable, and they arrive while the bays are already full.
That makes the season mostly a booking-window problem. The useful decisions are made before it starts: how many changeover slots there are each day, whether customers with tires stored at the shop get priority, and what the phone says once the next free slot is weeks away. A caller asking “do you still have my tires?” is a storage question the receptionist cannot see the answer to, so it goes to the advisor with the customer’s name and vehicle like any status call. The general argument about a seasonal phone — capacity that does not care what month it is — is the same one made on the landscaping page, and is not repeated here.
Calls that are not customers: suppliers, warranty claims and fleet accounts
These calls look like interruptions and are often the most time-sensitive on the line. A shop phone should recognise them in the first sentence and get them to the advisor with the detail that matters, rather than run them through a new-customer intake.
- Parts suppliers. The part is back-ordered, the wrong one arrived, or the driver is confirming a delivery. The message needs the supplier, the part and which car it is for.
- Warranty and extended-warranty calls. A warranty administrator calling about a claim, or a customer asking whether a repair is covered. The receptionist should not answer coverage; it takes the provider, the claim or repair order, and passes it to the advisor.
- Fleet and commercial accounts. The account name, the unit or vehicle number, who is allowed to approve work, and any purchase order. The person calling is often not the person who pays.
- Tow operators dropping a car, who need to know where to leave it and where the keys go.
What an AI receptionist does NOT solve for an auto repair shop
- It cannot see the job board. Status, parts on order and stored tires all stay with the advisor unless a system feeds them in — and Reign’s receptionist is not connected to one.
- It cannot diagnose. The symptom on the phone narrows it down; a technician decides.
- It cannot price a repair. It can state your inspection policy and nothing beyond it.
- It cannot approve work. Estimate approvals are a conversation between the advisor and the customer.
- It answers in English, and it will not know that you are closed for a long weekend, have stopped working on a make, or are booked solid for tire season unless someone tells it.
What it does well is the repetitive part: the same sorting question on every call, the vehicle and the symptom captured the same way, the unsafe-car instruction you configured, given every time, and one clear message per call instead of a note on a scrap of paper. How AI receptionists work covers the mechanics and the limits in more detail.
Test it with three calls your shop actually gets
Call whatever you are considering as three customers:
- “Is my car ready?” Does it say it cannot see the shop, take the vehicle and the deadline, and avoid inventing a time?
- “My brakes are grinding — how much to fix them?” Does it state your inspection policy, or make up a price?
- “The brake pedal goes almost to the floor. Can I drive it in?” Does it tell you not to drive it and to arrange a tow, if you’ve written that into the setup, without offering a diagnosis?
Then read what arrived on your end. Each message should name the vehicle, say which kind of call it was, and carry the customer’s words. If all three read “customer called about car”, the setup has not learned your shop yet.
Common questions
Can an AI receptionist tell a customer whether their car is ready?
Not on its own. Whether a car is ready lives on your job board, in your shop software or in the technician's head, and a receptionist that has not been connected to any of those does not know. Reign's is not connected to shop-management software, so it takes the question to the service advisor with the vehicle, the drop-off day and the time the customer needs it back. Where live transfer is set up and the caller asks to speak to the advisor, it rings them first. What it must never do is guess a time.
Should the phone quote a brake job or a repair?
No figure for a car nobody has looked at. "Brakes are grinding" can be pads, rotors, calipers or a stone caught in a shield, and the honest answer depends on what a technician finds. What the phone can state is the shop's policy: whether there is an inspection or diagnostic charge, whether it is credited against the repair, and that the customer approves the estimate before work starts.
What should a caller do if their car is not safe to drive?
Not drive it. A brake pedal that sinks, steering that has gone wrong, smoke, or fluid pouring out is a tow, not a drive to the shop, and the receptionist should say so once the shop has written that into its setup, and then take the details of where the car is and when it will arrive. A crash where anyone is hurt, or a car that is on fire, is a 911 call first. Beyond "do not drive it, get it towed", the phone gives no mechanical advice.
Can an AI receptionist book cars into our bays?
Only where calendar booking is connected, and only for the work you decide is bookable on a call, such as a tire changeover, an oil change or a drop-off for a diagnosis. Without a connected calendar it takes the request with the customer's preferred day and the advisor confirms. Either way it books a drop-off time, never a pick-up promise.
What about calls from parts suppliers, warranty companies and fleet customers?
Each one is a business call, not a new customer, and each should reach the advisor or whoever handles it with the details that matter: the supplier and the part, the warranty company and the claim or repair order it is about, the fleet account and the unit number. The receptionist should not answer whether a repair is covered by a warranty; that is between the advisor, the customer and the warranty provider.