At one technician, dispatch is a conversation. "Morning, you are going to Mrs van der Berg in Sandton at 9, then the Greenside plumbing job at 1." Done. No tools required.
At three technicians, it is still manageable. A WhatsApp group, a shared spreadsheet, maybe a whiteboard in the office. Busy, but workable.
At five technicians, it is no longer a conversation. It is a coordination challenge. Jobs get double-booked. Technicians show up at the wrong address. The urgent callout comes in at 11am and you have no idea who is closest, who has already started a job, and who might be available. You make phone calls. You interrupt three people to find the answer. You make a decision based on incomplete information and hope for the best.
This guide explains how professional dispatch works, what tools support it, and how to build a structured dispatch system that scales.
What dispatch actually involves
Dispatch is not just assigning a job to a technician. It involves:
- Availability management: Knowing which technicians are free, which are on a job, and when each will be available next
- Geographic matching: Assigning the technician who is geographically closest to a job — or who will be closest when the job needs to start
- Skills matching: For specialist work, assigning a technician with the right skills (a certified gas technician for a gas geyser, an electrician for a DB board fault, an HVAC tech for a commercial chiller)
- Priority management: When an urgent job comes in, adjusting the schedule without disrupting all other jobs
- Real-time tracking: Knowing where each technician actually is, not just where they are supposed to be
A WhatsApp group addresses one of these — assignment — and none of the rest. That is why it starts showing cracks at scale.
Where WhatsApp dispatch breaks
No confirmation visibility
You send a job assignment to a technician via WhatsApp. The message shows two grey ticks, then two blue ticks. The technician has read it. But have they actually accepted it? Have they added it to their day? Are they already committed to something else that they have not told you about?
In a group chat, job assignments disappear into a stream of other messages. A technician who reads a message at 8am and gets distracted by a customer question may genuinely have forgotten about it by 9am. You are following up. They are apologising. The customer is waiting.
Formal job assignment in a dispatch system moves the job to dispatched status with the technician's name attached. There is no ambiguity. The technician sees the job on their job list. The dispatcher can see whether the technician has acknowledged it. The job does not fall through a message thread.
No visibility into where anyone is
If three of your five technicians are on jobs right now and a new urgent job comes in, how do you decide who to assign it to? With WhatsApp dispatch, you make three phone calls: "Where are you? How much longer will you be? Can you go to Kyalami straight after?"
With a real-time dispatch system, you look at a screen. You see where each technician is, what their current job status is, and when they are expected to complete. You see which technician is closest to the new job. You drag the job onto their schedule. They get a push notification. The new customer gets an ETA. No phone calls.
Double-booking is too easy
In a WhatsApp-and-spreadsheet dispatch system, double-booking happens because the spreadsheet is not always open, not always updated, and not always accurate. Two people updating the spreadsheet simultaneously can create conflicts. A job that was added verbally and not yet entered into the spreadsheet is invisible to everyone else.
A proper dispatch system shows all assigned jobs in a shared view, updated in real time. If a time slot is full, it is full — visibly and immediately.
Job priority is invisible
In a group chat, every message looks the same. An urgent commercial callout from a client with a service level agreement looks identical to a routine residential maintenance visit. There is no mechanism in WhatsApp to sort, filter, or prioritise jobs by urgency.
A structured dispatch system assigns priority levels — low, normal, urgent, emergency — and the dispatch board reflects them. Urgent jobs are visually distinct. They can be filtered. They can be escalated without digging through a message thread.
The two dispatch views: list and calendar
Field service dispatch tools typically offer two views. Understanding when to use each one helps you choose the right tool for your business size.
List view
A list view shows all open jobs in a flat list with assigned technicians, scheduled times, job addresses, and current status. The dispatcher assigns jobs by selecting a job and selecting a technician from a dropdown. There is no visual timeline — just a list.
List view is the right view for businesses with a smaller team (two to five technicians) or a smaller daily job volume (under 15 jobs per day). It is fast to scan, easy to understand, and does not require much screen space. It is particularly useful on mobile for dispatchers who are not always at a desk.
On WorkOrderPro, the Starter plan (R999/mo base + R349/technician, up to five technicians) includes list-view dispatch. This is the right level for owner-operators and small teams.
Calendar drag-and-drop view
A calendar view shows the day or week broken into time slots, with each technician represented as a column (or row). Jobs appear as blocks on the calendar at their scheduled times. The dispatcher assigns jobs by dragging a job block onto a technician's time slot.
The visual benefit of the calendar view is immediate: you can see at a glance which technicians have full days, which have availability, and where jobs cluster or conflict. For a team of six or more technicians, this visual density makes dispatch significantly faster than list view.
The calendar view in WorkOrderPro also shows real-time GPS location for each technician and live job status updates via WebSockets. When a technician's job status changes — from dispatched to on_site, for example — the calendar updates without the page being refreshed. The dispatcher always sees the current state of the day, not a snapshot from five minutes ago.
The full calendar drag-and-drop dispatch board is a Professional plan feature (R1 999/mo base + R499/technician, up to 25 technicians).
The dispatch workflow in practice
Here is what structured dispatch looks like for a medium-sized plumbing company with seven technicians:
7:30am: The dispatcher opens the dispatch board. They see today's pre-scheduled jobs — six maintenance visits and three quote appointments already assigned to technicians from the day before. They check the GPS status: all seven technicians are showing their last known location, most still at home. Two are already en route to their first jobs.
8:15am: A new job comes in. A commercial property manager calls about a burst pipe in a Rosebank office building. The dispatcher creates the job, sets priority to urgent, and looks at the board. Two technicians are between jobs right now. One is in Midrand; the other is in Bryanston. The Bryanston technician is 15 minutes from Rosebank. The dispatcher drags the job onto the Bryanston technician's 8:30am slot. The technician gets a push notification immediately. They accept and confirm in the app.
8:17am: The property manager calls back asking for an ETA. The dispatcher tells them the technician will be there at approximately 8:45am. This is based on real data — the technician's current location from the GPS feed and the 15-minute drive time.
9:00am: The technician arrives in Rosebank. Their job status moves to on_site automatically (or they tap to confirm arrival). The dispatcher sees this on the board without being told. They do not need to call the technician or the customer.
11:30am: The job is more complex than expected. The technician moves the job to on_hold with a hold reason: "Waiting for isolation of mains — building manager on the way." The SLA clock pauses. The dispatcher sees the hold status and reason. They adjust the afternoon schedule to move the next job to another technician, because this job is now likely to run past lunch.
1:45pm: The hold is resolved. The technician resumes. The job moves to in_progress. The SLA clock resumes.
3:20pm: The job is complete. The technician marks it completed. An invoice is generated automatically. It is sent to the property manager's email. The dispatcher sees the completed status on the board and assigns the technician to the late afternoon job that had been waiting.
This is structured dispatch in operation. No phone calls about status. No guessing about location. No manual invoice creation. Clear priority handling. The dispatcher is managing the flow, not chasing information.
Building your dispatch system
Whether you are moving from WhatsApp or upgrading from a basic scheduling tool, the transition to structured dispatch follows a similar path:
Step 1: Centralise all pending jobs. Before you can dispatch efficiently, you need all jobs in one place. If jobs are being taken verbally, via WhatsApp, via email, and via the office phone, they all need to land in the same system before dispatch can manage them. Establish a single intake point.
Step 2: Set up your technician list with skill tags. Document which technicians handle which job types. A plumbing company may have gas-certified technicians, geysers-only technicians, and full-scope plumbers. Knowing this upfront means you assign the right person the first time.
Step 3: Train the team on app use before going live. Technicians need to know how to accept a job, update their status, and mark a job complete in the app. This is typically a 20- to 30-minute walkthrough, not a training course. But it has to happen before the first live dispatch, not after.
Step 4: Set a go-live date and stick to it. A dispatch system only works if it is used for everything. A mixed system — some jobs in the app, some in WhatsApp — means incomplete visibility. Pick a start date and move everything.
When to upgrade from list view to calendar view
The calendar drag-and-drop dispatch board becomes significantly more useful when:
- You have six or more technicians on any given day
- Your daily job volume is above 15-20 jobs
- You regularly handle urgent or same-day jobs that require reshuffling existing schedules
- You have a dedicated dispatcher whose primary role is managing the board — not a business owner doing dispatch alongside everything else
Below these thresholds, list view handles the work without the overhead of managing a visual calendar.
See the dispatch board in action. WorkOrderPro includes list-view dispatch on Starter and full calendar drag-and-drop dispatch on Professional. Start your free 14-day trial. Start your free trial
Frequently asked questions
Q: Can I assign a job to more than one technician? A: Yes. WorkOrderPro supports multi-technician job assignment. Each job has a lead technician (the primary assignee for dispatch purposes) and can have additional support technicians assigned. All assigned technicians see the job on their mobile app, and time tracking is recorded separately per technician. This is useful for HVAC installations, solar installations, electrical teams, and cleaning crews.
Q: How do technicians get notified when a job is assigned? A: When a job is assigned and moved to dispatched status, the assigned technician receives a push notification on their mobile device. They see the job on their job list with the customer details, job site address, and job description. They do not need to check WhatsApp or wait for a phone call.
Q: Can I see where my technicians are in real time? A: Yes, GPS live location tracking is included on all plans. The dispatch board shows each technician's last known GPS location, updated as they move. For the full calendar view with real-time location overlaid on the schedule, Professional plan is required.
Q: What happens if a job overruns and the next customer is waiting? A: When a job goes on_hold or runs significantly over its scheduled time, the dispatcher sees this on the board — either via the hold status flag or via the GPS location showing the technician still at the previous site. They can then adjust the next job's timing, reassign it to another technician, or contact the waiting customer directly.
Q: Does the dispatch board work on mobile for the dispatcher? A: The dispatch board is primarily designed for the web app, which is optimised for a desktop or laptop screen. For dispatchers who are mobile — business owners doing dispatch from their phone — the list view is accessible on mobile, though the full calendar view is better experienced on a larger screen.
Title variations
- "How to dispatch multiple technicians efficiently" (47 characters)
- "Technician dispatch for South African service businesses: the practical guide" (76 characters)
- "From WhatsApp to structured dispatch: how SA service companies manage their teams" (80 characters)
- "Managing multiple technicians: when WhatsApp stops working and what to use instead" (81 characters)
- "How to run a dispatch board for your SA field service business" (61 characters)
Meta description
Managing three or more technicians from a WhatsApp group stops scaling. Here is how structured dispatch works — list view, calendar, real-time tracking. (152 characters)
Key takeaways
- WhatsApp dispatch lacks confirmation visibility, geographic awareness, and priority management — these limitations compound as team size grows
- List-view dispatch is sufficient for teams of two to five technicians; calendar drag-and-drop dispatch becomes significantly more useful at six or more
- The calendar dispatch board shows all technicians, time slots, job status, and live GPS in one screen — no phone calls needed to know what your team is doing
- Multi-technician job assignment allows lead and support technician roles on a single job, useful for HVAC installs, solar, cleaning crews, and electrical teams
- Moving to structured dispatch requires centralising all job intake into one system — a mixed system (some in the app, some in WhatsApp) means incomplete visibility
Internal linking suggestions
- "dispatch board feature" → /features/dispatch-board — The core feature page for the dispatch board with full specifications
- "GPS tracking" → /features/gps-tracking — Real-time location is central to efficient dispatch; a natural cross-link
- "running your business from WhatsApp" → /guides/whatsapp-vs-job-management-software — Detailed guide on the broader WhatsApp vs software comparison
- "HVAC multi-tech jobs" → /industries/hvac — Multi-technician dispatch is specifically relevant for HVAC; cross-link for HVAC readers
- "pricing" → /pricing — Starter vs Professional distinction matters for dispatch board selection; link to pricing page