Take an out-of-area call only when the margin on the job covers the extra drive both ways plus the jobs that drive pushes off the day. If it doesn't, say no quickly, offer a specific alternative, and never book it into a time slot no truck can reach.
Every company has an edge to its map. Inside it, jobs cluster, trucks hop from one stop to the next, and drive time stays small. Past it, one job can eat a morning. The trouble is that the call doesn't arrive labelled "this will cost you two jobs." It arrives as a customer who wants help and is ready to pay.
Why a far call costs more than its drive
The obvious cost is the drive out and back. The less obvious cost is what that drive displaces.
Say a tech normally runs five jobs a day inside your service area, with about 20 minutes between stops. A job 60 minutes from your usual cluster means 60 minutes out and 60 minutes back. A normal stop would have cost two 20-minute hops, so the far job adds about 80 minutes of drive. On a full day, 80 minutes is very close to one job you no longer have room for.
So the real comparison is not "the far job versus nothing." It is "the far job versus the in-area job it replaces."
The arithmetic
Use these letters:
M_far= gross margin on the far jobM_near= gross margin on a typical in-area jobX= extra drive in hours versus a normal hop, both waysR= loaded cost per hour of the tech and truckk= share of a normal job the extra drive displaces (extra drive ÷ a typical job slot including its hop)
The far job is worth it when:
M_far − (X × R) > k × M_near
The left side is what the far job earns after paying for the extra drive. The right side is what you give up on the day.
In this example the far job is a wash on a full day. On a light day, where k is close to zero because nothing else would fill the time, the same job adds about $147. That is the general rule: far calls are good on slow days and bad on full ones. A trip charge changes the left side directly; the trip charge definition covers how companies set one by distance.
The four honest answers
When a call comes in from outside your area, you have four real options.
1. Yes, on a day that has room
If the far job can go on a day where it won't displace in-area work (a slow Monday, a day with a cancellation, the tech who lives out that way), take it. Book it as the first or last stop so it adds one long leg instead of two.
2. Yes, with a travel charge
If the job only works with more margin, say so plainly: "We can come out on Thursday. Because you're outside our normal area, there's a $X travel charge on top of the visit." Some customers accept immediately. The ones who don't were not profitable anyway.
3. Not now, but here's when
If you only go out that way on certain days, offer that day. "We're in your area on Tuesdays. The next opening is Tuesday the 14th." That is a zone day, and it turns an expensive one-off into a stop on a planned route.
4. No, with a referral
If the job doesn't work on any day, say no quickly and point them somewhere useful. A fast, polite no with a name to call protects your reputation better than a booking you cancel later. If you work with partner companies who cover that area, this is where a contractor network earns its keep: the call goes to someone who can actually reach it, and you can keep a share.
What not to do: the fake slot
The worst outcome is an out-of-area customer who books a time online or over the phone, gets a confirmation, and then gets a call the day before saying the tech can't make it. It happens because most booking calendars only know whether a tech is free, not whether the tech can get there from the job before. The far job looks like any other open hour.
The fix is to treat the address as part of the booking decision. In CrewLink, an address outside every tech's area does not get a time slot at all. It becomes an out-of-area request that lands with the office, so a person makes one of the four calls above instead of the calendar making a promise. That is the honest version of the answer: a request someone will look at, not a slot no one can keep.
Setting your edge on purpose
Most service areas were drawn years ago and grew one favour at a time. Two checks keep the edge honest:
- Measure the edge in minutes, not miles. Twenty miles of highway and twenty miles of surface streets are different jobs. Draw the line where drive time from your typical cluster crosses a number you choose.
- Count the far calls you took last quarter. For each, look at what else was on that day. If most of them landed on full days, your edge is too wide or your travel charge too low.
What to take away
- A far call costs its drive plus the in-area job the drive displaces.
- Take it when
M_far − (X × R) > k × M_near. Far calls are good on slow days and bad on full ones. - The honest answers are: yes on a light day, yes with a travel charge, yes on your zone day, or no with a referral.
- Never let an out-of-area address book a time slot nobody can reach.
Common questions
Should I charge more for service calls outside my area?
Often, yes. A travel charge by distance or zone puts the cost of the extra drive on the job that causes it. Set it from your loaded cost per hour and the typical extra drive, not from what a competitor charges.
How far is too far for a service call?
There is no fixed distance. Measure it in drive minutes from where your trucks usually are, and compare the extra drive against the margin of the job it displaces. A call that is too far on a full Thursday may be fine on a slow Monday.
How do I politely turn down an out-of-area customer?
Be quick and specific. Tell them you don't cover their area, and give them a name or a company who does. A fast referral is remembered better than a booking you cancel the day before.
What is an out-of-area request?
It is a booking attempt from an address outside every technician's area that goes to the office for a decision instead of being offered a time slot. It keeps a calendar from promising a visit no one can make.