Check the job address before the phone agent books it
7 min read
By Lumina Software
- Voice reception
- Service business
- Scheduling
- Dispatch
- Operations
A caller rings a plumbing company at 8 in the evening. The phone agent is friendly, collects the problem, finds an open slot for tomorrow at 10, reads back the address, and books it. The next morning the dispatcher looks at the board and sees the address is 45 minutes past the edge of where the company works. Now someone has to call the customer, explain that nobody is coming, and apologize for a promise the business never meant to make.
This happens more than most owners expect. A person at the front desk knows the service area without thinking about it. They hear a town name and know right away whether it is a yes, a maybe, or a polite no. A phone agent knows only what it was given, and on most setups it was never given the service area at all.
This post covers how to write your service area down in a form a phone agent can check, what to do with the calls that fall outside it, and how to keep that list from going stale.
Why the service area gets left out
When a business sets up a phone agent, the setup usually starts with the obvious things: hours, services offered, how to book, when to transfer. The service area feels obvious too, so it either gets skipped or written as one loose sentence like "we serve the greater metro area."
That sentence works for a person. It does not work for software. "Greater metro area" means different things to the owner, the dispatcher, and the tech who has to drive there. An agent reading that line will guess, and a guess that books a job an hour away costs a truck roll, a refund conversation, or a bad review.
The service area is also rarely one simple boundary. A lot of service businesses have layers:
- Towns or zip codes they serve every day.
- An outer ring they serve for bigger jobs or for an extra trip charge.
- Places they serve only for certain work, like installs but not repairs.
- Places they used to serve and quietly stopped.
All of that lives in people's heads. None of it is in the phone agent.
Write the boundary as a list, not a description
The most reliable format is a plain list the agent can look up, not a paragraph it has to interpret. Zip codes work well because callers know theirs and it is hard to misspell. Town names work too, as long as you include the ones that share names with places in other states or counties.
For each entry, write down what the business does there:
- Served. Book normally.
- Served with conditions. Book, but tell the caller about the trip charge or minimum, or only book certain job types.
- Not served. Do not book.
Anything not on the list should be treated as unknown, not as served. That one rule prevents most of the bad bookings. If the agent cannot find the caller's zip code, it should say so and route the call to a person or take a message, rather than assume the answer is yes.
If your scheduling or field service software already stores service zones, use that as the source and have the agent check it at booking time. One list in one place is better than a copy in the phone agent and another copy in the dispatch tool that drift apart.
Ask for the location early in the call
Order matters. If the agent collects the caller's name, problem description, and preferred time before it asks where they are, an out of area caller has spent three minutes on a call that was never going to end in a booking. They will be more annoyed hearing no at minute three than at minute one.
Have the agent ask for the zip code or town near the start, right after it understands the general kind of job. Then it can check the list before it gets into details. For callers in the served list, the call continues as normal. For the others, the agent can be honest quickly.
Asking early also catches a common mistake: the caller is calling about a property that is not where they live. A landlord, an adult child calling for a parent, or a property manager may be in your area while the job is not, or the other way around. The agent should ask for the address of the job, not the caller's home.
Handle out of area calls on purpose
A caller outside your area is still a person who needs help, and how you treat them says something about the business. Decide what the agent should do and write it down so it is the same every time.
A few reasonable options:
Say no clearly and kindly. "We don't cover that area, so I don't want to book something we can't get to." Callers generally prefer a fast, honest no to a booking that falls apart later.
Point them somewhere useful. If you have a referral partner or a trade association directory you trust, the agent can mention it. Only do this if the business actually stands behind the referral.
Take a message for the edge cases. For the outer ring, or for large jobs the owner might want to take anyway, the agent can collect details and promise a call back from a person who decides. Give that callback an owner and a time, the same as any other promise the agent makes.
Log every out of area call. Even when the answer is no, write down the zip code and the type of job. Over a few months that log shows where demand is coming from. If a nearby town keeps showing up, that is real information for a decision about expanding the route.
Keep the list current
Service areas change. A tech who lived on the north side leaves, and suddenly the north side is a long drive. The business adds a second truck and can reach farther. Fuel costs go up and the outer ring gets a trip charge. A town that kept generating no shows gets dropped.
Each of these is a decision someone makes in a meeting or a text thread. The phone agent never hears about it unless someone updates the list. Make updating the list part of the decision: whoever changes the area is responsible for changing the list the same day.
Then check it on a schedule. Once a quarter, pull the last few months of bookings and look for jobs that dispatch had to cancel or reassign because of location. Each one points to a gap between what the list says and what the business actually does. Also call the main line yourself with a zip code from each category and confirm the agent handles it the way you expect.
Watch the edges, not the middle
Most calls come from the middle of your area, and those almost never go wrong. The trouble sits at the edges: zip codes that are half in and half out, towns with the same name as one two counties over, new developments with zip codes the list has never seen.
For anything near the boundary, it is fine to have the agent book with a flag for dispatch to confirm, or to hand the call to a person. A small amount of human review at the edges is cheaper than a truck driving somewhere it should not go.
The short version
A phone agent does not know where your business works unless you tell it in a form it can check. Write your service area as a list of zip codes or towns with a clear status for each: served, served with conditions, or not served, and treat anything missing as unknown. Have the agent ask for the job location early, and ask for the job address rather than the caller's. Decide in advance what happens to out of area callers, log those calls, and update the list the same day the area changes. Check the edges every quarter, because that is where the wrong bookings come from.
Written by Lumina Software. Have a question? Book a call