For almost any business that travels to its customers, the first question is not about price. It is "do you cover my area?" Cleaners, locksmiths, dog groomers, electricians, removal firms, mobile mechanics: the visitor wants to know they are not wasting their time before reading anything else.
And it is astonishing how often the website does not say. There is a line in the footer about "serving the region", a map image with a blurry circle, or nothing at all. So the visitor fills in a form, waits a day, and gets an email saying sorry, that is outside our area. Both sides have lost a day.
Service area questions are among the easiest to answer instantly. They are factual, they have a small number of possible answers, and most of the effort is deciding your rules once.
Why "within 20 miles" is not an answer
A radius sounds precise. It is not, for the customer. Nobody knows whether their house is 18 or 23 miles from your unit, and road distance is not straight-line distance anyway. A river, a motorway or a toll bridge can make a place 10 miles away feel like 40.
A service area website needs coverage written in the terms customers actually know: towns, neighbourhoods and postcode districts. That also happens to be what an assistant needs. It cannot measure distances from a map image, but it can match "BS7" or "Horfield" against a written list reliably.
Deciding your rules before writing anything
The hard part is not the core area. It is the fringe. Sit down with whoever does the scheduling and agree how each situation below is handled. Here is an example set of rules for a hypothetical domestic cleaning company.
| Situation | Example rule | What the assistant says |
|---|---|---|
| Postcode in core list | Yes, standard pricing | "Yes, we cover that area." |
| Postcode in outer list | Yes, with a minimum booking | "Yes, we cover that area for regular cleans of three hours or more." |
| Postcode not listed but nearby | Check with the office | "That's on the edge of our area. Can I take your details so the team can confirm?" |
| Clearly out of area | No, offer referral | "We don't cover that area, but we can pass your details to a company we trust if you'd like." |
| Visitor only gives a town name | Ask for postcode district | "Some parts of that town are in our area and some aren't. Could you share the first part of your postcode?" |
| Commercial property, any area | Different team decides | "Commercial work is quoted separately. Can I take a few details?" |
Your rules will differ. What matters is that there is a rule for every row, so nobody improvises.
Writing coverage content your assistant can use
- List every postcode district or town you cover without conditions. Plain text, one per line or comma separated.
- List the outer areas where conditions apply, with the condition written next to each group.
- Write one sentence on what happens with borderline or unlisted places.
- Write one sentence on what happens with clearly out-of-area enquiries, including any referral offer.
- Add the list to a page on your website, ideally a dedicated coverage page, so visitors and search engines see it too.
- Teach the assistant using the same content, either by crawling that page or adding it as a document or Q&A pair.
- Test with real postcodes: five inside, five on the edge, five outside, and a few typed badly (no space, lowercase, just a town).
If the list is long, a CSV or text document uploaded to the assistant is often tidier than a sprawling Q&A. The docs explain the ways to add knowledge.
What the exchange should feel like
Quick, and never demanding a full address when a partial postcode will do.
Visitor: hi do you do end of tenancy cleans in kingswood
Assistant: Yes, Kingswood is in our regular area, and we do end of tenancy cleans there. Roughly how many bedrooms is the property, and do you have a date the keys need to be handed back?
And the out-of-area version:
Visitor: what about weston
Assistant: Weston is outside the area our team travels to, sorry. We do work with a cleaning company based nearer there. If you'd like, I can take your name and number and pass them on, or you can leave it there.
The second reply does three useful things at once: it answers fast, it does not pretend, and it offers something. That last part is optional and should only happen with the visitor's clear agreement.
Making out-of-area enquiries worth something
Most businesses treat an out-of-area enquiry as a waste. It does not have to be.
Referral partners. Plenty of trades have an informal arrangement with a similar firm in the next town. Passing them warm leads, with permission, tends to come back as referrals the other way.
Demand evidence. If you log where out-of-area enquiries come from, you learn where to expand. Ten enquiries a month from one town you do not serve is a business case. Zero is equally useful to know.
Future work. Some people move house, or have relatives in your area. A polite no leaves the door open.
To make any of this happen, those enquiries need to go somewhere. With lead capture on, the assistant records them. A webhook can send them to a spreadsheet, a CRM or a Slack channel tagged as out of area. The guide to sending leads to your CRM with webhooks shows the setup.
Multiple bases and shifting areas
If you run more than one depot or branch, each with its own patch, coverage gets more interesting. You may want one assistant that routes by postcode, or separate assistants per location page. The post on running an assistant across multiple locations covers the trade-offs.
Seasonal changes need the same attention. If you stop travelling to outer areas in winter, update the coverage list and re-sync the assistant, or it will keep saying yes into January.
This afternoon's job
Write your coverage list as towns and postcode districts, in two groups: core and conditional. Agree the edge-case rules with the person who schedules the work. Publish it on one clear page, teach it to your assistant, and test it with fifteen real postcodes including a few typed carelessly. Then decide what happens to out-of-area enquiries, and make sure they land somewhere instead of disappearing.