Loading
In most local service businesses one person is sales, scheduling, dispatch and accounts. Every one of those roles competes for the same attention.
Enquiries arrive while the owner is on site, quoting, or driving. Calls go unanswered, quotes are promised and delayed, jobs are scheduled from memory, and follow-up on an unaccepted quote almost never happens. The business is not short of demand - it is short of a coordination layer, and hiring for that is expensive before revenue is predictable.
Written out step by step, because naming the process is what makes it possible to see where it breaks.
By call or WhatsApp, usually while the owner is mid-job.
No record the enquiry existed; the customer calls a competitor.
Repeated back-and-forth to establish job type, location and access.
Scheduled informally, often rearranged.
Prepared in the evening, sent late.
Rarely happens; unaccepted quotes are simply dropped.
Held in the owner's head and a paper diary.
Two automations change the economics. First, never miss an enquiry: an agent answers, captures job type, location, urgency and access details, and books the estimate. Second, chase every quote automatically - a structured three-touch follow-up on quotes that have not been accepted is usually the single highest-return automation a service business can run, because the work is already scoped and priced.
Trigger
A quote is marked as sent and remains unaccepted
An illustrative exchange, written to show scope and tone. Names and details are examples, not transcripts from a real customer.
Enquiry captured while the owner is on a job
Every industry has lines automation should not cross. These are the ones we build in deliberately rather than discover later.
The same eight steps on every engagement. Scope is decided in discovery, not assumed beforehand.
Understand the existing process, the tools already in use, and where the real bottleneck sits.
Map the conversations, data, business rules and actions that make up the workflow today.
Decide what should be automated, what should be integrated, and what needs to be custom-built.
Develop the AI agents, automation logic or software the architecture calls for.
Connect the solution to the CRM, calendars, databases and channels you already run.
Test the workflow end to end, including edge cases, failure paths and access permissions.
Deploy with monitoring and a rollback path, and hand over documentation.
Monitor real usage, measure against the original bottleneck, and refine.
It is most worth it at small size, because the constraint is attention rather than headcount. Start with one automation - missed-call capture or quote follow-up - and judge it on a number you can see, like quotes accepted. If it does not move, it was a small commitment.
For standard jobs with a fixed rate card, yes. For anything that needs assessment it captures the requirement and books the estimate instead. Letting an agent improvise a price on a non-standard job is how you end up honouring a quote you cannot deliver.
Most do, and the automation is built to get them to you faster with the details already gathered. It answers when you genuinely cannot, and the alternative to an automated answer is not a personal one - it is a missed call.
Ongoing cost is mostly third-party usage - telephony minutes, WhatsApp message fees, AI model calls - which scales with volume and is usually modest at small-business levels. We put the expected running cost in front of you during scoping, because a solution you cannot afford to operate is not a solution.
Describe how the process runs today. We will come back with what can be automated, what should stay with your team, and what it would take to build.
