Automotive
Service reception is always already with somebody.
At a garage, the person on reception has a car on the ramp, a customer in front of them and three calls waiting. A missed call loses more than a booking for today: it loses a customer for the next three years of maintenance. The assistant takes the repetitive half of those calls.
The assistant takes service and repair bookings, records the make, model, registration and the symptom as the customer described it, offers a real slot from the workshop calendar, confirms by SMS, and passes quote requests and sales calls to an adviser.
What it lifts off the reception line
A garage runs two completely different flows on one number: maintenance, which is predictable, and sales, which is not. The assistant takes the first flow end to end, and qualifies and hands over the second.
A service booking
Mileage, service type and a slot chosen from the workshop calendar, against the right kind of job.
A repair with a symptom
The customer describes the noise or the fault, and the assistant records it exactly as they said it, without diagnosing.
The status of a job
If your system has an API, the assistant can read the work order status. Without one, it takes the question and hands it on.
A parts enquiry
Make, model, year and the part wanted, recorded as a request for a person to pick up.
A sales call
Interest in a particular model, budget, timing and whether there is a part exchange. It goes to the CRM as a lead.
The day-before confirmation
It dials tomorrow bookings so a ramp is not held for a car that never arrives.
From the call to a car in the workshop
The flow is built on the workshop calendar, because that is the system nearly every garage has, unlike a management package with an open API.
- 01 Separate service from sales The first question splits the call in two: are you bringing a car to us, or buying one. After that point the two roads have nothing in common.
- 02 Identify the car Make, model, year, mileage and registration, read back for confirmation, because a wrong registration means the wrong parts ordered.
- 03 Record the symptom literally The customer description goes in as text, word for word, into a structured output. The assistant does not translate a noise into a fault.
- 04 Find the slot It calls the availability tool against the workshop calendar and offers real times, allowing for how long that kind of job takes.
- 05 Confirm and write onward SMS with the time and address, the calendar event, and on the sales road a lead in HubSpot or Pipedrive with a call note attached.
What reaches your systems
The difference between a call that was answered and a call that was useful is what gets written down. The rows below are written during the call, by tools.
| In the workshop calendar | The booking, with the registration, the job type and the symptom in the description. |
|---|---|
| In the CRM | On the sales road, the contact and the deal in HubSpot or Pipedrive, with the call note on the contact. |
| By SMS | The booking confirmation and, if you want it, the day-before reminder. |
| On the call record | The transcript, the tools called, and the structured output with car, job and symptom. |
What it does not do for a garage
In a garage a wrong assumption costs a part ordered for nothing, so the list below is written tightly.
- It does not diagnose It does not say what is wrong with the car, does not estimate severity and does not confirm whether it is safe to drive in. It records the description, and that is all.
- It does not quote It does not estimate the price of a repair nobody has looked at. At most it reads a fixed price from a list you maintain.
- No link to your management software There is no ready-made connector for the garage management systems used in Romania. A work order status reaches the call only through your own HTTP tool or an MCP server.
- It orders no parts and takes no money It places no supplier orders and takes no deposits over the phone.
- It does not check vehicle history It has access to no vehicle database, not even yours unless you give it one explicitly through a tool.
What garages ask us
Can it say what a service costs?
Only if it is a fixed price you keep in a list and hand it as a knowledge base. For anything that depends on what is found once the car is stripped, the assistant is configured to say the quote is done at reception. A price estimated on the phone and contradicted in the workshop costs more than the call did.
How does it cope with registration numbers?
It reads them back letter by letter and asks for confirmation. That is the only approach that works, because transcription consistently confuses letters that sound alike over a phone line. The same rule applies to phone numbers.
Can it take sales calls for new cars too?
Yes, as intake and qualification rather than as selling. It records the model of interest, the budget, the timing and whether there is a part exchange, writes the lead to the CRM, and — if the adviser calendar is connected — offers a test-drive slot directly.
Does it work for a small garage with two mechanics?
Yes, and that is where the ratio is best, because a small garage has nobody dedicated to the phone. You do not need a switchboard: one Twilio number routed to the assistant is enough, and the phone-number guide covers the steps.
Where to go next
Integrations
25 business connectors, 18 selectable providers, eight storage destinations.
Tools and MCP
Discovery, per-tool permissions, per-server namespacing, and a tool of your own.
Telephony
Numbers, trunks, dial plan, queues, operators and campaigns, in one system.
Pricing
Components at their published price, the platform on top, and what we cannot price yet.
See it working on your own business
Five short steps. At the end, if you want one, an AI assistant rings you and handles a call the way it would handle yours.
- 01 Your business
- 02 What we found
- 03 What it should do
- 04 Connections
- 05 Your number
What you get, and what it costs
- A telephone number of your own, answered by an assistant built from what your website says. You can ring it the same day, from the phone in your pocket.
- Five steps, about four minutes. Reading your site takes half a minute, and after payment the number is usually live in under a minute.
- One payment: €3.00 for the first month of the number, plus the credit your calls are drawn from — the smallest bundle is €10.00. No subscription, no contract.
Calls cost €0.12 a minute, whoever rings and from wherever.
- €10.00 roughly 83 minutes of talking
- €20.00 roughly 166 minutes of talking
- €50.00 roughly 416 minutes of talking
From the second month the number costs €3.00 a month, taken from the same credit. If the credit will not cover it the number keeps answering for 14 days before it goes back to the pool.
What the assistant knows is built by reading your website, and an automated reading can get things wrong. That is why step two shows you everything we found, with a link to the page each fact came from, and you correct it before you pay — not after your first real call.
Nothing is built and nothing is charged until you pay. What you fill in is saved, and the link brings you back to it.
Notes
-
1
The tools named on this page are the ones in
App\Services\Integrations\ConnectorRegistrycarryingimplemented. Anything that is only in the catalogue, without that flag, is not named here as though it worked. -
2
The sales lead uses the
create_contactandcreate_dealcapabilities of the HubSpot and Pipedrive connectors, both flaggedimplementedin the registry.