Answered every after-hours WhatsApp and website enquiry within a minute for a three-location auto repair group
Client snapshot
An independent auto repair group with three locations and one shared service desk. Most new customers find them through a search and message first, on WhatsApp or through the website, usually in the evening after work.
The problem
Half the enquiries came in after the service desk had closed. They got answered the next morning, sometimes the next afternoon. By then a good share of those people had booked somewhere that replied first. Most of the questions were the same ten: what a service costs, how long it takes, whether they need to book, which location is open Saturday, the next free slot.
What we built
One assistant behind two channels.
Messages to the group's WhatsApp number and the website chat both go to n8n. Claude answers from a short, approved FAQ the group wrote: standard service prices, turnaround times, locations and hours. It doesn't diagnose or quote repairs. Anything about a specific fault gets a set reply and goes to the service desk.
If the person wants to book, they get one qualifying question (which location, and the car's make and model) and a booking link with live slots from Cal.com. Every conversation is logged in Pipedrive with the channel, the outcome and the transcript.
Anything the assistant can't answer goes to the service desk with the conversation attached, so staff pick it up in the morning without asking the person to repeat themselves. A 6am email lists the last 24 hours: who booked, who's waiting on staff, who went quiet.
WhatsApp only answers people who messaged first. The group doesn't use it for cold outreach.
Results, six weeks in
- After-hours enquiries answered: none until morning → all of them, in under a minute.
- About 35% of enquiries booked a slot with no staff involvement.
- Around 30 more bookings a month across the three locations.
- The service desk starts the day with a short list of conversations that actually need a person.
Quote
"The questions we answered fifty times a week now answer themselves. We only see the ones that need us." Operations manager
Build snapshot
- Timeline: 5 business days
- Stack: n8n, WhatsApp Cloud API, Claude, website chat widget, Cal.com, Pipedrive
- Investment: $1,800
- Who owned it: the operations manager wrote and approved the FAQ answers; the service desk handles the handoffs.
The pattern
This is the pattern we ship in the Missed-Lead Rescue engagement. Here the channels were WhatsApp and website chat instead of missed calls and SMS. The build is the same, with your channels and booking tool swapped in.
This is an illustrative composite drawn from operator engagements. Names, identifying details, and exact metrics are anonymised. The workflow, stack, and approach are real.
Looks like your situation?
A 30-minute call tells us whether the same pattern fits your operation, and what it would cost to ship it.