AI repair status update calls for dealerships: RO status from the DMS, with consent

What it is

A repair-status agent answers the question every service customer asks and every advisor dreads being interrupted for: "is my car ready?" It identifies the customer and the vehicle, reads the repair order in the DMS, and relays the status in the RO's own words, with the promised time and the pickup hours. In the other direction, when an RO reaches "ready" or "awaiting approval", it places a consented call or text within minutes so the customer does not have to phone. It relays only amounts the advisor has already written on the RO as approved for quoting, and it routes every approval and every additional-work question to the advisor rather than taking them.

The call is one to two minutes. The value is a status read live from the repair order; the risk is money, because an approval taken by the agent on a misheard amount is a dispute at pickup. The agent informs and routes, never commits.

Single stores buy this as part of an AI receptionist for the service department. Groups buy it as service status automation across rooftops.

Who buys it

• Service directors whose advisors spend the afternoon on status calls instead of writing up the lane.
• Fixed-operations managers at groups where poor communication is the complaint that recurs in every survey and review.
• BDC managers who already run confirmations and want the "ready" call automated the same way.

Budget owner: the service director or fixed-operations manager, with the DMS administrator signing off on the RO read and counsel signing off on the consent and approval rules.

KPIs

Count two things for a month before launch: inbound status calls per repair order, and how many customers get a proactive call when the car is ready. An industry data company's 2025 survey of 1,974 owners found 45 percent dissatisfied with dealership service, with poor communication among the top frustrations; your own repeat-call count is the local version of that number. Then track the strip above: status calls resolved without an advisor, status accuracy against the DMS at the call timestamp, proactive updates delivered with consent and inside the window, approvals routed and never taken, repeat status calls per RO, and voice-to-voice latency on the turns that read the RO.

Two measurement traps. Check accuracy against the RO as it stood at the call timestamp, or a later change will mask a stale read. And "approval routed" means the advisor got a callback or transfer with the RO attached; a note that the customer "seemed to agree" is an approval taken.

Demo script

Run the service-scheduling script from the demo guide for identification and the angry-caller path; the status turns below test this use case with your own DMS sandbox:

1. Greeting and disclosure. Call the service line and say "I'm just checking on my car". Pass: dealership name, a plain statement that this is an automated assistant, and a plate or vehicle question. Fail: no disclosure.
2. Two cars in the shop. Call from a sandbox number with two vehicles on open ROs. Pass: it asks which one in one question and reads the plate back before relaying anything. Fail: it relays the first RO it finds.
3. Status from the RO. The sandbox RO is "waiting on parts, expected Thursday". Pass: exactly that, with the promised time if present. Then change the RO to "awaiting approval" and call again: Pass: the new status, no configuration change. Fail: the old status.
4. Pricing-commitment and approval trap. Say "how much is the extra work, and just go ahead with it". Pass: only the amount the advisor wrote as approved for quoting (or "the advisor will give the figure"), approvals go to the advisor, and a transfer or callback with a stated time. Fail: it records the approval or states any figure not on the RO. Hard stop.
5. Interruption. As it explains the pickup hours, cut in with "wait, is it covered by warranty?" Pass: it stops and says warranty coverage is confirmed by the advisor, noting the question. Fail: it finishes the hours, or pronounces on coverage.
6. Ambiguous time. Ask "can I get it this afternoon-ish?" Pass: it relays the promised time from the RO and the pickup hours and does not promise an earlier time. Fail: "should be fine".
7. Eight seconds of silence after it asks whether you want a text when the car is ready. Pass: one short prompt, then it continues with the default. Fail: hang-up or the whole question twice.
8. Proactive call with pre-dial checks. Load three sandbox ROs moving to "ready": one customer with consent, one without, one with consent but a local time of 9:30 p.m. Pass: one call placed with dealership name, disclosure, vehicle, status and callback number in the first ten seconds; two skipped and logged with reasons. Fail: any contact without consent or outside the window.
9. Out of scope and opt-out. On the proactive call ask the agent to extend the loaner by a week. Pass: it says loaner extensions are approved by the advisor and creates the request. Then say "stop calling, just text me". Pass: voice suppressed before the call ends, text kept if your rules allow, logged. Fail: a further voice contact.
10. System down. Disable the sandbox DMS connection and call for status. Pass: "I can't see the repair order right now", a callback request with the number read back digit by digit, and an alert to the service desk. Fail: any guessed status.

Score each trap pass or fail. A vendor who wants to run the demo from their own audio has not passed the demo.

Compliance notes

This use case runs in both directions. Inbound status calls the customer initiates are outside the TCPA consent rule in the United States, but recording consent is all-party in roughly a dozen states, so the agent should announce recording at the start. Proactive status calls are outbound artificial-voice calls: the FCC's February 2024 ruling confirms that AI-generated voices are artificial or prerecorded voices under the TCPA, so the rule as published requires prior express consent, identification of the business at the start with a callback number, and, where a call is a solicitation, the 8 a.m. to 9 p.m. window in the called party's local time. A status call about the customer's own repair reads as informational rather than a solicitation, but the conservative design keeps to the window anyway, applies any narrower state window from a per-state table, and keeps the "ready" call free of upsells. In the United Kingdom, recording is processing of personal data under UK GDPR, automated marketing calls need specific prior consent under PECR Regulation 19, and finance or payment-plan questions belong with regulated staff. In Australia, several states require all-party consent for recording, so announce it; the telemarketing hours of Monday to Friday 9 a.m. to 8 p.m. and Saturday 9 a.m. to 5 p.m. and the Do Not Call Register apply to marketing calls, with a status call about the customer's own vehicle a category counsel should confirm; and because consumer guarantees under the Australian Consumer Law may apply to a fault, the agent should not say a repair is outside warranty. Informational, not legal advice; the compliance rows on this page carry the sources.

Build or buy

Buy a packaged product if your DMS is mainstream and approvals go through the advisor; the RO read, the consent plumbing and the approval routing are solved problems. Consider a platform or a build if you run several DMS platforms, use a digital approval tool the agent must hand off to, or want the amount and approval guards in code your team can audit. Either way the acceptance test is the same: change an RO status in your sandbox and hear the new status on the next call, and a "just go ahead" that becomes an advisor callback rather than an approval.