What can an auto service phone assistant do?

It takes maintenance and repair booking requests, collecting the licence plate, make and model, mileage and the request. If your service software is connected, it reports the vehicle’s status; if not, it passes the question to a service advisor. It can call customers when their car is ready and remind those whose service is due. Diagnosis, pricing and warranty decisions should always stay with the service advisor.

Do service reminder calls need İYS consent?

It depends. Turkey’s Law No. 6563 says that if the recipient gave their contact details so they could be contacted, no separate consent is needed for messages about the maintenance of goods or services supplied to them. Whether you have serviced the car before and what the call says both matter, though; adding a discount or campaign may make it a promotional call. Classify it with your lawyer.

Can the assistant understand licence plates correctly?

Plates mix letters and numbers, so this is an area to test. In a good setup the assistant reads the plate back to confirm it, and it should also understand callers who spell letters with Turkish city-name codes such as “A as in Adana”. During the pilot, try different plate formats, fast talkers and workshop noise; if you see errors, match on the registered phone number instead of the plate.

What happens if a caller says their car has broken down?

The assistant should not assess the fault remotely. If you have a roadside assistance or towing line, it transfers the call there; if not, it hands the call to the on-call team or a service advisor with priority. If anyone is hurt or in danger on the road, it tells the caller to dial 112, Turkey’s emergency number, straight away. Write these rules into the agent’s instructions and test them.

Blog

AI Phone Assistant for Auto Services: A Practical Guide

An auto service phone assistant books maintenance, reports vehicle status and makes pickup and service reminder calls, but never diagnoses. Flows and İYS notes.

By SpeaklinePublished October 22, 202610 min read

An AI phone assistant for auto services is a voice agent that answers maintenance and repair booking calls in Turkish, collects the licence plate, model, mileage and request, and either books the appointment or passes it to a service advisor. If the service software is connected, it reports the vehicle’s status, and it makes pickup and scheduled service reminder calls. It does not diagnose faults or decide on prices and warranty cover; those go to the service advisor.

This guide covers the call load at an auto service centre, six call flows an assistant can take on, its limits, setup steps, KVKK and İYS notes for Turkey, metrics and a fictional booking call.

The call load at an auto service centre

Most calls to a service centre fall into these groups:

Booking scheduled maintenance, a tyre change or a repair
“Is my car ready?”
Asking for a rough price for maintenance or a repair
Spare parts availability
Insurance claims and warranty cover
Breakdowns, towing and roadside assistance
Complaints after pickup or a recurring fault

The busy hours are predictable: during morning vehicle drop-off and late-afternoon pickups, service advisors are with the customer at the desk. Booking requests rise at the change of seasons, especially when winter tyres are due, and before public holidays when people service their cars for long trips.

Typical reasons calls get missed at service centres:

The advisor is at drop-off. An advisor walking round a car with a customer cannot pick up.
Workshop noise. If the phone is in the workshop, calls are short and error-prone; plates and dates can be misheard.
Status calls. “Is my car ready?” calls keep the line busy all day, and customers trying to book get a busy tone.
After hours. Booking requests thought of in the evening or at the weekend wait until the next day.

To estimate what missed calls cost your service centre, try the missed call cost calculator.

Six call flows an assistant can take on

1. Maintenance and repair booking

Trigger: The customer wants an appointment.
Details: Licence plate, make and model, approximate mileage, the request (scheduled service, tyres, description of a fault), preferred day and time, and whether a courtesy car is needed.
Outcome: If the service calendar is connected, a slot is offered and the booking is made; if not, the request goes to an advisor to confirm. The assistant reads back the plate and time to confirm.
Handover: The fault description is unclear or the customer wants to talk to an advisor.

2. Vehicle status enquiry

Trigger: “Is my car ready?”
Details: Licence plate or registered phone number.
Outcome: If the service software is connected, the job status and estimated pickup time are read from it; if not, the question goes to the advisor as a note and a callback is scheduled.
Handover: Approval for extra work or a price discussion is needed.

3. Pickup notification

Trigger: An outbound call scheduled when the job is closed.
Details: When the customer will collect the car.
Outcome: The pickup time is recorded and passed to the advisor.
Handover: The customer has a question about the invoice.

4. Scheduled service reminder

Trigger: An outbound campaign to customers whose service is coming up.
Details: Whether they want a booking and which day and time suit them.
Outcome: A booking is made or the request goes to an advisor; customers who are not interested are removed from the list.
Handover: The customer describes a problem with the car. The İYS limits of this flow are covered below.

5. Roadside help and emergencies

Trigger: “My car has broken down”, “I’ve had an accident”.
Details: Location and contact details; the assistant does not attempt a diagnosis.
Outcome: The call goes to the roadside assistance line or the on-call team through a priority queue.
Handover: Always. If anyone is hurt or in danger, the caller is told to dial 112 without delay.

6. Department and branch routing

Trigger: Callers for sales, service, spare parts or insurance work.
Details: Topic and branch.
Outcome: The assistant understands the topic and sends the call to the right queue; instead of a keypad menu (IVR), the caller explains what they need in their own words.
Handover: If the queue is full, a queue callback or voicemail.

For ready-made reminder and pickup scripts, see our appointment reminder call scripts; for after-hours and holiday periods, see the greeting and after-hours announcements and holiday announcements.

What the assistant should not do

No diagnosis. It does not answer “why is it making that noise?”; it takes the description and leaves it to the advisor.
No decisions on whether the car is safe to drive. Every safety question goes to an advisor or roadside assistance.
No firm prices or approval of extra work. It can share list prices from approved text in the knowledge base; extra work, discounts and final amounts are for the advisor.
No warranty or damage decisions. Warranty cover and insurance claims go to the right specialist.
No payment details. Card details are never read out over the phone.

