Key takeaways<\/h2>\n\n\n\n\n- Two filters answer most enquiries:<\/strong> do you cover the area, and do you do that job.<\/li>\n\n\n
- Both have fixed answers, which makes this the easiest flow in the cluster to get value from.<\/li>\n\n\n
- Emergencies must bypass the flow<\/strong> and route to a phone immediately.<\/li>\n\n\n
- No price leaves the automation – a quote is a commitment, and trades get held to it.<\/li>\n\n\n
- An honest no about area or job type saves a call and often earns a referral.<\/li>\n\n\n
- The flow should end in a callback time, not a promise to get back to them.<\/li>\n\n<\/ul>\n\n<\/div>\n\n\n\n
The Emergency Route<\/h2>\n\n\n\n
First, because it overrides everything else in the article.<\/p>\n\n\n\n
Somebody With a Leak Should Not Answer Questions<\/h3>\n\n\n\n
Water coming through a ceiling, no heating in February, no power, a lockout, a smell of gas. These are not enquiries to be qualified; they are people who need a phone number and a human voice.<\/p>\n\n\n\n
Match the words broadly – leak, flooding, no heat, no power, gas, smoke, locked out, emergency, urgent – and route before any other branch runs. Give the phone number directly in the message.<\/p>\n\n\n\n
Say Clearly If You Do Not Do Emergencies<\/h3>\n\n\n\n
Plenty of trades do not, and that is fine. What is not fine is silence at eleven at night while somebody assumes help is coming.<\/p>\n\n\n\n
If you do not, say so and point to who does. That one sentence is genuinely the difference between a bad night and a bad review.<\/p>\n\n\n\n![\"Local](\"https:\/\/dmpro.brandid.app\/blog\/wp-content\/uploads\/2026\/10\/dm-automation-for-local-business-twofilters.jpg\")
Answering them automatically is most of the value in this trade.<\/figcaption><\/figure>\n\n\n\nThe Two Filters<\/h2>\n\n\n\n
Between them they resolve most of what arrives.<\/p>\n\n\n\n
Do You Cover the Area?<\/h3>\n\n\n\n
Ask for a postcode or offer your areas as buttons. It is the first thing the customer wants to know and the first thing you need, and getting it answered before anybody speaks saves a call for both sides.<\/p>\n\n\n\n
Build in the edge case: the area just outside your normal radius where you will travel but the price changes. \u201cWe do cover that but there is a travel charge – still interested?\u201d is better than a flat no and better than an awkward conversation later.<\/p>\n\n\n\n
Do You Do That Job?<\/h3>\n\n\n\n
The one that wastes the most time when it goes unanswered, because adjacent trades sound close enough that customers reasonably guess. Offer your actual services as buttons and include \u201csomething else\u201d.<\/p>\n\n\n\n
A clear no here is valuable. \u201cWe do not do that, but X does and they are good\u201d takes ten seconds and is remembered.<\/p>\n\n\n\n
Then Take the Details<\/h3>\n\n\n\n
For the enquiries that pass both: what the job is, where, and when suits for a callback. The flow should end in a time – \u201cI will call you between 6 and 7 this evening\u201d – rather than \u201cwe will be in touch\u201d.<\/p>\n\n\n\n
A named time is what stops them ringing the next business on the list.<\/p>\n\n\n\n![\"Trigger](\"https:\/\/dmpro.brandid.app\/blog\/wp-content\/uploads\/2026\/10\/dm-automation-for-local-business-variables.jpg\")
The flow is the same everywhere. Only these change.<\/figcaption><\/figure>\n\n\n\nNever Quote<\/h2>\n\n\n\n
Short section, and it is the rule most often broken in this trade.<\/p>\n\n\n\n
A Number Becomes a Promise<\/h3>\n\n\n\n
\u201cRoughly two hundred\u201d sent by an automation will be quoted back when the actual job turns out to need a day and new parts. Trades get held to numbers more literally than most businesses, and the dispute costs more than the job.<\/p>\n\n\n\n
A band is acceptable – \u201cmost jobs like this are between X and Y, I will confirm when I see it\u201d – because it is explicitly not a quote. A single figure never is.<\/p>\n\n\n\n
Call-Out Fees Are Different<\/h3>\n\n\n\n
A fixed call-out charge is a published fact and should be in the flow. It manages expectations, filters out people who did not realise there was one, and prevents an argument on the doorstep.<\/p>\n\n\n\n
What to Automate<\/h2>\n\n\n\n
Short list for a trade that does not need a long one.<\/p>\n\n\n\n
The Emergency Route<\/h2>\n\n\n\n
First, because it overrides everything else in the article.<\/p>\n\n\n\n
Somebody With a Leak Should Not Answer Questions<\/h3>\n\n\n\n
Water coming through a ceiling, no heating in February, no power, a lockout, a smell of gas. These are not enquiries to be qualified; they are people who need a phone number and a human voice.<\/p>\n\n\n\n
Match the words broadly – leak, flooding, no heat, no power, gas, smoke, locked out, emergency, urgent – and route before any other branch runs. Give the phone number directly in the message.<\/p>\n\n\n\n
Say Clearly If You Do Not Do Emergencies<\/h3>\n\n\n\n
Plenty of trades do not, and that is fine. What is not fine is silence at eleven at night while somebody assumes help is coming.<\/p>\n\n\n\n
If you do not, say so and point to who does. That one sentence is genuinely the difference between a bad night and a bad review.<\/p>\n\n\n\n Between them they resolve most of what arrives.<\/p>\n\n\n\n Ask for a postcode or offer your areas as buttons. It is the first thing the customer wants to know and the first thing you need, and getting it answered before anybody speaks saves a call for both sides.<\/p>\n\n\n\n Build in the edge case: the area just outside your normal radius where you will travel but the price changes. \u201cWe do cover that but there is a travel charge – still interested?\u201d is better than a flat no and better than an awkward conversation later.<\/p>\n\n\n\n The one that wastes the most time when it goes unanswered, because adjacent trades sound close enough that customers reasonably guess. Offer your actual services as buttons and include \u201csomething else\u201d.<\/p>\n\n\n\n A clear no here is valuable. \u201cWe do not do that, but X does and they are good\u201d takes ten seconds and is remembered.<\/p>\n\n\n\n For the enquiries that pass both: what the job is, where, and when suits for a callback. The flow should end in a time – \u201cI will call you between 6 and 7 this evening\u201d – rather than \u201cwe will be in touch\u201d.<\/p>\n\n\n\n A named time is what stops them ringing the next business on the list.<\/p>\n\n\n\n Short section, and it is the rule most often broken in this trade.<\/p>\n\n\n\n \u201cRoughly two hundred\u201d sent by an automation will be quoted back when the actual job turns out to need a day and new parts. Trades get held to numbers more literally than most businesses, and the dispute costs more than the job.<\/p>\n\n\n\n A band is acceptable – \u201cmost jobs like this are between X and Y, I will confirm when I see it\u201d – because it is explicitly not a quote. A single figure never is.<\/p>\n\n\n\n A fixed call-out charge is a published fact and should be in the flow. It manages expectations, filters out people who did not realise there was one, and prevents an argument on the doorstep.<\/p>\n\n\n\n Short list for a trade that does not need a long one.<\/p>\n\n\n\nThe Two Filters<\/h2>\n\n\n\n
Do You Cover the Area?<\/h3>\n\n\n\n
Do You Do That Job?<\/h3>\n\n\n\n
Then Take the Details<\/h3>\n\n\n\n
Never Quote<\/h2>\n\n\n\n
A Number Becomes a Promise<\/h3>\n\n\n\n
Call-Out Fees Are Different<\/h3>\n\n\n\n
What to Automate<\/h2>\n\n\n\n