
On this page
It is 8am. Six jobs are booked, four technicians are on the road, and one van is carrying the wrong part. The office manager is on her third phone call of the morning and the first customer of the day has already been told “sometime between 9 and 1”.
Dispatch is not a scheduling problem. It is an information problem, solved badly, several times a day.
What dispatch actually needs to know
Four facts decide who goes where:
- Skill — a drain specialist is not a gas engineer.
- Parts — no point sending a van that does not carry the part.
- Location — the nearest free technician, not the one who likes that neighbourhood.
- Availability — including the job that will overrun, because one will.
Most small teams hold these four facts in one person’s head. That works until that person is on holiday, ill, or on another call.
The three-call problem
The typical dispatch loop:
- Call the customer to confirm the slot.
- Call two technicians to find out who is free.
- Call the customer back because the first technician cannot make it.
Each call is two minutes, and each one happens while someone else is waiting. Three dispatches a day is half an hour. Ten is most of a morning.
The fix is not a bigger office. It is putting those four facts somewhere the whole team can see.
What the customer should get
The customer does not care about the dispatch board. They care about three things:
- Who is coming — a name, not “an engineer”.
- When — a window, then a live update if it moves.
- That it is still happening — a message on the day, not silence.
A technician’s name and a two-hour window removes most of the “are they coming?” calls. Adding a “on my way” text when the van leaves the previous job removes most of the rest.
The DONE moment
The handover from field to office is where money leaks. The technician finishes, writes nothing down, and the invoice is built from memory three days later — with the extra part missing from it.
One word fixes this: the technician texts DONE, and the job record opens with the notes, the parts used and the invoice ready to send as a payment link.
The customer pays while the work is still fresh. The office stops reconstructing jobs from WhatsApp.
Recurring work is dispatch too
Maintenance contracts, filter changes, annual inspections — these are known months in advance and still get missed, because they are not in the same system as the emergencies.
If recurring visits are not generated automatically from the job history, they will always lose to today’s fire.
Checklist for a working dispatch setup
- Every technician has skills listed, not job titles
- Van stock recorded — at least the parts that cause second visits
- Job types mapped to required skills
- Availability blocks respected, including travel time
- Customer gets name, window and on-the-day confirmation
- DONE triggers an invoice, not a note
- Recurring maintenance created automatically
Get these right and dispatch becomes a glance at a screen instead of a morning of phone calls.
From call to invoice
BittaFlow keeps the job record whole: the call that came in, the quote the customer signs on their phone, the technician assigned, the updates along the way, and the invoice raised when the technician marks the job done. Payment links go out by text, and the same record holds the photos, notes and parts.
One record, four people looking at it, no morning phone tree.