Plates, mileage and dates: Turkish reading pitfalls

At a service centre, the assistant is most likely to slip on strings of letters and numbers. Test these separately before the pilot:

Plate formats. Turkish plates start with a province code followed by one, two or three letters, and the length of the number group varies. The assistant should always read the plate back to confirm it.
Spelling codes. Callers spell letters with city names, such as “A as in Adana” or “K as in Kayseri”; the assistant should understand this and be able to use it when confirming.
Mileage. “A hundred and twenty thousand”, “a hundred and twenty-odd” and “a hundred and twenty thousand five hundred” lead to different records; where an approximate figure is enough, the assistant should log it as approximate.
Long strings. Taking long strings such as a chassis number by voice is error-prone; where possible, match to the existing record by the registered phone number or the plate.
Dates and times. Phrases like “first thing Tuesday next week” or “around three in the afternoon” must map to the right slot in the service calendar.

Setup in five steps

Plan the number and departments. Set up separate queues for service, sales and spare parts; number options are in our guide to connecting your business number.
Write the knowledge base. Opening hours, services, courtesy car policy, list prices (if approved), directions and pickup rules.
Connect your service software. If job status and the service calendar can be read through an API or webhook, the assistant answers status questions and books appointments; if not, it collects requests and an advisor confirms.
Prepare announcements and the KVKK notice. A sample privacy notice for auto services is in our KVKK guide.
Test. Try plates letter by letter and with spelling codes, mileages (“a hundred and twenty thousand”) and workshop noise; in our test checklist, treat the licence plate item as critical for auto services.

KVKK and İYS notes for Turkey

This section is general information, not legal advice. Last checked: 2026-10-22.

Article 3 of Law No. 6698 on the Protection of Personal Data (in Turkish) defines personal data as any information relating to an identified or identifiable natural person. Once a licence plate and vehicle details are matched to a customer, they fall within that definition. Limit what the assistant collects to what the booking and service need (Article 4), and if you record calls, inform callers before recording starts (KVKK and call recording).

For outbound calls, separate three cases:

Pickup notifications and booking confirmations. These are notifications about an ongoing service; Article 6 of the Regulation on Commercial Communication and Commercial Electronic Messages (in Turkish) does not require prior consent for such notifications but prohibits promotion in them.
Scheduled service reminders. Article 6 of Law No. 6563 on the Regulation of Electronic Commerce (in Turkish) says that if the recipient gave their contact details so they could be contacted, no separate consent is needed for messages about changes to, use of and maintenance of the goods or services supplied. Whether a reminder stays within that scope depends on your relationship with the customer and what the call says.
Campaign calls. A winter tyre discount or a service package offer is a commercial electronic message and as a rule needs the customer’s consent recorded in İYS. Even for calls to merchants such as fleet customers, the number has to be registered in İYS and checked for an opt-out.

For details, see our guide to İYS consent rules.

Which metrics should you track?

Metric	How to calculate it	What it shows
Booking conversion	Calls ending in a booking ÷ calls with booking intent	How well the assistant completes requests
Share of status calls	“Is my car ready?” calls ÷ all inbound calls	How much pickup notifications relieve the line
Pickup notification reach	Customers reached ÷ customers called	Whether notifications go out at the right time
Bookings after reminders	Bookings made after a reminder ÷ customers reached	The real effect of the reminder flow
Missed call rate	Inbound calls ended without a conversation ÷ all inbound calls	The state of the line during drop-off and pickup hours

Sample call (fictional)

Fictional example: not a real call; the service centre, plate and names are made up.
It assumes the service calendar is connected to the assistant.
The call takes place in Turkish; shown here in English. Turkish plates start with a
two-digit province code, and callers often spell letters with city names.

Assistant: Hello, Yıldız Oto Servis. I’m the service centre’s AI assistant. How can I help?
Caller:    My car is due for its scheduled service. I’d like to book.
Assistant: Of course. Could I have your licence plate?
Caller:    Thirty-four, K, L, two hundred and twelve.
Assistant: Thirty-four, K as in Kayseri, L as in Lüleburgaz, two hundred and twelve. Is that right?
Caller:    That’s right.
Assistant: What’s the mileage on the car?
Caller:    About sixty thousand.
Assistant: Thank you. Thursday at 9 am or Friday at 2 pm are available. Which would you prefer?
Caller:    Thursday at nine. Also, the brakes are making a noise.
Assistant: I’m noting the brake noise for our service advisor; they’ll talk to you at drop-off.
           To confirm: Thursday at 9 am, scheduled service, note about brake noise. Your booking is made.

Auto service calls with Speakline

We build Speakline in Turkey. For automotive businesses, our voice agent answers service and sales calls in Turkish, collects the plate, model and request, and either books the appointment or passes it to a service advisor with a summary. With the HTTP request step in the call flow you can fetch information from your own system during the call, for example to find a record by the caller’s number; if your service calendar is connected, slots are offered from it.

You make pickup notifications and service reminders as outbound campaigns at the times you set, and in promotional campaigns numbers are checked against İYS records. You can set up separate queues for service, sales and spare parts and hand calls to an operator in our call center with a call summary (warm transfer); if the queue is full, a callback is logged. The summary, outcome code and transcript can be sent through the API and webhooks to your CRM or your own systems. Calls can be recorded and transcribed, and if a call flow has no KVKK notice before recording, the designer warns you. To adapt it to your service centre, get in touch.