The Cancellation Nobody Chased
A pest control company in Burnaby had a solid booking process. CRM, online scheduler, automated confirmation emails. By most measures, they were running a tight operation.
Then I pulled their cancellation data from the last six months.
Forty-one cancellations. Twelve were filled by someone manually calling through a waitlist. The other twenty-nine just sat there as empty slots on days where a tech was already in the area, already paid, already driving.
That’s somewhere between $5,800 and $8,700 in revenue that evaporated quietly. Not from a bad sales process. Not from a lousy website. From a coordination gap that nobody was watching.
What Automation Gets Wrong
Most service businesses have automation. CRM sequences, booking software, confirmation texts. The problem is that these tools are built for happy paths. They do exactly one thing when exactly one condition is met.
A Zapier workflow will send a cancellation notification when someone cancels. That’s it. It does not know that the tech is already four blocks away. It does not know there are three people on a waitlist who live near that address. It does not know that one of those people submitted a quote request eight days ago and never heard back.
Rule-based automation executes instructions. It does not make decisions.
An agentic workflow does something different. When the cancellation comes in, it reasons through the situation: Who is available? Who is closest? What type of job is it, and who is certified for it? Has anyone on the waitlist already been contacted this week? Is there a follow-up from a previous estimate that matches this time slot?
Then it acts. It reaches out to the best candidate, updates the schedule if they confirm, and closes the loop without anyone touching it.
The difference is not complexity. It is judgment.
Where the Leakage Actually Happens
Cancellations are one example. The same pattern shows up in a few other places I see consistently with service businesses:
Estimates that don’t convert. A homeowner gets a quote for duct cleaning, says they need to check with their spouse, and disappears. Most businesses send one follow-up email and move on. An agentic workflow can track where that lead is in the decision cycle, wait an appropriate amount of time, and follow up with something contextually relevant — not a generic “just checking in” blast.
Reviews that never get requested. The job goes well. The tech drives away. Nothing happens. Reviews are the most underleveraged asset a local service business has, and the window to ask for one closes fast. An agentic workflow sends the request at the right moment, through the right channel, and follows up once if there’s no response.
Seasonal rebooking. A customer had their furnace serviced in October. By August of the following year, that relationship is cold. A workflow that monitors the calendar and initiates outreach before the busy season — with specific context about what was done last time — is worth more than most ad budgets.
None of this requires a massive tech stack. Most of it can run on top of tools the business is already using.
What This Is Not
I want to be clear about the tradeoffs.
Agentic workflows make mistakes. They occasionally contact someone who does not want to be contacted. They sometimes misread context. A workflow that is not set up carefully can come across as spam rather than service.
This matters more for service businesses than most people admit, because the relationships are local. If a pest control company sends an awkward automated message to someone in a neighborhood where the tech is known personally, that lands differently than an email from a national brand.
The answer is not to avoid automation. The answer is to design it with guardrails. Review thresholds. Opt-out handling. A human in the loop for anything sensitive. The goal is to handle the routine decisions automatically so that humans can focus on the ones that actually need judgment.
The Real Question
The service businesses I work with are not short on leads. They are short on capacity to handle what they already have.
Calls come in after hours and get lost. Cancellations open up slots that stay empty. Estimates go cold without follow-up. Customers who had a good experience never get asked to say so publicly.
An agentic workflow does not replace the people doing the work. It handles the coordination that currently falls between the cracks because everyone is too busy doing the work to manage it.
That is the actual value. Not AI for its own sake. Not replacing staff. Just making sure the business captures what it already earned.
Get new notes when they ship.
~2 posts/month. No tracking, no spam.