01
Booking service or a repair
- It asks
- Year, make and model, the kilometres, what the car is doing (a noise, a warning light, a leak), and whether they will wait, drop it off or need a ride.
The problem
Where the work leaks.
The phone rings hardest at the same moment the workshop is busiest. Service intervals come round quietly, and the customer who was happy in March books somewhere else in September because nobody reminded them.
On the phone
The calls a repair shop gets while the bays are full.
Most calls to a shop are about booking, a car already in, or the seasonal tire rush, and each has a short list of questions.
02
Checking on a car already in
- It asks
- The name and vehicle on the work order, so the service desk can call back with an update instead of the caller holding.
03
Tire changeovers and inspections
- It asks
- Which work, whether they have their own tires or rims, and the days that suit, which matters most when the changeover rush fills the phone.
Flagged urgent
A car that has broken down, a stranded driver, or brakes and steering that feel wrong are marked urgent for the service desk. The assistant does not diagnose; it records the symptoms in the caller's words.
Booking tools
Shop management systems are not connected directly. Bay times kept in Google Calendar can be booked directly; otherwise the request is captured and the customer is sent your own booking link.
What we set up
Three that fit this work.
Each one is described by what sets it off and what then happens — so you can check it rather than take it on trust.
01
Booking
- Starts when
- A customer calls or messages asking for a slot.
- What happens
- Real availability is offered from your diary, the vehicle and the work are recorded, and a confirmation goes out.
02
Service reminders
- Starts when
- A service or inspection interval approaches.
- What happens
- A reminder goes to the customer with a way to book, timed to the interval rather than sent in a monthly batch.
03
Review requests
- Starts when
- A job is marked complete.
- What happens
- A request goes out with a direct link, after a short delay rather than the moment the customer collects the keys.
Works with: AI receptionist · missed-call text-back
Example scenario
A brake job in March, an inspection reminder in September
The visit is recorded with the vehicle and the work. Six months later a reminder goes out referencing the right car and the right interval, with a link to book. Nobody had to keep a spreadsheet.
A worked example of how a run takes shape.
Scope
What this does not do.
Review requests go to all customers alike, with no filtering by expected sentiment. Selective asking breaches most platforms' terms.
01
Map
A session on how enquiries reach you now, which ones are missed, and what should happen instead.
02
Script
The greeting, the questions asked and the routing rules, written down for you to change before anything is built.
03
Build
Wired to your number, calendar and records, then tested end to end on a line that is not yours.
04
Launch
Live with a rollback path. We watch the first days of real enquiries and adjust against what people actually say.
Pricing
Month to month, published in the open.
Plans start at $299 a month plus $299 setup, including 200 voice minutes. Cancel any month.
Questions
Auto Services: common questions
Where we work
Where we work for Auto Services teams.
Carrtel supports Auto Services teams in Calgary, Airdrie, Cochrane, and Okotoks. Service delivery is remote: planning, setup, and ongoing support happen online or by phone, without requiring a local office visit.
Other industries
Same setup, different shape.
Start with whatever costs you most.
A short call to map where enquiries are being lost, and what it would take to close the largest one.