Booking requests
No more lost bookings. Requests from every channel land in the diary with the car, the job and a suggested slot, ready to confirm.
Hours back
7
hours a week back, typically
How it runs
What we build, step by step.
This is the usual shape. Yours gets built around how your team actually does the job.
- 01
Every request in one place
Emails, web forms, texts and WhatsApp messages are read as they arrive. Missed calls get a text back offering to book by message.
- 02
The details the advisor needs
The vehicle, the problem in the customer's words, and when they can drop off. If anything's missing, the customer is asked for just that.
- 03
A suggested slot
A slot is proposed from the job type and what's free in the workshop. Longer jobs don't get squeezed into short gaps.
- 04
Confirmation once the advisor accepts
The advisor accepts or changes the slot, and the customer gets a confirmation with the drop-off time and address.
- 05
A reminder the day before
A text the day before cuts no-shows, with an easy way to move the booking.
Shown with software we see a lot. If your team uses something else, we build it into that instead.
Built for your business
Same job, different business. We build yours.
Two firms in the same trade rarely run a job the same way. Different software, different steps, different people signing off. We build it for your business, around how your team actually does the job.
Your steps
Built around the order your team already works in, odd exceptions included.
Your software
Runs inside the tools you already pay for, set up the way you use them.
Your rules
Your wording, your limits, your sign-offs. Nothing generic goes out in your name.
You sign off
Your team keeps the final say.
The advisor confirms every booking. Anything that sounds unsafe to drive, like brake failure or warning lights, goes straight to a person.
What it's worth
What those hours add up to.
7 hours a week, over 46 working weeks, is 322 hours a year. At $50 an hour, that’s
$16,100
back in the business, every year.
Typical, not promised.
Before and after
The job, before and after.
How it runs today
Requests come in by phone, email, web form and the odd Facebook message. The advisor scribbles them on a pad, rings back for the reg and the problem, then finds a slot. After-hours requests wait until morning, and some get missed.
What we build
- Every request in one place
- The details the advisor needs
- A suggested slot
- Confirmation once the advisor accepts
- A reminder the day before
A month in
After-hours enquiries are booked by morning, nothing sits on a scrap of paper, and your advisor gets around 7 hours a week off the phone.
Why the advisor still confirms
Your advisors know which technician is off, which job will overrun and which customer always turns up late. The system proposes a sensible slot, and they make the call in one click.
Once you trust its suggestions, you can let routine jobs like an oil and filter book straight in.
FAQ
Can it answer the garage phone?
Not at first. Booking requests start with the written channels and a text back to missed calls, which moves a lot of callers to messages. Answering live calls can be scoped separately.
Will it quote a price for the job?
Only for fixed-price items on your menu, like a standard service. Anything that needs diagnosing gets booked in for a look, not priced by message.
More for automotive
See them all →Next step
Bring this one to a free live build.
Thirty minutes on booking requests. We build its elf with you, live, and you keep it.