A reference build for any appointment-based service business: one system that answers every inquiry in under a minute, on every channel, at every hour — and keeps working on the customers you already have.
Read this as a blueprint, not a testimonial. No real client is named here. The business profile is a composite of the service companies this system is built for, and every figure below is a worked model from stated inputs — not a verified outcome. Your numbers go in the calculator further down.
The gap between those two bars is the whole engagement. Everything else in this case study is built to hold that second bar in place.
The profile this system was designed against: an owner-operated service company, five to ten years old, taking 40–70 inquiries a week across Messenger, web forms, Google Business, and the phone. Good reviews. Skilled crew. No CRM, no automated intake, no after-hours coverage. Every reply is typed by a person who is already on a job.
Messages sent between 6pm and 8am wait until morning. That window is when most people actually shop for services — evenings, weekends, in bed, on a phone.
An existing base of service or maintenance customers with no recall system. Most come back once a year when the cycle calls for three or four visits.
Lead status lives in spreadsheets, inboxes and phone notes. Nobody can answer "how many inquiries did we get last week, and what happened to them?"
"You message a company, nobody gets back to you, so you move on and find someone else." The same sentence, in every service category, in every market
A business at this volume usually has enough inquiries to hit its booking target already. The constraint is responsiveness, not lead generation. So every inquiry — any channel, any hour — routes into an automated intake conversation that qualifies, quotes, and books. A human enters only once there’s a real job on the table.
Fires on any new message or form submission. Captures service type, job details, budget acknowledgment and preferred schedule, then books directly into the calendar.
A four-touch SMS chain from booking confirmation through to "we’re on the way," so the appointment that was booked is the appointment that happens.
For everyone who started the conversation and stopped. Two SMS touches plus one value-add email, spaced so it reads as helpful rather than desperate.
Fires on a set interval after a completed job, pulling the existing customer base back into the calendar on the cycle the service actually calls for.
What changes operationally on the day the build goes live.
| Function | Before | After |
|---|---|---|
| First reply | 2–3 hours, if someone is free | Under 60 seconds, always |
| Coverage | Business hours, manual | 24/7 intake with a 9am human SLA |
| Lead tracking | Spreadsheets and phone notes | One pipeline with stage-by-stage visibility |
| Repeat business | Whoever remembers to call | Automated recall on a fixed cycle |
| Drop-offs | Nothing recovered | Three-touch recovery sequence |
| Reviews | Asked for occasionally | Requested 3 days after every completed job |
| Reporting | Gut feel | Weekly inquiry, booking and show-rate counts |
These are the targets a build like this is held to, and the numbers tracked in the pipeline from day one.
Illustrative targets. Figures below are modelled from the composite profile described in Phase 01. They are what the system is engineered to hit, not results collected from a live account.
Four questions you already know the answer to. Everything is worked out in plain sight on the right, so you can see exactly where each number comes from.
This is the only guess on the page. Keep it modest — five extra jobs per hundred is a realistic starting point, and the number still adds up.
Worked example: 240 inquiries a month at 25 jobs per 100 is 60 jobs. At 30 per 100 it’s 72. The extra 12 jobs, at ₱3,750 each, is ₱45,000 a month or ₱540,000 a year. Currency buttons change the symbol only; no exchange rates are applied. This sizes the opportunity. It is not a promise of results.
The build isn't handed over as a folder of workflows. Positioning, messaging and technical architecture arrive together, because a fast reply saying the wrong thing is still a lost job.
The architecture doesn't change by industry — what changes is what counts as an inquiry, what a recall is called, and how long the cycle runs. A few worked examples.
| Business type | The inquiry is | Recall fires on | Typical cycle |
|---|---|---|---|
| Home services | A repair or quote request | Maintenance due since last visit | 3–6 months |
| Dental and medical clinics | A first-appointment request | Recall or check-up interval | 6 months |
| Aesthetics and wellness | A treatment consultation | Top-up window for the treatment | 4–12 weeks |
| Fitness studios | A trial class booking | Lapsed attendance | 2–4 weeks |
| Auto service | A service or diagnostic booking | Mileage or time since last service | 6 months |
| Professional services | A consultation request | Annual filing, renewal or review date | 12 months |
Automation is a multiplier on an operation that already works. If the underlying business has a different problem, this build will make that problem faster, not smaller.
I build marketing automation systems that turn ignored inquiries into booked work — without bolting on more ad spend. Bring your inquiry volume and your average job value, and we'll size it in one conversation.
