Dispatch: the route is the schedule, and the window is the promise

WhatsApp dispatch for field service teams works when the route is built first and the messages follow it. The route sets the travel, the arrival window is the promise to the customer, and a job that runs over must trigger a message to every customer later in the route. Most dispatch automation only adds messages around a route that someone still builds by hand at seven in the morning.

Key takeaways

• Travel time is the cost most field service quotes leave out, and the order of jobs decides it.
• Book by area rather than by customer preference, so the route builds itself.
• Quote an arrival window the route can carry, narrow it on the morning, and tell the customer as soon as the old time is wrong.
• Treat a job overrun as a trigger that messages every customer later in the route.
• Measure billable hours, travel per job, first-time fix rate and jobs lost to no access, not message counts.

What we'll cover

• Travel is the cost nobody prices
• The window is a promise about somebody's day
• What the technician needs before leaving
• When a job overruns, everyone behind moves
• Building it with CodeWords
• The emergency that lands mid-route
• Access failures, which are pure loss
• What the office needs back from the van
• Measuring a day honestly
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

Travel is the cost nobody prices

Travel is the cost nobody prices: every mile between two jobs is paid for out of margin, because the mile was never in the quote. A workshop sells hours on a ramp. A field service business sells hours minus travel, and the order of the jobs decides the travel.

Three things make travel worse than it needs to be.

Jobs booked by customer preference rather than geography. A morning slot in one direction and an afternoon slot forty minutes the other way accommodates two customers and loses an hour.

Urgent work inserted without resequencing. A job dropped into the middle of a route rather than into the right place in it.

No measure of what the travel actually was. Few small operators know their ratio of billable to travelling hours, so they cannot tell whether a change helped.

Booking by area rather than by preference is a scheduling policy, not software. Offer Tuesday morning to the north side and Tuesday afternoon to the south, and the day builds itself.

The window is a promise about somebody's day

An arrival window is a promise about the customer's working day. Field service is unusual because the customer has to be present, and they have usually taken unpaid time to be there.

That sets the standard. A four-hour window is tolerable if it is accurate. A two-hour window that slips by three is worse than the four-hour one, because the customer planned around it.

Three things make windows work.

Quote a window you can hit, including travel and the job before it running long.

Narrow it on the day. A text at eight saying "between ten and eleven" turns a morning off into a morning mostly worked.

Tell them the moment it moves. Message when you know the old time is wrong, not when you know the new time. "We are running late, I will confirm a time within the hour" is worth more than silence followed by precision.

What the technician needs before leaving

A technician needs six things before leaving for a job, and dispatch fails most often when one is missing.

• The address that works, including which entrance, which floor, and the gate code. Rural addresses and flats generate most of the "I cannot find it" calls.
• Who will be there, and their number, which is frequently not the person who booked.
• Parking. In a city, parking can decide whether a thirty-minute job takes an hour.
• What the fault is, in the customer's words, not translated into a job code that loses the detail.
• Make and model, and anything needed to work on it. This is usually what separates a first-time fix from a return visit.
• Whether it is a return visit, and what happened last time. A technician arriving without that context in front of an already annoyed customer starts at a disadvantage.

When a job overruns, everyone behind moves

When a job overruns, every appointment after it moves, so the overrun must be a trigger, not an exception. A job running ninety minutes long affects the whole rest of the route. Handled by hand, the technician either rings four customers from a driveway or rings none, and the second is what usually happens.

When a job is marked as running over, the customers later in the route are told automatically, with a revised window. The technician does not have to decide who to call or find the time to do it.

Two details matter. Give the customers furthest down the route the most notice, since they have the most time to use it. And where a job clearly cannot be reached today, say so and rebook rather than moving somebody to six in the evening.

Building it with CodeWords

You build dispatch messaging in CodeWords by describing the route rules to Cody, the automation builder. CodeWords connects to 3,000+ integrations (CodeWords pricing page, 2026), and you make each connection once and reuse it.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody: what the technician receives before each job, what the customer receives and when, and what happens to the rest of the route when one job runs over.
3. Authorize the connections to wherever jobs are recorded, your calendar, and your WhatsApp Business Platform account.
4. Describe the exceptions: an emergency inserted mid-route, a no-access, a job that needs a second visit, a customer who asked to be phoned.
5. Run it on one technician's route for a fortnight, and record travel time honestly while you do, because travel time is the number the whole exercise is about.

You describe the outcome; Cody builds it, connects it, and deploys it. The Free plan costs $0 and covers light use, Pro is $39 per month ($33 billed yearly) and Business is $100 per month (CodeWords pricing page, 2026). Details are on the pricing page.

The emergency that lands mid-route

