Get started

An AI phone agent for the service line that rings while every advisor is at the counter

In an auto repair shop or a dealership service department, the phone competes with everything else an advisor does. Calls arrive while the advisor is walking a customer through an inspection, writing up a repair order, or chasing a technician for a completion time. The morning rush at the service drive is also the morning rush on the phone, so the two busiest queues peak at the same moment. Callers who wait on hold hang up, status questions interrupt write-ups, and after-hours breakdown calls land in a voicemail box nobody checks until opening.

ThunderPhone gives an automotive service operation an AI phone agent that can answer routed calls, collect a consistent write-up before the vehicle arrives, use connected scheduling and shop-management tools, place compliant outbound status and reminder calls, and transfer the conversations that need an advisor. It follows the shop's instructions and searches the shop's approved documents instead of improvising policy, prices, or repair advice.

Turn every call into a usable repair-order record

An auto-services agent can be configured to:

  • answer inbound calls during rush periods, lunch coverage gaps, and after hours;
  • identify the service type up front—an oil change or scheduled maintenance, a diagnostic concern, tires and alignment, or open recall work—and ask the intake questions that service type needs;
  • collect the caller's name, callback number, vehicle year, make, model, and approximate mileage, plus a plain-language description of the symptom for diagnostic visits;
  • book, reschedule, or cancel appointments through a connected scheduler or shop-management API, and note drop-off versus waiter preferences;
  • answer status questions from information the shop's systems expose, and take a message for the advisor when they do not;
  • place outbound vehicle-ready, parts-arrival, and appointment-confirmation calls on an eligible production number;
  • run estimate-approval callbacks: relay the shop's written estimate exactly as provided, record the customer's decision, and transfer to an advisor for anything outside the shop's phone-approval rules;
  • make recall and maintenance-interval outreach calls to the shop's own customers and consented contacts as outbound campaigns with voicemail handling and retries;
  • take towing and breakdown calls, capture the vehicle's location and situation, and hand off to the shop's dispatch or on-call path;
  • route warranty and goodwill questions to the person the shop designates rather than guessing at coverage; and
  • coordinate loaner and shuttle logistics using the shop's stated policies and availability.

The agent does not diagnose vehicles, quote repair prices it was not given, or take payment-card details. The shop defines what it may say, what it must collect, and when it must hand the call to a person.

Sample auto-service call flow

Agent: Thank you for calling Ridgeline Auto Service. Are you calling to schedule service, check on a vehicle we have in the shop, or something else?

Caller: My check-engine light came on yesterday, and the car is idling rough.

Agent: I can set up a diagnostic visit for that. Is the vehicle safe to drive, or do you need help getting it to the shop?

Caller: It drives fine, it just feels rough at stoplights.

Agent: Understood. May I have your name, the best callback number, and the year, make, and model of the vehicle?

Caller: Sam Okafor, 415-555-0189. It's a 2019 Outback.

Agent: Thank you. For a check-engine diagnostic we reserve time with a technician first, and the advisor calls you with findings and a written estimate before any repair work begins. I have a drop-off opening tomorrow at 7:30 a.m. or Thursday at 10:00 a.m. Which works better?

Caller: Tomorrow. Do you know roughly what this will cost?

Agent: I can't quote repair costs before the technician inspects the vehicle—the shop provides an estimate after diagnosis, and nothing is done without your approval. The diagnostic visit itself is booked for tomorrow at 7:30 a.m. drop-off. Would you like the shuttle back home while the car is with us?

If the caller instead said the vehicle was undrivable or stranded, the agent would switch to the shop's breakdown flow: capture the location and situation, then follow the configured handoff—for example, a warm transfer to the on-call dispatcher or a structured message pushed to the towing partner's system.

Features that matter in a service operation

Service-type intake instead of one generic script

An oil change needs a time slot and a vehicle. A driveability complaint needs a symptom description, when it happens, and whether warning lights are on. Recall work needs the vehicle identified and the open campaign confirmed against the shop's process. The agent can branch its questions by service type, so the advisor starts the day with structured write-ups instead of "customer says car makes noise."

Outbound status, ready-for-pickup, and confirmation calls

Vehicle-ready notifications, parts-arrival calls, and day-before appointment confirmations can run as individual outbound calls or campaigns on an eligible production number. Voicemail detection can leave the shop's configured message or hang up, and campaigns can retry voicemail outcomes under their retry policy—so a "your car is ready" call that hits voicemail at 2 p.m. can try again before closing. Confirmation calls that offer a one-touch reschedule path give the shop a chance to refill a bay instead of absorbing a no-show. The organization remains responsible for consent, identification, calling windows, do-not-call requests, and other applicable outbound-calling rules.

Estimate-approval callbacks with the shop's limits built in

Authorization rules for repair work vary by jurisdiction, and every shop has its own documentation practice. The agent works inside that practice: it relays the written estimate the shop provides—line items, amounts, and the total, exactly as written—records whether the customer approves, declines, or has questions, and transfers to an advisor for anything the shop has not authorized it to handle by phone, such as amounts above a threshold, added work, or negotiated changes. Where recording is enabled, the call's recording and transcript give the shop a timestamped record of who approved what, which supports the notation many shops keep for phone authorizations.

Breakdown intake with location capture

After-hours and roadside calls are the ones a voicemail box handles worst. The agent can collect the caller's location, vehicle, and situation, distinguish "tow needed" from "question that can wait until morning," and follow the configured escalation: cold transfer for immediate routing, or warm transfer on an eligible production number so the on-call person hears a private briefing before accepting the call. If nobody picks up, the agent returns to the caller, takes a complete message, and the shop starts the morning with a structured intake instead of a garbled recording.

