For a service business, the most expensive thing you can do is drive somewhere you were never going to take the job.
It is not just the fuel. It is the hour you did not spend on paid work, the slot you did not give to a customer who was in your area, and the quote you wrote that was never winnable.
Why it keeps happening
Nobody asks early enough. The conversation goes: what do you need, when do you need it, roughly what does that involve, and only then, twenty minutes in, does location come up. By that point there is a sunk-cost pull to make it work.
The fix
Ask location second. After establishing what the job is, before anything about price or availability.
That ordering matters. Asking first feels like a gatekeeper. Asking after the job is understood feels like a professional working out whether they can help, which is exactly what it is.
Decide your rule in advance
Vagueness here costs money. Write down:
- The core radius you will always travel.
- The margin you will consider, and what makes it worthwhile: job size, or a travel charge.
- The hard no.
Publish it. "We cover Greater Manchester and 15 miles beyond, with a travel charge outside the M60" is a sentence that saves you hours a month, and it does it whether or not you buy any software.
What to say to someone outside it
Be direct and be useful. "We do not cover Sheffield, but the checks we would do are X, Y and Z, and a local firm should be able to help." That is thirty seconds and it costs nothing.
Being strung along and then declined is what generates the bad review. Being told straight away, with something useful attached, does not.
Automating it
Once your service area is published in plain language, anything that reads your website can check an enquiry against it, including a chat assistant on your website, which will ask for a postcode early and give a consistent answer at 11pm.
The gain is not that software does it better than you would. It is that it does it every single time, including the times you would have been too busy to ask.
What the website assistant needs, and what it collects
SpideyChat works in the chat window on your website. It does not answer your phone, so a caller still needs a person to ask about location. On the website side, the assistant can only screen against what you publish. Write the area as text a visitor would understand: the towns or postcode districts you cover, the edge zone with its travel charge, and the places you never go. A map image alone is not enough, because the assistant reads words, not pictures.
When a visitor is inside the area, the assistant collects what a quote or callout needs: name, phone number, email, postcode and a short description of the job. That becomes a lead or a callback request for your team to arrange, not a fixed appointment. When they are in the edge zone, it states the travel charge you published. When they are outside it, it says so politely and points them elsewhere. Borderline cases, like a large job just past your boundary, should go to a person, and the chat can be handed over if someone is online. See the home services page for a worked setup.
Test it
Build an AI employee from your site and tell it you are somewhere you do not cover. If your service area is published clearly, it will tell you so.
Related: AI employee for service businesses.