The Ugly Call Test: a one-week AI phone answering trial for auto repair shops

This is the kit from our video on AI phone answering for auto repair shops. It follows the video:

1. Log every call for one normal week.
2. Make the ugly calls yourself: a bad line, a mumbled make, asking for someone by name.
3. Write the never list before the week starts: what it may never do alone.
4. Watch the handoffs, not only the bookings. A transfer to nobody is worse than a ring.

Every vendor demo is a smooth call. Your Tuesday afternoon isn't, so that's what you test.

Why test it at all

Calls go unanswered because the people who'd answer them are busy with customers. People don't pick up unknown numbers either: Hiya's report says 86% of calls from unknown numbers go unanswered. Shop software vendors have built answering tools for this. AutoLeap's AIR books into the AutoLeap calendar and lists per-call and monthly plans, and Shopmonkey's Concierge takes calls after hours, captures the customer and vehicle, and can transfer or create follow-up tasks. If your shop already runs one of those systems, ask them first. Whichever tool you look at, the test below is the same.

Before the week (about an hour)

Pick a week with a normal mix of work, not a holiday week. Then write down three things.

Your five most common calls. Most shops hear some version of these: an appointment request, "what's the status of my car," a price on a job, "is it done," and a parts or vendor call.

The never list. These are things the system must never do on its own. Start with these three and add your own:

• Quote a price for work nobody has inspected.
• Promise a pickup time.
• Tell a customer a car is safe to drive.

The handoff plan. Who gets a transferred call, and who's the backup when that person is under a car. Write the hours each one covers.

During the week: the call log

Keep one line per call. A spreadsheet or a clipboard both work.

Time	What the caller wanted	What the system did	Did a person have to fix it?
8:12 (example)	appointment, brakes	booked Thursday 9:00	no
9:40 (example)	is my car done	handed to the advisor, notes attached	no
2:15 (example)	asked for Mike	transferred, nobody answered	yes

Ask your front-desk person to mark every call where they thought "I'd have said that differently." Those marks are often more useful than the vendor's dashboard.

The ugly calls to make yourself

Call your own number six or seven times during the week, from different phones. Script them loosely:

1. The bad line. Call from somewhere with one bar of signal, or with traffic noise behind you.
2. The mumbled make. Say "it's the, uh, Silverado, maybe a 2016" and see what it captures.
3. The name. Ask for a specific person by first name, the way regulars do.
4. The noisy engine. Describe a sound with no vehicle details and see if it asks the right questions.
5. The price. Ask what a brake job costs. It should not quote uninspected work.
6. The safety question. Ask whether it's safe to keep driving. It should hand that to a person.
7. The angry caller. Be short and annoyed about a delay. It should get you to a person fast.

Log each one with a "TEST" tag so you can separate them from real calls.

At the end of the week: count four things

1. Real bookings. Appointments that are actually on your calendar, not just "booked" in the vendor's report.
2. Handoffs. Calls passed to a person, and how many arrived with the right notes.
3. Visible mistakes. Calls it got wrong in a way a customer would notice.
4. Dead ends. Calls where it did nothing useful and the caller hung up.

You'd expect bookings to be the number that decides it. Watch the handoffs just as closely. A caller who gets transferred to nobody has a worse experience than one who simply hears the phone ring, and that's the call that turns into a review. If you can't get these four numbers from the vendor's own reporting, that tells you something about the vendor.

Questions for the demo call

• Where does the booking land? In your shop system, or a separate calendar someone copies over? Tekmetric lists 70+ integrations, so ask about your specific system, not "do you integrate."
• What happens when it doesn't know? The right answer is a handoff with the notes captured so far.
• Can you hear recordings and read transcripts? Ask for both.
• What counts as a call for billing? Get the per-call and monthly numbers in writing.
• Who owns the phone number? You should be able to leave and keep it.

Rules to check before go-live

Recording a call can require consent from everyone on it. Rev's state-by-state guide lists California, Florida, Illinois and Pennsylvania among the all-party consent states, so if you record, the greeting should say so. Have your lawyer confirm your state's rule.

For inbound calls, the FCC has said the TCPA's requirements don't extend to technologies used to answer inbound calls. Outbound is different. The FCC ruled in 2024 that AI-generated voices count as artificial under the TCPA, so if the same tool calls customers back, ask how it handles consent.

Where RevvOS fits

RevvOS doesn't sell a standalone AI phone answering product. What it does is bring calls, texts, forms and open estimates into one customer view, so the person who picks up a handoff sees what the call was about and what's still open, and drafts go to a service advisor to approve. See customer engagement and missed call automation for more.