Playbook · lead response automation ontario
The competitor who won that job was not better. They answered first.
How to answer every enquiry in under a minute, what the build costs in Ontario, and the PIPEDA line that decides whether you may enrich a lead at all.
Lasse Pettersen
An enquiry arrives on your website at 4:40pm on a Saturday. You see it Monday morning and reply at 9:15am. Nothing about that reply is bad. It is just second. Somebody else answered on Saturday evening, and the job was decided before you read the form.
This is the least interesting automation on this site and one of the two or three most profitable. It contains almost no artificial intelligence. It is a form, a database record and a schedule, connected so that the gap between an enquiry arriving and somebody acknowledging it is under a minute instead of over a weekend.
What the build actually does
Five steps, in order, and the order matters because the expensive ones come last.
One: catch every enquiry in one place
Most businesses have more than one front door and have never counted them. The website form, the second website form nobody remembers building, the info inbox, the quote request on a listing, the direct messages, the phone. A build that only watches the website form leaves the others exactly as broken as they were.
The first hour of this work is an inventory of the doors. It is boring and it changes the scope of everything after it.
Two: create the record before anything else
The enquiry becomes a row in the CRM immediately, with a source, a timestamp and the raw message text. This happens before enrichment, before scoring and before any message goes out, because every one of those steps can fail and none of them may be allowed to lose the lead.
The record is the product here. A business that answers fast but never writes the enquiry down still cannot tell you in March what January cost per lead, and it will keep buying the channel that does not work.
Three: acknowledge, in under a minute
One message. It says the enquiry arrived, names the business, says who will reply and by when, and gives one way to reach a person sooner if it is urgent.
It does not quote. It does not promise a date. It does not pretend to be a person. An acknowledgement that overpromises is worse than a slow reply, because the slow reply only cost you a chance and the overpromise costs you a complaint.
Four: score it, quietly
A model reads the enquiry against your description of the work you want and returns a tier and a one line reason, written to the record. It does not decide anything on its own. It changes the order of the callback list.
Calibrate this after the first 20 to 30 leads by comparing the tier the model gave to what actually happened. Before that calibration the score is a guess with a number attached, and it should be treated as one.
Five: follow up until somebody replies
Five touches over about two weeks, and every one of them checks the record before sending. A reply from the lead stops the sequence. A logged call from a human stops the sequence. A booked appointment stops the sequence and hands over to the confirmation and reminder run described in appointment reminder automation.
The PIPEDA line that decides the enrichment step
The workflow templates being sold for this job all put an enrichment step after the form, appending company size, revenue, job title and a social profile to whatever the person typed. Bought as a template, that step is a privacy decision nobody made.
The federal Personal Information Protection and Electronic Documents Act governs the collection, use and disclosure of personal information in commercial activity. It carves out business contact information collected solely to communicate with an individual about their employment or business. So:
| What arrives | What appending data to it is |
|---|---|
| A work email at a company domain, plus a job title | Business contact information, and the carve out is doing real work for you |
| A personal email address from a homeowner | Personal information, collected without their knowledge, from a third party |
| A phone number and a description of a household problem | Personal information, and possibly sensitive depending on the problem |
A residential trades business, a clinic and a home services company are mostly in the second and third rows. An enrichment step there is collecting personal information about an identifiable individual from a source the individual never dealt with, and the fact that a template put it in the workflow is not a defence.
My default in a build is no enrichment on a personal email address, enrichment allowed on a business domain, and the rule written into the runbook rather than left to whoever configures the tool next. The wider version of this argument is in PIPEDA and your AI tools. None of it is legal advice.
The practical loss is small. Enrichment on a residential lead rarely changes what you do next, because the thing that decides whether you want the job is what they typed in the message box.
What it costs
$2,500 to $5,000, inside the $2,500 to $12,000 range published on the workflow automation page. Running costs are usually under $100 a month, because the volume is low and most of the work is moving records rather than calling a model.
| Driver | Cheap end | Expensive end |
|---|---|---|
| Front doors | One form, one inbox | Four or more sources including a listing site and direct messages |
| CRM | A modern system with a documented API | A spreadsheet, or a desktop system with no interface |
| Routing | Everything to one person | By service, by region, by value, with an out of hours path |
| Follow-up | One sequence, five touches | A sequence per service line, in two languages |
| Attribution | Source field only | Full campaign and cost per lead reporting back to the ad accounts |
The cheapest real version of this is a build at the bottom of that range against a business already running one form into one usable CRM. The expensive version is almost always the CRM row, and the honest advice in that case is to fix the CRM workflow first, not automate instead.
What this does not fix
It does not fix a phone that nobody answers. A form automation cannot help a caller who reached voicemail at 2pm and phoned the next company. That is intake work, it is priced as AI agents, and it ranks ahead of this in any business where most enquiries arrive by phone.
It does not fix an empty top of funnel. If four enquiries arrive a month, answering them in 40 seconds instead of 40 hours changes very little. The problem is upstream, and whether a marketing agency is worth it is the more useful page.
It does not make you visible to an AI assistant. Across 136 recommendation queries in 34 Ontario cities, the businesses an assistant named were decided by the citation layer far more often than by the quality of their own site, and the pattern is set out in who an AI assistant recommends across 34 Ontario cities. Lead response is what you do with the enquiry once it exists.
Why this is worth building in a small Ontario business
Statistics Canada put Canadian business AI use at 19.2% in the second quarter of 2026, and marketing automation at 19.8% of those adopters, which is a minority of a minority and down from 23.1% a year earlier. Rural adoption sits at 9.9% against 21.0% urban.
Read against a business in Barrie, Guelph or Peterborough, that is not a warning. It is the reason the automation still works. Speed of response is a competitive advantage precisely because most of the firms quoting against you are still reading the form on Monday morning.
The arithmetic to run before you spend is your own. Take last month’s enquiries, count how many you replied to within an hour, and multiply the rest by your average job value and your usual close rate. That number is what the build has to beat. If you cannot get the enquiry count out of your systems at all, that is the first finding, and the $999 assessment is the cheaper way to get to it than a build quoted on guesswork.