Auto Repair Shop Sub-Account Kit

1. No. 01

   1 AI Receptionist

   Component 01 · AI Receptionist

   The problem

   A shop with three bays takes its heaviest call volume between eight and ten, exactly when the advisor is handing over keys, and an operator building that call flow by hand rewrites the same make, model and symptom script for every garage they onboard.

   Once it is loaded

   The receptionist lands already asking for registration, symptom and whether the driver needs a courtesy car, already reading bay availability from the calendar, and already escalating an undriveable vehicle to a person instead of booking it three weeks out.

   How it pays back

   If building a shop-grade call flow from a blank account costs six hours and you stand up five garages a year, that is a working week returned, and the first of those accounts is live in days rather than after a fortnight of scripting.

2. No. 02

   1 AI Chatbot

   Component 03 · AI Chatbot

   The problem

   Drivers ask two things before they book, whether you can look at it this week and what a diagnostic costs, and an operator answering that per shop ends up retraining the same assistant on labour rates and serviced makes for every account they open.

   Once it is loaded

   One assistant is live across the website, SMS and both Meta inboxes with the makes the shop declines already excluded, diagnostic and labour bands pulled from account values, and anything about brake or steering safety routed to a person rather than answered.

   How it pays back

   Assume the shop fields forty chat enquiries a month and a quarter arrive after the counter closes; if a third of those become booked work at an average ticket of four hundred, the account is defending revenue nobody was previously capturing.

3. No. 03

   Pipelines

   Not one of the nine — what they run on

   The problem

   Work a driver declined at inspection sits in a note on the job card and nothing moves it, and a vehicle waiting on a back-ordered part stalls with no stage to sit in. An operator drawing those boards fresh per garage invents the stage names again each time.

   Once it is loaded

   The account opens with boards for enquiry through to booked work, for declined items waiting on a return visit and for vehicles held on parts, so an advisor can see which cars are blocked and which deferred jobs are due back.

   How it pays back

   If a garage carries sixty declined items at an average of two hundred and eighty and a board plus a follow-up cadence recovers a tenth of them, the client sees a result in month one, which is the month agency churn actually happens.

4. No. 04

   Workflows

   Not one of the nine — what they run on

   The problem

   When a part slips to the following day somebody has to ring every affected driver, and authorisation for extra work has to be chased while the car is on a lift. Operators rebuild that branching by hand, then patch it per shop at three in the afternoon.

   Once it is loaded

   Authorisation requests, parts-delay notices, ready-for-collection messages and the escalation to the advisor when a driver does not reply within the hour are wired on load, with branches already reflecting whether the driver waits or drops the car off.

   How it pays back

   Rebuilding that logic by hand runs to eight or nine hours per sub-account once testing is included; across four garages onboarded in a year that is most of a billable week you keep, and none of it is time a client agrees to pay for twice.

5. No. 05

   Appointment reminders, confirmations and no-show recovery

   Component 05 · Smart Appointment System

   The problem

   An empty bay at nine in the morning cannot be refilled by lunchtime, and technician hours booked against a car that never arrives are simply gone. Configuring a ladder per appointment type, drop-off against waiter, is fiddly work an operator repeats at every account.

   Once it is loaded

   Confirmations carry the drop-off time and whether a courtesy car is held, reminders run at twenty-four hours, one hour and fifteen minutes, and a vehicle that does not arrive triggers a recovery call inside the hour against the seventy per cent recovery target the kit is designed to.

   How it pays back

   Take a shop losing six bookings a week to no-shows at an average repair value of three hundred and twenty; recovering seven in ten is the difference between a client renewing quietly and a client asking what the retainer is for.

6. No. 06

   Funnels

   Not one of the nine — what they run on

   The problem

   A garage sells a diagnostic, an inspection slot and a seasonal check, and each one needs its own path from advert to booked bay. Operators build those pages per shop, which means rewriting the same fee disclaimer and the same calendar embed for the tenth time.

   Once it is loaded

   Conversion paths for the diagnostic booking, the inspection or MOT month slot and the deferred-work return visit are in the account already, each pointed at the right calendar and each collecting registration and mileage before the driver reaches the thank-you page.

   How it pays back

   If an operator charges out at eighty an hour and an honest funnel set takes five hours per account to build, loading six garages in a year is thirty hours you keep, which is roughly the capacity to take on one more account.

7. No. 07

   AI Studio website

   Component 04 · Professional Website

   The problem

   Most garages arrive with one page, a phone number and photographs of the forecourt, and nothing that ranks for the work they actually want. Writing service copy for clutches, cambelts and diagnostics from scratch is the slowest part of any rollout an operator does.

   Once it is loaded

   The site arrives with pages per job type, an inspection-month booking page, a courtesy-car explanation the advisor stops repeating, forms wired into the same account and a structure a search engine can read without a separate optimisation pass.

   How it pays back

   Commissioning a written, structured site for a trade business sits somewhere between two and four thousand and takes weeks of back and forth; removing one of those builds per quarter from your delivery calendar is not a close arithmetic.

