AI Receptionist
Takes bookings while the counter is busy with a handover, asks make, model and symptom, and books into real bay availability rather than promising a call back.
- Books into bay availability
- Captures make and symptom
- English and Spanish
Theme
Palette
Saved to this browser. Applied before the page paints, so it never flashes.
Home & trade · SK-AUTO
Configured for a busy service counter: bookings taken without interrupting the bay, approvals chased, service intervals remembered for the customer.
What is in the kit
Every SubaccountKit snapshot contains the same nine components and nothing else. What changes between kits is what they are configured to say and do — everything below is written for the Auto Repair Shop Sub-Account Kit, laid out in the order it runs.
Stage 01Lead capture and first contact
Takes bookings while the counter is busy with a handover, asks make, model and symptom, and books into real bay availability rather than promising a call back.
Answers the questions that decide whether someone books — can you look at it this week, roughly what does a diagnostic cost, do you handle this make — on web chat, SMS and Meta.
Service pages written per job type, a booking calendar on each, and forms that capture registration, mileage and symptom so the first call is useful.
Stage 02Ten days of multi-channel follow-up
Chases authorisation on a car that is already on a lift, calls no-show bookings the same morning, and rings customers whose service interval has passed.
Stage 03Booking and no-show prevention
Bookings confirmed with drop-off instructions, reminded at 24 hours, 1 hour and 15 minutes, and recovered within the hour when a car does not arrive — because an empty bay cannot be refilled at short notice.
Stage 04Reviews and social proof
Collection is the ask. Completion fires one satisfaction question while the customer has the keys and a working car, then routes to the public link or a private form.
Keeps the garage profile growing without asking the same regular every oil change: interval-aware asking, platform rotation and a monthly count of repairs against reviews.
Stage 05Lifetime client nurture
Customers who have not been back in six months are the largest recoverable list a garage owns. The AI call leads with the vehicle and its last service, not with a discount.
Service interval reminders paced from the last visit, seasonal tyre and check prompts, MOT or inspection anniversaries, and a referral offer for long-standing customers.
The same nine ship in every kit in the catalog. Delivered within 1–2 business days of purchase confirmation. 12 hours of dedicated installation support, to be used within 14 days of purchase.
The end-to-end run
From a stranger’s first ring to a client of several years. This is the flow the Auto Repair Shop Sub-Account Kit wires into a sub-account on day one — the nine components above are what you get, and this is how they run together.
A stranger makes contact
Multi-channel entry with intelligent routing
The call is answered on the first ring, at any hour, in a natural speaking voice.
The same assistant, on every inbox the business owns.
A submission is the start of a sequence, not an entry in a spreadsheet.
They are interested but not ready
A ten-day multi-touch sequence across three channels
Establish who this is and why they should keep reading.
Shorter, closer, easier to act on from a phone.
The touch almost every sequence is missing.
They have booked
Protecting the slot from the moment it is taken
Confirmation lands before they have closed the tab.
Three reminders, three different jobs.
The slot is missed, and the phone rings while the intent is still warm.
The repair is done
Turning finished work into public evidence
Two hours after the repair, one question decides where it goes.
Reviews are answered, which is half of what a profile is judged on.
The reviews go back onto the site rather than sitting on a platform.
They are a client
Keeping the relationship alive for years, not weeks
Low frequency, long horizon, never silent for a whole year.
Existing clients get answers without waiting for office hours.
Nobody is allowed to quietly disappear.
The two performance figures above — a 70% no-show recovery rate and 5–10 reviews a month — are the system's design targets, supplied by the product team. They are not measured results from named customers, and they are never published as review or rating markup.
The problem it is pointed at
One person runs the counter and the phone. Bookings are lost all day and nobody counts them.
A vehicle on a lift with unauthorised work is dead bay time, and chasing the authorisation depends on somebody having a spare minute.
The most predictable revenue in the business relies on the customer remembering, because the garage has no reminder system.
Decades of goodwill and a handful of reviews, because nobody ever asks the customer collecting their keys.
Built for
Not built for
If you are in the second list, say so and we will tell you what would actually help — or that nothing we sell would.
An independent garage taking 120 calls a week, missing about 30, with an average repair worth $420 and a 40% close rate on recovered calls.
~16.5 hours a week in this illustrative scenario — roughly 71 hours a month. Your figures will differ; the arithmetic is shown so you can substitute them.
When it pays back
Four recovered calls a week at $420 and a 40% close rate is roughly $2,900 a month in this scenario, against a one-time kit price. The sixteen hours a week off the counter is what the owner notices first.
Run your own numbers
These are not measured customer results and never will be presented as such. They are arithmetic. Change any field and the sentence below changes with it — including the sub-account multiplier, because most people reading this are rolling the Auto Repair Shop Sub-Account Kit out across more than one client.
Illustrative arithmetic only. It assumes every missed enquiry is answered and that your own close rate holds on recovered contacts — neither is guaranteed, and both depend on your offer and your team. No figure here is a measurement from a real customer, and none of it is published as review or rating markup.
In most independent garages the person answering the phone is also the person handing over keys, explaining an invoice and taking a payment. Calls get missed constantly, and each one is a booking that went somewhere else. The receptionist answers them all and books into real bay availability.
A car on a lift waiting for authorisation is the most expensive thing in the workshop. When approval is needed, the customer is messaged, reminded and — if the car is still waiting — called. That single loop pays for the system in most shops.
A garage’s most reliable income is the customer who comes back on schedule. Interval reminders run from the customer’s own last visit rather than a blanket monthly email, keyed to the service type during installation.
Keys in hand, invoice explained, car running properly. Review harvesting fires there, which is a different result from asking a week later.
Wiring the kit to your workshop management system is an integration build.
Delivery and support
Clear edges make a better engagement than a long list of exclusions. Here is where the included support ends and where a quote begins.
Included with every kit
Quoted separately, or run by a VA
All four are real services we offer — seeintegrations, APIs and custom software. They are scoped and quoted so you know the cost before anyone starts.
Reviews
These are sample entries. SubaccountKit is new, so rather than invent testimonials we are showing clearly-labelled placeholders while the deck waits for real customers. Nothing here is published as review or rating markup either — search engines see no ratings from this site until the words are real.
This is a preview card so the review deck can be styled and tested before real feedback exists. The kit went into a fresh sub-account, the load sheet listed every custom value in order, and the build was finished before lunch.
Placeholder copy standing in for a real review. The point being illustrated here is the follow-up ladder stopping the moment someone books, which is the thing most sequences get wrong.
A preview entry, not a customer quote. It exists so the deck renders with a realistic length of text and the shuffle animation can be judged honestly before launch.
Sample text. Deliberately four stars rather than five, so the star row is tested at more than one value and the layout is proven before real reviews arrive.
Another preview card. Real reviews will replace every entry in this file, and the same change that swaps them in also switches the review structured data on.
When a job needs authorisation, the customer is messaged, then reminded, then called by the outbound component if the car is still on a lift and nobody has answered. That is dead bay time, and it is expensive.
The last visit. Interval reminders are set during installation per service type — oil, inspection, timing belt, seasonal tyres — and the lifetime nurture component paces them from the customer's own history.
Not for the core configuration. If you want job-created and job-completed events flowing in automatically, that is an [integration build](/services/integrations-apis-custom-software/).
Ready when you are
Delivered within 1–2 business days of purchase confirmation, with 12 hours of dedicated installation support to use within 14 days.
No call required to buy a kit · replies within one business day
Accessibility
Text size
Display
Turning animation off tears down the WebGL grid and the particle field — they stop running, they are not just hidden.