An emergency mid-route needs a rule decided in advance, because urgent work is the main reason a planned route stops matching the day that happens. Decide what counts as an emergency for your business, what it costs, and how many planned jobs you will displace for one. Without a rule, the loudest customer wins and four quiet ones are let down for a job that was not urgent.

Where you do displace somebody, send the message immediately and offer something: the next slot, a specific time, a choice. A customer bumped with an apology and no alternative is likely to book elsewhere.

Access failures, which are pure loss

An access failure is pure loss: the travel is spent, the slot is gone, and there is nothing to invoice. Nobody in, wrong key, no access to the loft, a dog in the room.

Prevent most of it at booking and confirmation. Ask what access is needed, who will be there, and whether anything has to be moved or turned off first. Repeat the request the day before, specifically, rather than as a generic reminder.

Then state a policy before the visit rather than after. Whether a failed visit is chargeable is your commercial decision, and a customer told in advance is more likely to accept it than one told on the doorstep.

What the office needs back from the van

The office needs five things back from the van, because dispatch is two-directional and the return leg gets neglected.

• Job completed, with what was done. Enough for an invoice without a phone call.
• Parts used, so the van stock is right tomorrow.
• Whether it is finished. This is the most valuable field in field service, and the one most often left ambiguous.
• What is needed for the return visit, if there is one, captured while the technician is still on site.
• Photographs where relevant, particularly for anything that may be disputed.

Captured at the door, this takes a minute. Reconstructed in the evening, it takes longer and is less accurate.

Measuring a day honestly

Measure four numbers, and none of them are message statistics.

Measure	Why it matters
Billable hours as a share of working hours	The headline figure for the whole business
Travel time per job, trending	Shows whether sequencing is improving
First-time fix rate	Where the money is in most repair trades
Jobs lost to no access	Pure waste, and usually fixable

Track those for a month and the priorities become clear. Message counts describe the automation, not the business.

Making it survive

A durable dispatch flow checks the job state before every customer message, because routes change constantly.

Check the job state before any customer message, since routes move constantly.

Make the overrun a trigger rather than something a technician remembers to handle.

Ask about access at booking and again the day before, in specifics.

Give the no-access policy to the customer in advance, in writing.

Record travel and first-time fix permanently, not just during a trial.

Limits worth knowing about

Automation cannot shorten a journey. Better sequencing can; messaging cannot.

Some days go wrong, and a good system makes that visible sooner rather than preventing it.

Traffic cannot be predicted to the minute, which is why arrival windows exist.

A technician cannot answer a phone in a loft, so anything requiring their input has to be asynchronous.

Tight windows raise the cost of every slip. Promise what the route can carry.

What to build first

Build the overrun message first. When a job is marked as running long, everybody later in the route hears about it with a revised window, without the technician deciding who to ring. The overrun is the most common failure in a field service day and generates many complaints.

Two habits make the difference. Book by area rather than by preference, since the route is where the unbilled hours go and no message recovers them. And narrow the window on the morning, because a customer who gets their day back after an eight o'clock text remembers the courtesy.

Frequently asked questions

Why does travel time matter so much in field service?

Travel time matters because it is paid out of margin and rarely quoted. Two schedules containing identical work can differ in billable hours purely on the order the jobs were put in.

How should jobs be sequenced?

Sequence jobs by geography rather than customer preference. Offering one area a morning and another an afternoon builds the route automatically and removes most of the crossing.

How wide should an arrival window be?

An arrival window should be wide enough to be accurate, then narrowed on the day. A two-hour window that slips by three is worse than an honest four-hour one, because the customer planned around it.

When should a customer be told about a delay?

Tell the customer when you know the old time is wrong, not when you know the new one. "Running late, I will confirm within the hour" beats silence followed by a precise time.

What should a technician get before leaving?

A technician should get the address with entrance and access details, who will be there and their number, parking, the fault in the customer's words, the make and model, and whether it is a return visit.

How should an overrun be handled?

Handle an overrun as a trigger. Everyone later in the route is told automatically with a revised window, with the most notice going to the customers furthest down the day.

How do I handle emergencies without wrecking the route?

Decide in advance what counts as an emergency, what it costs, and how many planned jobs you will displace. Anyone displaced gets an immediate message offering a specific alternative.

How do I reduce failed visits?

Ask what access is needed at booking and again the day before, in specifics. State the no-access policy in writing beforehand rather than on the doorstep.

What should come back from the van?

Five things should come back: what was done, parts used, whether the job is finished, what a return visit needs, and photographs where relevant. Captured at the door, this takes a minute.

What should a field service business measure?

Measure billable hours as a share of working hours, travel per job, first-time fix rate, and jobs lost to no access. Message statistics describe the automation rather than the business.

Related reading

• What to know before the van moves
• Missed calls, and which ones are worth having
• The jobs that are not finished