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 sets out exactly what Opsler does and does not do on routing, GPS and automation, because that is where this category makes the loosest claims.
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.
What Opsler will not do in any of these cases is decide for you. There is no suggestion engine proposing who should take the emergency, no automatic reshuffling of the remaining jobs, and no rebalancing of the day. The board makes the situation legible in a few seconds; the judgement stays yours.
Keep customer communication claims evidence-based
Dispatch pages routinely promise the customer half of the story — automated on-the-way texts, live arrival windows, tracking links. It is worth checking each of those against what a product actually sends, because it is the most commonly overstated area in the category.
Opsler's position, plainly: customer communication runs on email. SMS is planned as a bring-your-own-provider option and is not live, so there are no automatic on-the-way texts and no appointment reminder messages today. There is no customer-facing live tracking link showing a van approaching on a map.
What does exist is a per-job customer link. The customer opens it in their browser — no account, no password, no app to download — and can see their job and message about it. For most residential service work that covers the “where are they” question adequately, and it does so without asking a homeowner to install anything.
If automatic customer texting is a requirement for your operation, name it in your shortlist and check it works before you buy. Several competitors do offer it, and on this point they are ahead.
GPS, routing, skills and automatic dispatch: what to verify
Four capabilities get sold as one bundle in this category, usually by vendors who have one or two of them. Here is Opsler's position on each, separately.
Route optimisation — yes, on Pro, and you trigger it
Select a set of stops and run it, and Opsler returns them in a more efficient order along with the distance and driving time for each leg. It is genuinely useful on a day with six or seven addresses spread across a metro area. Two qualifications: it is a Pro feature, and it is something you choose to run rather than something that happens on its own. There is no continuous re-optimisation as the day changes.
GPS — yes, on Pro, at four moments only
Opsler records a location stamp when a technician starts a job, marks themselves en route, arrives, and completes. Four points, each with a time. You can confirm that somebody was at the address at 10:42. You cannot watch a vehicle move, and nothing is recorded between those four moments. That is a deliberate design position rather than a missing feature: it answers the disputes that actually arise — did we attend, when — without putting a tracker on your staff.
Skills-based dispatch — no
Technicians have a skills field you can fill in and read, but nothing in the software matches a job to a technician by skill or filters the assignable list. If your work needs certification matching — gas fitting, refrigerant handling — you are relying on the dispatcher knowing who is ticketed for what.
Automatic and AI assignment — no
No auto-assignment, no suggestion engine, no capacity balancing, no schedule optimisation across a team. Every job on the board was placed there by a person. Microsoft Dynamics 365 Field Service, Salesforce Field Service, Zoho FSM and Fieldcode all publish automated scheduling and optimisation capabilities of various kinds; if that is what you are shopping for, they are the honest answer and you should go and look at them properly.
Nor does Opsler do employee rostering, payroll or time and attendance. Job timers record time against work, which is a different thing from a payroll clock.
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.
- Ask the four questions from section 9 separately — routing, GPS, skills matching, automatic assignment — and make the vendor answer each on its own.
- Check what the customer actually receives, and whether it is a real message or a roadmap item.
- Count seats honestly. A dispatcher plus four technicians is five seats at US$25 each per month, billed in US dollars, not CAD.
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 stamps, 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.
What the dispatch board does and does not do
Checked against the product. Amber means it exists with a condition attached.
| 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 | Useful once 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 | |
| Board updates without a manual refresh | An assignment made in the office appears on the technician's phone | |
| Route optimisation | Pro plan. You trigger it; it reorders a set of stops. Not automatic | |
| GPS location stamps | Pro plan. Four moments only: start, en route, arrived, complete | |
| Live vehicle tracking | No continuous or background location. The four stamps are the whole of it | |
| Skills-based dispatch | Technicians carry a skills field; nothing matches jobs against it | |
| Automatic or AI assignment | Every assignment is a person's decision | |
| Capacity optimisation across the day | The board shows you the load; it does not balance it for you | |
| Employee rostering, payroll, time attendance | Different category — use specialist workforce software | |
| Automatic SMS to customers | SMS is planned, not live. Customer communication is by email |
Two of those three, with conditions, and it is worth separating them because vendors in this category tend to sell all three as one thing. Route optimisation: yes, on the Pro plan. You select a set of stops and trigger it, and it returns them in a more efficient order with the distance and driving time for each leg. It is something you run, not something that runs itself. GPS: yes, on the Pro plan, but only as location stamps at four moments in a job — start, en route, arrived, and complete. That is deliberately not live tracking. You can confirm a technician arrived at the address at 10:42; you cannot watch a van move across a map, and nothing records location between those moments. Skills-based dispatch: no. Technicians have a skills field you can fill in and read, but nothing in the software matches a job to a technician by skill, and there is no automatic or AI-driven assignment of any kind. Every assignment on the board is a person deciding.
Yes — the dispatch board is part of the free Budding plan, which is unusual in this category and worth knowing. Budding gives you two seats, being one admin and one technician, with 50 jobs a month and unlimited customers. The practical catch for dispatch specifically is the seat count and the dedicated office-staff role: with two seats you are the dispatcher and you have one technician, so the board is doing real work but a small amount of it. The separate office-staff role, which is how you give a dispatcher access without making them an admin, is a Pro feature. Pro is US$25 per seat per month with no seat minimum, so a dispatcher plus three technicians is four seats, and the 14-day trial does not ask for a card.
No. Opsler bills in US dollars at US$25 per seat per month, and your card issuer handles the conversion, so what lands on your statement moves with the exchange rate. Worth knowing: this is not unusual in the category. Jobber is a Canadian company and its published pricing is also in US dollars, checked 4 August 2026. Ask any vendor directly rather than assuming a Canadian head office means Canadian billing. Where people do get confused is the other half: the invoices your business issues to your own customers are an entirely separate matter, and those are Canadian. A Canadian account defaults to Canadian dollars, GST at five percent, Canadian date formatting and Eastern time, and you can set HST instead if your province uses it. Your subscription currency and your invoicing currency are two different settings.
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.