Knowledge grounded in the shop's documents

Attach hours, service menus, maintenance-interval charts, warranty and financing policies, tire and battery brand information, and drop-off instructions to the knowledge base—text, Markdown, CSV, PDF, and DOCX files up to the documented limits of 5 MB per text file and 50 MB per PDF or DOCX, with URL import available for pages the shop already maintains. The agent searches those documents mid-call and routes questions the material does not answer instead of guessing.

Connections to the systems the shop already runs

Agents can call HTTP APIs and remote MCP tools during a conversation, so a connected scheduler, shop-management system, or CRM can expose exactly the operations the shop allows—check availability, create an appointment, look up a repair-order status, log a lead. HMAC-signed webhooks push call events to the shop's systems as they happen. Production numbers can be brought through supported VoIP connections or manual SIP configuration for any SIP trunk, so the shop keeps the phone number customers already know. An embeddable web widget can put the same agent on the shop's website for customers who prefer to click rather than dial.

Hold, phone menus, and multilingual calls

When the agent itself places calls—to a dispatcher, a parts line, or a customer's workplace—it can wait on hold and navigate keypad menus. On the language side, ThunderPhone supports 47 voice languages; configure a primary language and additional languages, and the agent can switch mid-call when a caller changes to one of the selected languages, provided the chosen voice supports the set. One service line can greet in English and finish the booking in Spanish without a transfer.

Testing before customers hear it

Use a browser mic test for quick iteration, then run simulations for the scenarios that go wrong in real shops: the caller who wants a price for an unseen transmission, the estimate approval that exceeds the phone-approval limit, the stranded caller at night, the recall callback that reaches a new owner, the customer who switches languages mid-call. Simulations produce transcripts and grading, graded scenarios can be grouped into regression suites with pass-rate gates, and A/B experiments can compare prompt variants on live traffic. Recordings, transcripts, and call grading make production calls reviewable afterward.

What would this cost each month?

Suppose a service operation handles 1,500 AI-assisted calls per month, averaging 3 minutes each:

1,500 calls × 3 minutes = 4,500 minutes per month

  • Spark: 4,500 × $0.02 = $90/month
  • Bolt: 4,500 × $0.05 = $225/month
  • Storm: 4,500 × $0.09 = $405/month

That is base engine usage, not a quote. Premium voice or language paths can add up to 3¢ per minute, and phone-number or carrier charges depend on the telephony setup. Hold time bills a flat 2¢ per minute; voicemail and phone-menu minutes bill at the engine rate. Optional add-ons such as verbal acknowledgements, call supervision, and long prompts carry their own published surcharges. The agent builder shows the current all-in rate before calls are placed.

Guardrails the shop stays in control of

  • No improvised prices. The agent quotes only prices and estimates the shop has explicitly provided; for anything else, it explains that pricing follows inspection and books the visit or routes the call.
  • No card details. The agent does not collect payment-card numbers. Payment happens at pickup or through whatever payment flow the shop already uses.
  • Approval limits. The shop decides which estimate amounts and line items can be acknowledged by phone and which require an advisor; the agent transfers at the boundary rather than stretching it.
  • Warranty answers come from people or documents. Coverage questions route to the designated advisor or draw only on approved policy documents.
  • Outbound compliance. Campaigns run under the shop's consent records, identification script, and calling windows.
  • Data handling. ThunderPhone's public compliance posture is GDPR and HIPAA compliant; the shop still configures recordings, retention, integrations, and agent instructions for its own obligations.

Frequently asked questions

Can a ThunderPhone agent book service appointments?

Yes, when connected to a scheduler or shop-management API that permits it. The agent can identify the service type, collect vehicle and contact details, offer available slots, book or reschedule, and confirm the result—with different intake questions for an oil change, a diagnostic concern, or recall work.

Can it handle estimate approvals over the phone?

It can relay the shop's written estimate exactly as provided, record the customer's approval or decline, and transfer to an advisor for questions, changes, or amounts outside the limits the shop sets. Because authorization requirements vary by state, the shop defines what may be completed by phone; recordings and transcripts, where enabled, document the authorization.

Can it call customers when their vehicle is ready?

Yes. Vehicle-ready, parts-arrival, and confirmation calls can run as individual outbound calls or campaigns on an eligible production number, with voicemail detection and configurable retries. The organization is responsible for consent, identification, calling windows, and other applicable outbound-calling laws.

Can it run recall and maintenance-reminder outreach?

Yes, as outbound campaigns limited to the shop's own customers and consented contacts, using the contact list and script the shop provides. The agent can explain the shop's approved recall or maintenance message, book the visit, leave a configured voicemail, and retry under the campaign's policy.

What happens when someone calls at night with a breakdown?

The agent answers, captures the location, vehicle, and situation, and follows the shop's escalation rules—transferring to an on-call number, handing off to a dispatch system, or taking a complete structured message. Warm transfer, on eligible production numbers, lets the agent brief the on-call person privately before connecting the caller.

Will the agent quote repair prices?

Only prices the shop has given it—posted menu services, for example. For repair work that requires inspection, it explains that the shop provides an estimate after diagnosis and offers to book the visit. It never invents a number.

Can it take a payment over the phone?

No. The agent does not collect payment-card details. It can explain the shop's payment options from approved material and direct the customer to the shop's existing payment process.

Can one agent serve English and Spanish callers on the same line?

Yes. ThunderPhone supports 47 voice languages; set a primary language and additional languages, and the agent can switch mid-call when the caller changes language, provided the selected voice supports both.