Field service dispatch software for Canadian teams
Dispatch is a job you do between 7am and about 10am, and then again every time something breaks. A no-heat call comes in from Scarborough at minus eighteen, and somebody has to decide within a minute or two who is going, what moves, and who gets told. Dispatch software either makes that decision faster or it is overhead.
This page covers the day-of workflow — the queue, assignment, reassignment, statuses and exceptions — for a Canadian field service business. Booking work into a calendar in the first place is a different job, and it belongs to field service scheduling software. Section 9 covers route optimisation and GPS — the two Pro features that take driving out of the day and take the check-in calls off your dispatcher.
Dispatch versus scheduling in field service
These two words get used interchangeably and they describe different work at different moments. Getting the distinction right is what stops you buying a calendar when you needed a control board, or the reverse.
Scheduling is a decision about the future. A customer calls on Tuesday, you look at the diary, and you book them for next Monday at 9am. The questions are about availability and capacity — who is free, how long will it take, can we fit it before the end of the month.
Dispatch is a decision about today. It is 8:15, one technician is stuck on a job that has turned out to be a compressor replacement, and there are two calls waiting. The questions are about the present — who is actually free, what moves, and who needs to know. Dispatch is triage, and it is judged on how fast you can reorganise, not on how the week looked on Friday.
Most terms in this space — scheduling and dispatching software, dispatch scheduling software, plain field scheduling, or the broader field services management that covers both and everything after them — bundle the two, because most products do both. Opsler does too. We separate them across two pages because the buying questions are different: if your problem is an empty diary you want the scheduling page, and if your problem is a chaotic 8am you are in the right place.
A caution on the word “dispatcher software” specifically: it also returns trucking and logistics dispatch, freight brokerage and taxi products. Those solve load boards and driver hours, not service calls. If you are running technicians to customer addresses, they are not your category.
Build a usable queue of ready and unscheduled jobs
The board opens on a date, day or week, with an unassigned column beside a lane for each technician. The unassigned column is sorted by priority, and it holds today's work and everything ahead of it — which is the mechanism that stops a job quietly ageing.
That sounds mundane. It is the single most common failure in small field service operations. Work that has been accepted but not booked lives in somebody's inbox or head, and the first anyone knows about it is the customer ringing to ask when you are coming. A queue that is always visible on the same screen as the day's assignments turns that from a memory problem into a housekeeping one.
Above the lanes, the board summarises the day: total jobs, how many are assigned, how many are not, how many technicians are available and how many you have in total. For a dispatcher covering six technicians across the Greater Toronto Area, those five numbers answer “how bad is today” before you read a single job.
If you run more than one crew — a residential team and a commercial team, say — the board filters by team so you are not scrolling past work that is not yours to move.
Assign work with the customer and site context attached
Assigning a job hands over more than a name and an address. The technician gets the customer record, the service address, the access notes and the property's job history — what was done there before, by whom, and what it cost.
For a return visit that context is the difference between a productive hour and a wasted one. A furnace that has been serviced twice at the same address in Barrie tells the technician something before they open the panel. Without history they start from scratch, and the customer notices that they are explaining it again.
Where the customer is a property manager and the work is at a tenant's address, the record keeps the two apart: the job files against the service address, the invoice goes to the billing address. Job history stays with the building even when the payer changes.
Assignments can be made one at a time or in bulk. Bulk assignment settles each job on its own, so a single failure in a batch of twenty does not roll back the other nineteen — you get a count of what succeeded and what did not, and you fix the exceptions.
Reassign jobs when the day changes
Reassignment is the core dispatch action, and the measure of a board is how little ceremony it involves. Move the job to another technician's lane. The record keeps who held it before, which matters when you are reconstructing why an appointment slipped three days later.
Two things make reassignment safe rather than merely fast. The first is the conflict check: put someone on two jobs whose times overlap and you get an error that names the job it collides with, rather than a silent double-booking that surfaces when a customer phones. The second is availability — each technician shows as available, busy or offline, with their booked windows and the day's job count, so you are moving work onto someone who can take it.
Availability is not purely manual, either. Busy sets itself while a job timer is running, so the board reflects who is actually on a job rather than who was scheduled to be. On a morning where two jobs have overrun, that distinction is the whole picture.
Changes propagate without anyone refreshing anything. Move a job in the office and it appears on the technician's phone; they change a status in the field and the board shows it. That is the part that removes the confirmation phone calls, which on a busy morning is most of a dispatcher's day.
Use job statuses to coordinate office and field
Opsler uses five job states, and the restraint is intentional — a status list long enough to describe every nuance is a status list nobody updates.
- Pending — the job exists and nobody is on it. This is your queue.
- Assigned — it belongs to a technician and is on their day.
- In progress — work has started.
- Completed — finished, with the evidence attached.
- Cancelled — closed without the work happening.
The office reads those states instead of ringing to ask. When a technician marks a job in progress, the dispatcher knows the next one is going to slip before the customer does — which is the moment to call ahead, and the reason to bother with statuses at all.
Completion is not a checkbox. A job needs at least one before photo, one after photo and a signature before it can close. In service work that requirement pays for itself the first time a customer disputes the condition of something on arrival, and it means “completed” on the board is backed by evidence rather than by somebody tapping a button in the driveway.
On Pro, technicians also record time as work and pause intervals with a reason attached — a parts run, a break, waiting on the customer. For diagnosing where a day actually went, that is considerably more useful than a single elapsed number.
Handle urgent work, delays and cancellations
Exceptions are the actual work of dispatch. Three patterns cover most Canadian service days.
The emergency that jumps the queue
A no-heat call in February is not a scheduling question. Raise it as a job, set its priority so it sorts to the top of the unassigned column, and place it with whoever is closest to free — reading the availability column rather than guessing. The technician who loses their afternoon slot sees the change on their phone.
The job that overruns
A one-hour service call becomes three hours. The status stays in progress and the technician's remaining jobs are visibly at risk. You move the last one to tomorrow or to another technician, and the conflict check keeps you from creating a second problem while solving the first.
The cancellation
Cancel the job and you have an unexpected gap. The unassigned queue is where you go looking to fill it — which is the argument for keeping unbooked work on the same screen as the day rather than in a separate list.
All three come down to the same thing. The board makes the situation legible in a few seconds — who is free, what is at risk, what it costs to move — and then the person who knows the crew makes the call and it lands on the right phone immediately. That is what turns a chaotic 8am into a ten-minute one, and it is the part of the job you can test on real work this week without paying anything.
Give the customer their own window onto the job
Half of a dispatcher’s morning is answering the same question: when is somebody coming. Opsler takes that question off the phone by giving every job its own customer link.
The customer opens it in whatever browser is already on their phone — no account, no password, nothing to download — and sees their job and can message you about it from there. That last part matters more than it sounds. Ask a homeowner to install an app to check a service appointment and most of them simply will not, which is how customer-facing features quietly go unused. A link opens first time for everyone: the homeowner, the tenant, the neighbour with the key, the property manager two provinces away.
It also keeps the conversation about one job in one place rather than scattered across three voicemails and a text thread nobody can find. The question arrives attached to the job it is about, your dispatcher answers it from the same record, and what was agreed has exactly one version.
Confirmations, quotes and invoices go out by email, from the record they belong to, so the customer’s inbox and your job history tell the same story six months later when somebody asks what was promised.
Cut the driving, and see the day moving
Two Pro features do most of the work here, and both are about getting hours back rather than about watching anybody.
Route optimisation
Route optimisation is an Opsler feature. Give it the day’s stops and it hands them back in the order that leaves the least driving between them. On a spread of six or seven addresses across the Greater Toronto Area, that is an hour of windscreen time recovered — which is one more billable call, every day, for every technician. Multiply that across a five-van crew and the subscription stops being a line item and starts being a rounding error.
GPS
GPS is an Opsler feature too, and what it buys the office is the end of the check-in phone call. You can see the job was picked up, that the technician is on the way, and that the work is finished — and so, when the customer rings at 11 to ask, can whoever answers. Six months later, when somebody disputes whether you attended at all, the record is already there and nobody has to reconstruct it.
The dispatcher still makes the call
Who takes the emergency is a judgement about people, not a calculation. Your dispatcher knows who holds the gas ticket, who the customer in Etobicoke asks for by name, and who has already had a bad morning. That knowledge is the advantage a small operation has over an enterprise scheduling engine, and Opsler is built around it: the board makes the situation obvious in a couple of seconds, the conflict check stops the expensive mistake, and the decision reaches the right phone before the dispatcher has put the handset down.
Job timers on Pro record work and pause intervals against the job with a reason attached — parts run, break, waiting on the customer — which is what you need to cost a job honestly and to find out where Tuesday actually went.
Field service dispatch software evaluation checklist
Test dispatch software on a bad morning, not a good one. Every board looks capable when the day is going to plan.
- Load a real day for a real crew. Then insert an emergency at 8:15 and time how long it takes to place it and move what it displaces.
- Deliberately double-book somebody. Confirm you are stopped, and that the warning tells you which job it clashes with.
- Reassign a job and check the technician's phone. If they need a phone call to learn about it, the board is not doing its job.
- Cancel a job mid-morning and see how quickly you can fill the gap from the unassigned queue.
- Run route optimisation on a genuine day of stops and see how much driving comes out of it. That number is the business case, and it takes five minutes to get.
- Open the customer link the way your customer will — on a phone, with no account — and decide whether it answers “when are they coming” well enough to stop the call.
- Count seats honestly. A dispatcher plus four technicians is five seats at $25 each per month, with no minimum and no tier above it.
The dispatch board is included on the free Budding plan, so steps one to four can be run on real work without a card: two seats, 50 jobs a month, unlimited customers. Route optimisation, GPS, timers and the dedicated office-staff role are Pro, and the 14-day trial covers them. If you want the whole customer-to-invoice picture rather than the day-of board, start with cloud field service management software, and if the field devices are your question, see the mobile field service app page.
Eighteen things the board does on a bad morning
Every line checked against the product. Take the list into your next demo and ask for the same eighteen answers in the same words.
| Claim | Opsler | Detail |
|---|---|---|
| Unassigned job queue, sorted by priority | Today and ahead, so nothing quietly ages out of view | |
| One lane per technician, day or week view | Their jobs in time order beside the unassigned column | |
| Filter the board by team | Earns its keep the moment you run more than one crew | |
| Assign and reassign a job | Reassignment records who held it before | |
| Assign many jobs at once | Each settles independently — one failure does not sink the batch | |
| Double-booking conflict check | Raises an error and names the job it collides with | |
| Technician availability and busy slots | Available, busy or offline, with each booked window and the day's job count | |
| Busy set for you while a timer runs | The board shows who is genuinely on a job, not who was meant to be | |
| Board updates without a manual refresh | An assignment made in the office appears on the technician's phone | |
| Customer and site context travels with the job | The record, the service address, the access notes and that property's history | |
| Separate service and billing addresses | Work at a tenant's address, invoiced to the property manager who pays | |
| Completion backed by evidence | A before photo, an after photo and a signature before a job can close | |
| Job timers with a reason on every pause | Parts run, break, waiting on the customer. Pro plan | |
| Route optimisation | Pro plan. The day in the order that leaves the least driving between stops | |
| GPS | Pro plan. The job picked up, the technician on the way, the work done | |
| Per-job customer link | Opens in their own browser — no account, no password, nothing to install | |
| Canadian invoices with GST or HST | Canadian dollars, Canadian dates, the rate configured once and applied per line | |
| The whole board on the free plan | Budding: 2 seats, 50 jobs a month, unlimited customers, free forever |
Both, on the Pro plan, and they pay for themselves in different ways. Route optimisation hands you the day in the order that leaves the least driving between stops. On six or seven addresses spread across a metro area that is the difference between finishing at four and finishing at six, and it is usually where the extra call of the day comes from. GPS answers the questions an office actually asks out loud: has that job been picked up, is the technician on the way, is it done. You read the answers off the board instead of ringing round for them. The assignment itself stays with your dispatcher, which is where it belongs — they know who the customer in Etobicoke asks for by name, who is ticketed for gas, and who is already three streets away. None of that lives in the data, and it is exactly what a small operation is good at. Opsler's job is to make acting on it take a couple of seconds, and to stop you double-booking somebody while you do it.
Yes — the whole dispatch board is part of the free Budding plan, which is unusual in this category and worth knowing before you pay anyone anything. Budding gives you two seats, one admin and one technician, with 50 jobs a month and unlimited customers, free forever. That is enough to run a real morning through it: load a genuine day, drop an emergency into it at 8:15, and see how fast the board lets you move what it displaces. When you outgrow two people, Pro is $25 per seat per month with no seat minimum, so a dispatcher plus three technicians is four seats and nothing else — and that is where the dedicated office-staff role lives, which is how you give a dispatcher full access to the board without making them an administrator. The 14-day trial does not ask for a card.
The invoices you send your own customers are Canadian all the way through: Canadian dollars, Canadian date formatting, Eastern time, and GST applied at a five percent default. Where your province charges HST you set that instead, as a named rate with its own type, and you can hold more than one configuration at a time with one marked as your default — which is what a business working either side of a provincial border needs. A rate can apply to labour, to parts, or to both, so the two are treated differently on the same document when that is what your bookkeeper wants. The customer record carries a province field that feeds it. Set it up once and every invoice raised from a completed job comes out with the breakdown already worked out, which is one fewer thing anybody has to check on a Friday afternoon.
Related
Field service scheduling software
Calendars, booking, rebooking and conflicts
Cloud field service management
The full Canadian lifecycle hub
Mobile field service app
What technicians can do on a phone
Field service CRM
Customers, properties and service history
Opsler pricing
$25/seat/month, free Budding plan
Ready to Run Your Business Without the Chaos?
Scheduling, dispatch, estimates, invoicing, customer portal, and a free branded website — start completely free, upgrade to Pro when you scale.
Free forever on the Budding plan. No credit card required.