AI voice agent for dealerships: the hours calls go unanswered

When dealership calls go unanswered

A customer at the counter handing over keys takes priority over a ringing phone, and that is correct. If the morning drop-off is the busiest hour at your counter, service calls that arrive in that hour can go unanswered, and the caller may book with the independent garage down the road. Your phone log shows whether that holds at your site.

Sales enquiries can leak at a different hour. Some buyers look at cars in the evening and on Sundays, when your showroom may be shut. A voicemail left late in the evening can wait until the next morning, and the buyer may have asked other sellers by then. Your phone log shows whether your sales line leaks the same way.

The two leaks can have different causes, so each needs its own count.

Three kinds of call share one phone number

Sort what the line carries before you count anything. Three kinds of call go into these counts. They look alike on the phone bill and need different things.

Take two counts from your own phone log

Your phone system or your carrier should hold the evidence. Pull the call records for several typical weeks before you speak to any vendor. If your system does not log calls that ring out, ask your telephony provider for the call detail records.

Write both counts down before the first demo. A vendor’s average describes somebody else’s showroom, and your own numbers are the baseline for reading a pilot.

Read the counts before you pick a line

• If unanswered calls bunch in the drop-off hour, start with the service line, where booking calls tend to repeat.
• If voicemails pile up after hours, start with the sales line: each hour of delay can let the buyer ask elsewhere.
• If calls ring out evenly all day, check staffing and routing first, because an agent adds no capacity to a full workshop.
• If both counts are quiet, leave the phones alone.

Treat the counts as a hypothesis and let a pilot test it. Every call comes back as a transcript, so the pilot counts the callers who asked for a time you did not have. That shows whether the phone or the schedule is the bottleneck. The AI appointment booking page describes the same effect.

The agent’s work on a dealership call

The page for dealers and service centres sets out what Benerra would build for a dealer. Five behaviours matter for the counts above.

• It reads availability live during the call and offers slots that a free bay and a qualified technician can both take.
• It reads registration, mileage and contact details back and confirms them, since a misheard registration can put a job card on the wrong car.
• It answers questions about the cars in stock from the data you give it, and takes any question the data cannot answer to a person.
• For a sales enquiry, it writes the vehicle, budget, part exchange, interest in finance and visit time into your CRM as structured fields, with the transcript attached.
• It books the test drive in the right diary.

Benerra configures job types, durations, skills and bay constraints with you before launch. If your stock feed is out of date, the agent repeats the error, so ask how often the feed refreshes. Where a system cannot be read and written programmatically, Benerra says so during scoping. It confirms in writing which systems are connected before the agent takes a live call.

Three things it leaves to people

These three belong to this trade. The article on what a voice agent should never be asked to handle lists four categories that belong to a person by design. The article on the exit path covers how a call moves to a person.

Pilot one line and read the results

Benerra quotes go-live timing per project and promises no number of days. Ask each vendor, including Benerra, how a limited slice of calls can be routed to the agent. Start on that slice, then widen it.

Review five items from the pilot.

1. The transcripts of the bookings, starting with the shortest and the longest.
2. The registration and mileage on a sample of job cards, against what the caller said.
3. The bookings in the diary, and whether each one fits a free bay and a qualified technician.
4. The calls handed to people, with the reason for each: out of scope by your rules, asked for by the caller, or a conversation that went wrong. Only the last is a failure.
5. The requests for a time you did not have.

Reading by hand stops scaling once volume grows beyond the pilot. Locator, Benerra’s speech analytics, scores 100% of your recorded calls against a checklist you set, whereas manual QA in our own operations reviews under 5% of recorded calls. The recordings and the checklist are its two inputs.

Service reminders are outbound calls

Outbound calls follow different rules from the calls you answer, and the rules depend on the country and on the list. Settle the lawful basis for each number with your counsel before the first reminder goes out. The same agent can make service reminder, inspection due date and confirmation calls. Benerra suppresses numbers marked as opted out on its side as well as yours. The article on outbound calling compliance and the AI outbound calling page cover the rules. This article is not legal advice.

Steps for this week

1. Pull the call records for both lines for several typical weeks, and take the two counts.
2. Check the CRM for after-hours enquiries: which have a record, and how long each waited for a callback.
3. Pick the line the counts point to.
4. Write its rules in your own words. For service: job types, durations, skills and bays. For sales: vehicle, budget, part exchange, interest in finance and visit time.
5. Ask every vendor, including Benerra, to confirm in writing which systems are connected and what is written where, before the first live call.

Keep the counts as the baseline for the pilot.

Frequently asked questions about AI voice agents for dealerships