AI call intake for auto service: collecting the service request properly

The short answer

A call to an auto service usually has one purpose: the customer describes a problem and wants to know when they can bring the car in. An AI voice agent can fill in the service intake card on that call: make, model and year, a description of the problem in the customer's own words, how long the symptoms have been there, a preferred time and contact details. When the technician comes back to the call, they already know what it is about.

The key rule: the agent does not diagnose and does not estimate prices. "That's probably the shock absorber, about 200 manat" sounds like a promise to the customer and causes an argument when the workshop finds something else. This article shows the intake card, the question order, safety escalation and the split of work with the technician.

Calls an auto service line receives

• New repair request: noise, warning light, leak, a problem while driving
• Scheduled maintenance: oil change, inspection, seasonal tyres
• Status: is the car ready?
• Price question: a specific job or part
• Opening hours, address, queue
• Warranty and complaints

Scheduled maintenance and information questions suit the agent best. On a new-problem call, the agent collects information and the technician does the assessment.

The service intake card

1. 1VehicleMake, model, year; engine type and mileage if needed.
2. 2ProblemIn the customer's own words: "there's a knocking from the front left wheel when the engine is cold".
3. 3Since whenA week, a month, suddenly.
4. 4ConditionsWhen it happens: at speed, turning, braking, in the cold.
5. 5UrgencyIs the car drivable, is a warning light on?
6. 6Time and contactPreferred day, name, number.

Question order

Customers usually start with the problem, not the car. The agent should not interrupt; it should listen to the problem first, then ask for what is missing. The order: listen to the problem, confirm the vehicle, ask about conditions, check urgency, agree a time. Every question should be short — a long list of questions on the phone sounds like a survey.

The no-diagnosis rule

Customers often ask the agent "what do you think it is?" and "how much will it cost?". The agent's answer should be honest and short: "The technician will tell you the exact cause after inspecting it. The inspection costs X manat; the price of the work will be known after diagnosis." If the inspection or diagnostic fee is fixed, the agent can say it — that is approved information.

For scheduled services (oil change, tyre change), if there is a price list, the agent can quote it from the knowledge base. But notes such as "part prices vary by model" should be part of the answer too.

Safety escalation

Some symptoms suggest the car may be unsafe to drive: a sinking brake pedal, heavy steering, smoke, a smell of fuel, a red warning light. In these cases the agent should prioritise warning the customer and handing over rather than continuing the booking flow: "The symptom you describe could be dangerous; it's advisable not to drive the car. I'm connecting you with our technician." If there is a towing service, its contact is offered too. The list of key phrases should be approved by the head technician.

Scheduled maintenance calls

Oil changes, inspections, seasonal tyre changes — these are standard services, and the agent can record them fully: vehicle, service type, preferred time. When a season starts (winter tyres, for example), the number of such calls jumps in a short time and reception is overloaded. The agent answers without a queue during that peak, and a manager confirms the records against the workshop schedule.

Illustrative example: a multi-brand workshop

Not a real customer case. The workshop gets lots of calls in the morning, and the service adviser is juggling the phone and customers at the counter. The agent takes a call: the customer says "the car suddenly has no power". The agent asks for the model and year, since when, and about warning lights — an amber light is on, and the car is drivable. A diagnostic slot is booked for the next day.

The next morning the technician reads the card: "2016, diesel, two days, loses power at high speed, amber light". They call the customer and confirm how much time the diagnosis will need. The customer does not have to explain everything a second time.

Dividing work with the technician and service adviser

The agent fills in the intake card, the service adviser confirms the time against the workshop schedule, and the technician talks about diagnosis and price. This split lets everyone do their own job. What matters is the quality of the card: if the technician reads it and still asks the customer the same questions, the question list in the scenario needs fixing.

What to measure

• The share of fully completed intake cards — which field is left empty most often
• The share of recorded requests that become actual workshop visits
• Calls handed over on safety key phrases, and their review
• Waiting time and abandonment during the morning peak
• How often the technician has to ask extra questions — a measure of card quality

Common mistakes

• The agent suggesting a likely diagnosis or a price for the work
• Converting the problem into technical terms and losing the customer's words
• Continuing the booking flow when dangerous symptoms are described
• Presenting a request as a confirmed workshop slot
• Answering status questions without data from the workshop system

Limits

Information collected on the phone does not replace diagnosis; the customer's description may be inaccurate. Safety warnings are general in nature and not a technical assessment. Information such as whether a car is ready needs integration with the workshop system; without it the agent does not know the status and should say so honestly.

A service line with Vexvon

In Vexvon AI Call Center the intake card fields — vehicle, problem, conditions, urgency, time — are defined in the scenario, and the agent extracts them from the call and writes them to the customer card; a field that was not found stays empty. Answers come from the knowledge base, so scheduled-service prices and opening hours are written once. Dangerous symptoms or difficult questions are passed to a live member of staff. You can give the agent your own API as a tool — for example, to get a status from the workshop system; that requires integration.

Outbound calls to remind customers about maintenance are covered in vehicle service reminder calls, and calls never given to the agent in when not to use an AI voice agent.

First step

With your head technician, write the intake card in six fields and check last week's ten calls against it: which information is always missing? More articles are in the inbound calls by industry section; to discuss a scenario for your service line, get in touch.