8. No. 08

   Nurture campaign

   Component 02 · AI Outbound Caller + Component 08 · Database Reactivation

   The problem

   A quote for a gearbox goes quiet on day three, a driver last seen fourteen months ago is in nobody mind, and the dormant list sits untouched in the old system. Assembling that outbound engine per account is a two-day job an operator does at a loss.

   Once it is loaded

   Stalled estimates are worked on a cadence, the outbound caller opens with the vehicle and its last service rather than an offer, and the dormant list is worked in throttled batches so a small shop is not swamped by returns it cannot book.

   How it pays back

   Assume a garage with eighteen hundred lapsed records and a two per cent return at an average ticket of three hundred; the client attributes that to you in month one, and a client who can point at a month-one number does not cancel in month four.

9. No. 09

   Review automation

   Component 06 · Review Harvesting + Component 07 · Review Automation

   The problem

   The moment a driver has keys in hand is the only moment worth asking, and the regular who comes in twice a year must not be asked twice a year. Operators tune that interval logic by hand per garage, usually only after a client complains about it.

   Once it is loaded

   The ask fires on collection with a satisfaction question first, the interval rule stops a returning customer being asked again too soon, platforms rotate, and the cadence is paced towards the five to ten reviews a month the kit targets.

   How it pays back

   A garage closing ninety repair orders a month needs only a small conversion to change what its search result looks like within a quarter; for the operator, a visibly growing profile is the easiest artefact to point at on a renewal call.

10. No. 10

    Seasonal automation

    Component 09 · Lifetime Nurture Campaigns

    The problem

    Inspection month, the first cold week and a service interval counted from the last visit all move per vehicle rather than per calendar, and an operator wiring anniversary maths into a fresh account each time is redoing date arithmetic that was solved years ago.

    Once it is loaded

    Inspection and MOT anniversaries fire from the vehicle record, service intervals count from the last invoice, winter and holiday check prompts are scheduled, and the referral offer goes only to drivers who have come back more than once.

    How it pays back

    If a shop has nine hundred vehicles on file and inspection anniversaries alone bring back one in eight at an average of two hundred and twenty, that is a line the client can verify, and a campaign you did not build for a tenth time.

11. No. 11

    Custom values

    Not one of the nine — what they run on

    The problem

    Bay count, the parts supplier cut-off time, whether courtesy cars exist at all and the hourly rate differ at every garage, and an operator who typed those into message bodies is opening automations one at a time when a fee goes up in April.

    Once it is loaded

    Hourly rate, diagnostic fee, parts cut-off, courtesy-car policy, inspection month wording and collection hours sit as account values read by every message, so a new garage is configured on one screen and a price change is a single edit.

    How it pays back

    If a labour-rate change touches a dozen message bodies and costs forty minutes to chase down, and seven garages under management each move a price or a policy twice a year, you have removed most of a working day of unbillable correction.

12. No. 12

    Custom fields

    Not one of the nine — what they run on

    The problem

    Registration, mileage, the makes a shop will not touch, whether a driver waits or drops off and what they declined last time are the fields a garage runs on, and an operator adding them per account gets the naming slightly wrong, which breaks filters later.

    Once it is loaded

    Vehicle registration, make and model, mileage at last visit, declined items with their date, courtesy-car eligibility and preferred contact time are on the contact record from load, named consistently so every workflow, board and message reads the same data.

    How it pays back

    Field drift is what quietly wrecks a rollout: if renaming and remapping fields across an account you built six months ago costs three hours, avoiding that on half the garages you manage pays for the kit without touching client revenue at all.

13. No. 13

    Forms and surveys

    Not one of the nine — what they run on

    The problem

    A booking request that arrives without a registration or a symptom is really a phone call, and a post-collection question sent three days late tells the advisor nothing. Intake for a garage means asking the right handful of things, which operators rediscover per account.

    Once it is loaded

    The booking form captures registration, mileage, symptom and whether the driver can leave the car; the estimate form asks what has changed since the last visit; and the post-collection survey is short enough that a driver in a car park will finish it.

    How it pays back

    Assume the shop takes twenty-five web bookings a month and each incomplete one costs a five-minute clarification call; two hours a month back at the counter is modest, but it is the visible relief that keeps a first-quarter client from drifting.

On purchase you receive two things: one snapshot link, and one PDF with full installation instructions. Installation is not in the kit price — load it yourself from the PDF, or add installation by us for $200 a sub-account. Every payback figure above is an illustrative scenario with its assumptions in the sentence, not a measured customer result.