
Bespoke AI team members for UK local businesses. They phone customers when the job is ready, confirm bookings and follow up once on quotes, always as an AI.
AIHi, this is the AI assistant calling for the garage. Am I speaking with Dave?
DaveYes, speaking.
AIThanks, Dave. Your Fiesta is ready to collect. If you would rather talk to someone at the garage, just say.
DaveNo, that is great. I will pick it up after work.
Saved to Dave’s record: collecting after work.
Every call is about the customer’s own job or booking, and each call type and script is agreed with you before anything is switched on.

AIHello, this is the AI assistant calling for the garage. Is that Sam?
SamIt is, yes.
AII am calling to confirm your car’s service on Thursday at 9am. Does that still suit you?
SamCould we make it Friday instead?
AIOf course. I will pass that to the team and they will confirm a new time with you.
Change request passed to the team.
Polite, honest and at a sensible hour.
When a job is marked ready, it calls the customer, tells them, and asks what happens next. At a garage, that means when they will collect the car. The answer goes straight onto their record.
It calls to confirm a booking that is already in the diary. If the customer wants to change it, it passes that to your team. It confirms who it is speaking to before mentioning any details.
For a quote the customer asked for, it makes a single follow up call. No pressure, no discounts and no upselling. If they want to go ahead, your team confirms it.
These are service calls to your existing customers. The rules below are part of every build, not settings someone can forget.
At the start of every call, and it never pretends to be a person.
If a customer asks for a person, it offers one and arranges a call back from your team.
We set its calling hours with you during the build: 8am to 8pm, Monday to Saturday, with Sundays and bank holidays blocked out.
At most two attempts per job, and only one follow up on any quote.
Existing customers, about their own job, booking or quote. No sales calls. If someone asks not to be called, that opt out is recorded and respected.
Your team messages it one to one by text. We are building WhatsApp messaging, and can add it as part of your build. It works from your own records and your own way of doing things.
TomCan you book the blue Corsa in for an MOT on Friday?
AII can book the Corsa in for an MOT on Friday at 9am. Shall I go ahead?
TomYes
AIBooked and logged. Shall I text the customer to confirm the booking?
TomYes
AIText sent and logged.
Two separate approvals from Tom, both logged.
It shows exactly what it is about to do, then waits. Small record edits happen straight away and are logged with a reference number. Bookings and customer messages each wait for their own yes, and quotes are saved as drafts for you.
Estimates are drafted from your templates and saved as drafts. Nothing reaches a customer until you check it and press send.
You approveAsk it to book a customer in. It shows exactly what it will do, then waits for a yes. If a job needs moving or cancelling, it passes that to your team.
After a yesJob ready, running late: it sends the update from an agreed message the moment someone on your team says yes.
After a yesIt lists the quotes still waiting, biggest first, and chases the ones you choose. Every chase is approved before it goes.
After a yesNew starters ask it how you do things. It answers only from the how to notes you have approved, shows which note it used, and asks you when the answer is not there.
Approved notes onlyToday’s jobs, a customer by name, due dates and your own price list. A garage can look a car up by reg and check its MOT date.
Read onlyUpdates contact details, adds notes and tags, logs new enquiries and sets tasks for the team.
LoggedAnyone on your team can ask “What’s on today?” and get a short summary of the day’s jobs and what needs doing.
On requestExample. A new starter at a garage asks what to do when they find extra work on a job. It replies from the owner’s approved note: stop, take a photo, have it priced, and do nothing without the customer’s yes. It names the note it used.
Every action has an approval level agreed with you before launch, and every change is logged.
Looking things up changes nothing, so it simply answers.
Small edits happen straight away and are logged with a reference number.
It shows exactly what it will do. The person who asked replies yes.
Saved as drafts. You approve them before anything is sent.
Set up and tuned around how your business works, tested properly and handed over to your team.
We map how your business really runs, list your tools, and agree in writing which tasks it handles and who approves what.
We set it up with your data, your notes and fixed steps for anything involving customers or money.
It runs on test data first. Nothing customer facing is switched on until you are happy.
Your team uses it for real while we review the log every day and refine it.
Training for each person, a one page guide, named approvers, and ongoing care after launch.
The tasks it handles, the calls it makes and who approves each one.
Every call type is scripted and signed off by you before it goes live.
Data processing terms, available on request, and help completing your data protection impact assessment.
Each change records who asked, a reference number and what changed.
Short sessions for each person, plus a one page guide to what it can and can’t do.
We keep reviewing and refining it as your business changes.
Most examples on this page come from a garage.
Stock photo, not a client
Stock photo, not a clientCar ready calls, MOT bookings confirmed and quotes followed up once.
Customers called when the job is done, and bookings confirmed before the van sets off.
Customers told when a job is finished, and quotes followed up once.
Appointments confirmed with the clients who booked them.
If you book jobs, send quotes and keep customers updated, we would like to hear how you work.
Case studies will appear here once our first clients have approved them. Until then, we are happy to walk you through a full build with test data on a call.
We agree in writing what it can see and what it can do before it goes live.
Data processing terms available on request, and help with your data protection impact assessment, with UK data protection rules in mind.
Each change records who asked, a reference number and what changed.
Yes. Every call starts with it saying it is the AI assistant calling for your business, and it never pretends to be a person. If a customer asks for a person, it arranges a call back from your team.
No. It only makes service calls to your existing customers, about their own job, their booking or a quote they asked for. At most two attempts per job, and only one follow up on any quote.
We set its calling hours with you during the build: between 8am and 8pm, Monday to Saturday, with Sundays and bank holidays blocked out.
No. Most examples on this page come from a garage, but every build is shaped around how one business works. We agree its tasks, its calls and who approves what with you during discovery.
Bookings and customer messages wait for a yes from the person who asked. Quotes are saved as drafts for you to approve. Every change is logged.
One to one by text. We are building WhatsApp messaging, and can add it as part of your build.
Every build is scoped individually, so we talk it through on a call once we understand your business.
A conversation about how your business runs, the calls that eat your team’s day, and what a bespoke build would handle.
Book a callWe use essential cookies to run the site. Our website host, HighLevel, also uses a visitor ID cookie to count visits. Accept to allow it, or Reject and we will remove it from your browser. See our privacy notice.