Field service scheduling software for Canadian teams
Every schedule is a promise. Thursday between nine and eleven, someone will be there. The software’s job is to make sure that promise was possible when you made it, that everyone who needs to know about it does, and that when it changes — and it will — the change reaches the customer before they are standing at a window wondering.
Opsler shows you who is genuinely free before you promise anything, stops you double-booking a technician and names the job it would have clashed with, and moves the whole booking — customer, address, scope — in one action when Thursday falls apart. Quarterly and annual visits book themselves 30 days out. Two seats are free permanently, so you can load a real week onto it before you spend anything. What happens on the day itself is field service dispatch software.
- 30 days
- of repeat work ahead
- 2 seats
- free, no expiry
- 50 jobs
- a month on free
- $25
- per seat, no minimum
Scheduling versus dispatch and employee rostering
Three categories overlap here and buying the wrong one is a slow, expensive mistake — slow because it takes a few months to notice. The distinction is what each one schedules.
| Category | Schedules | Typical question | Opsler |
|---|---|---|---|
| Field service scheduling | Customer jobs into time slots | “Can we get someone there Thursday morning?” | This page |
| Dispatch | Today’s work against today’s reality | “Kowalski is running two hours late — who takes the 2pm?” | Its own page |
| Employee rostering | People into shifts | “Who is working Saturday, and does that trigger overtime?” | A separate tool, sitting alongside |
Scheduling and dispatch are two halves of one product here — separated across two pages because the buying question differs, not because they are separate tools. Rostering is a genuinely different category, and it belongs to a tool of its own: one handles your employees’ hours, Opsler handles your customers’ appointments, and they coexist without either getting in the other’s way.
The terms in the wild are looser than the table. Service scheduling, service scheduling software, field scheduling and scheduling software for service business all usually mean the first row. Anything promising shift patterns and labour cost forecasting alongside customer appointments is either two products or is doing one of them badly.
Capture unscheduled work before choosing a time
Work exists before it has a time, and that gap is where jobs get lost. A quote accepted on Friday, a maintenance visit due next month, a callback promised in spring — none of them belong in the calendar yet, and none of them should live only in somebody’s memory.
Opsler keeps unscheduled work in a queue sorted by priority, sitting on the same screen as the calendar rather than in a separate list. That placement is the whole mechanism. Anything in a separate list is something you have to remember to open; anything beside the calendar is something you see every time you book.
Work arrives in that queue from three directions: a quote the customer accepted, which converts into a job carrying its line items; a job raised directly by the office from a phone call; or a request submitted through your branded booking page, which lands pending review rather than writing itself into the calendar. That last default is the right one — a booking form with direct calendar access will eventually book a job that does not exist.
A practical habit worth adopting whatever software you choose: if the queue is growing week on week, you have a scheduling capacity problem rather than a software problem, and no calendar feature fixes it.
View the calendar, availability and booked jobs
The calendar shows a day or a week, with a lane for each technician and their booked jobs in time order. If you run separate crews — residential and commercial, or two regions — it filters by team so you are not reading past work that is not yours to move.
Availability is the part worth examining closely when you compare products. Each technician shows as available, busy or offline, and each of their booked windows carries a start, an end, the job it belongs to and that job’s status, along with a count of their jobs that day.
Two details make that more useful than a static diary. Busy sets itself while a job timer is running, so the calendar shows who is genuinely on a job rather than who was scheduled to be — a distinction that matters by mid-morning. And the day’s job count gives you a load reading at a glance: four jobs each across three technicians and one with nine is a problem you can see without opening anything.
Reading that imbalance takes about a second, and fixing it takes one drag. The person running your diary already knows which of those nine jobs can move and who can absorb it — the calendar’s job is to put the answer in front of them before the customer rings.
Book and assign a customer appointment
Booking and assigning happen together. Pick the job from the unscheduled queue, put it in a slot, and give it to a technician — the customer, the service address, the access notes and the scope travel with it.
That the context travels is not a small point. A technician who arrives knowing the gate code, that the dog is friendly, and that the last visit replaced a capacitor is a technician who does not phone the office from the driveway. Multiply that by four jobs a day across three people and it is most of a working morning saved somewhere.
Where you are booking a batch — twenty maintenance visits across a week, say — they can be assigned in bulk, and each one settles on its own. If two of the twenty fail, you are told which two rather than having the whole batch rolled back, which is the difference between fixing two problems and starting over.
The booking reaches the technician without anyone confirming it by phone; their view updates on its own. The customer gets their confirmation by email, attached to the job it belongs to, so six months later the inbox and your job history tell the same story about what was promised and when. One booking, one record, one version of the truth — which is what you actually want when somebody disputes a Thursday.
Rebook cancellations and handle conflicts
A schedule is judged on how it absorbs change, and two kinds arrive constantly: the customer who cancels, and the booking that should never have been made.
The double-booking you nearly made
Assign a technician to a job whose time overlaps one they already have, and Opsler raises an error that names the job it collides with. Not a warning you can scroll past — an error, with the conflicting job identified so you know what you are choosing between.
This matters more than it sounds because double-bookings are never discovered by the person who made them. They are discovered by a technician at 2pm, or by a customer at 4pm, and by then the cost is a phone call, an apology and sometimes the job. Catching it at the moment of booking is the cheapest possible place to catch it.
The cancellation
Cancelling leaves a hole. The unscheduled queue sitting beside the calendar is where you go to fill it, sorted by priority, which is the argument for keeping unbooked work on the same screen rather than in a separate list. Rebooking is moving the job to a new slot, and reassignment records who previously held it — useful three days later when someone asks why the appointment moved.
Filling the hole takes seconds because the queue is already sorted by priority and already on the screen. You pick the job that should have been done last week, drop it into the gap, and a cancellation stops being lost revenue and becomes the one thing on your list that finally got booked.
Put next year’s repeat work on the calendar today
Recurring work is where scheduling software earns its subscription. Here is exactly what you get.
You create a recurring series against a customer on a fixed interval — monthly, quarterly, annually. Opsler generates the jobs 30 days ahead, so upcoming work appears on the calendar before it falls due rather than the week it is needed. If you want longer visibility, a manual generation run can produce jobs further out, up to a year. A series can be active, paused, completed or cancelled, so a customer putting a contract on hold does not keep producing jobs nobody wants. This is a Pro feature.
Generated jobs land in the priority-sorted queue as ordinary unscheduled work, beside everything else waiting for a slot, and you book them into the week where they fit. That is deliberate. Maintenance visits are the flexible work in your diary — the jobs you use to fill the gaps a cancellation leaves — and having them visible a month early is what lets you build a full week instead of a lumpy one.
A series attaches to the customer, so an annual programme across a whole property portfolio stays on one record rather than fragmenting into dozens. Set it once, pause it the day a customer asks, restart it the day they come back, and stop running your maintenance revenue out of a calendar reminder and a good memory.
Pass the schedule into the day-of dispatch workflow
The seam between the calendar and the day is the five job states, and they are the same records rather than a handover between systems: pending, assigned, in progress, completed, cancelled.
A booked job is assigned. When the technician starts it, it moves to in progress and the office can see the rest of that person’s day is at risk without ringing to ask. When it closes — with its before photo, after photo and signature — it is completed, and the invoice can be raised from it.
That continuity is why scheduling and dispatch are one product rather than two. Where they differ is the time horizon you are working in: scheduling is a decision about a future slot with capacity in mind, and dispatch is a decision about now with reality in mind. The dispatch page covers the day-of half — the queue, reassignment, urgent work and exceptions. What technicians see and do on their phones is on the mobile field service app page, and the whole lifecycle around both sits in the Canadian field service management guide.
What Pro adds once the week is booked
A booked week is the start. Four Pro features decide how much of it you actually get paid for.
Route optimisation
Route optimisation is an Opsler feature. Hand it the day’s stops and it returns them in the order that leaves the least driving between them. On six or seven addresses across a metro area that is an hour a day, per technician, moved out of the van and into billable work — which for a five-person crew is a great deal more than the subscription costs.
GPS
GPS is an Opsler feature, and what it gives the office is the end of the check-in call: the job picked up, the technician on the way, the work done. When the customer rings at eleven to ask, whoever answers already has the answer on screen. The dispatch page covers both of these from the day-of side, where they earn their keep hardest.
Recurring series
Repeat visits generated a month ahead on the interval you set, pausable the day a customer asks and restartable the day they return. This is the feature that turns a maintenance book into predictable revenue rather than a set of reminders somebody has to keep.
Technician timers
Work and pause intervals recorded against the job with a reason attached — parts run, break, waiting on the customer. That is how you find out which work types actually make money for you, and it is the difference between quoting from instinct and quoting from evidence.
All four come in the one Pro price: $25 a seat, no minimum, nothing above it, and a 14-day trial that does not ask for a card.
Field service scheduling software evaluation checklist
Book a real week, then break it. A calendar that handles an empty week gracefully tells you nothing.
- Load a genuine week for your whole crew and time how long it takes. This is the task you will repeat every Friday afternoon for years.
- Double-book someone deliberately. Confirm you are stopped, and that you are told which job it clashes with.
- Cancel a Wednesday morning job and fill the gap from the unscheduled queue. Count the clicks.
- Set up a quarterly recurring visit and check how far ahead the jobs appear, and whether pausing it stops them.
- Run route optimisation over a real day of stops and see how much driving comes out of it. That saving is the business case, and it takes five minutes to get.
- Book a customer and check what actually lands in their inbox, on their phone, the way they will read it.
- Check the schedule on a technician’s phone, not on a desktop.
- Count seats: at $25 per seat per month with no minimum, a scheduler and four technicians is five seats, and your sixth hire costs $25 rather than a new plan.
Steps one to three run on the free Budding plan — two seats, 50 jobs a month, no card. Step four needs recurring series, which is Pro, and the 14-day trial covers it without a card.
Every claim in this category, answered
Eighteen claims made across field service scheduling software listings, each with the detail behind it rather than a bare tick. Take the list into your next demo and ask for the same eighteen answers in the same words.
| Claim | Opsler | Detail |
|---|---|---|
| Calendar in a day or week view | Filterable by team once you run more than one crew | |
| Unscheduled work visible beside the calendar | Priority-sorted, so accepted work does not go quiet | |
| Per-technician availability | Available, busy or offline, with each booked window | |
| Booked slots showing start, end and job | Plus a count of that technician's jobs that day | |
| Conflict detection on double-booking | Raises an error naming the job it collides with | |
| Busy set for you while a timer runs | The diary shows who is genuinely on a job, not who was meant to be | |
| Book and assign in one action | Customer, address and scope travel with the assignment | |
| Bulk booking of many jobs | Each settles independently; failures reported separately | |
| Rebooking and reassignment | Records who previously held the job | |
| Booking requests from your branded page | They land for review, so nothing writes itself into your week | |
| Repeat work on a fixed interval | Pro plan. Generated 30 days ahead; a manual run can extend to a year | |
| Series you can pause and restart | Active, paused, completed or cancelled, so a contract on hold goes quiet | |
| Technician job timers | Pro plan. Work and pause intervals with a reason, costed against the job | |
| 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 | |
| Five job states carrying into the day | Pending, assigned, in progress, completed, cancelled — one set of records | |
| Canadian invoices with GST or HST | Canadian dollars and dates, the rate configured once and applied per line | |
| The whole calendar on the free plan | Budding: 2 seats, 50 jobs a month, unlimited customers, free forever |
Route optimisation is an Opsler feature, included with Pro. Hand it the day's stops and it gives them back in the order that leaves the least driving between them, which on a spread of addresses across a metro area is an hour of windscreen time turned back into a billable call. The technician decision stays with the person making it, and at this size of team that is the advantage rather than the gap. Whoever runs your diary already knows which technician you send to the difficult customer in Scarborough, which two jobs can be stacked because they are on the same street, and who is best left off a Friday afternoon. Opsler's job is to make that person fast and hard to trip up: the load on every technician is visible at a glance, the conflict check names the job you would have collided with, and the whole booking — customer, address, scope — moves in one action when Thursday falls apart.
Yes, and this is where the subscription usually pays for itself. Create a recurring series against a customer on a fixed interval — monthly, quarterly, annually — and Opsler generates the jobs 30 days ahead, so next quarter's work is sitting on the calendar before anyone has to remember it exists. Need a longer view for planning or for a tender? A manual run generates further out, up to a year. A series can be active, paused, completed or cancelled, so a customer who puts a programme on hold stops producing work the same afternoon, and starts again with one click when they come back. That is a Pro feature, and it is the difference between a maintenance book you own and one that depends on somebody's diary reminders. Repeat visits attach to the customer, which keeps a whole programme running on a single record rather than scattered across dozens.
They are different jobs, and it is the most common category confusion in this space, so it is worth being clear. Opsler schedules customer work — this appointment, at this address, at this time, with this technician — and everything in the product is pointed at that: availability, conflicts, rebooking, repeat visits, and the job record the appointment turns into. Rostering software schedules people: who is working Tuesday, who is on lates, what that does to overtime. The two sit happily side by side, because one is about your employees' time and the other is about your customers'. The Pro plan does record technician work and pause intervals against a job with a reason attached — a parts run, a break — which is how you find out what a job really cost you and which of your work types are worth chasing more of.
Load next week onto it, then break it on purpose
Book a genuine week for your whole crew, double-book somebody deliberately, then cancel a Wednesday morning and fill the gap from the unscheduled queue. That is the Friday afternoon you will repeat for years, and it takes twenty minutes to find out whether this one handles it. The free Budding plan covers all of it — 2 seats, 50 jobs a month, no card, no clock.
Recurring series, route optimisation, GPS and technician timers come with Pro at $25 a seat, no minimum and nothing above it, on a 14-day trial that takes no card. Your fifth technician costs $25, not a new plan.
Related
Field service dispatch software
The day-of queue, assignment and exceptions
Cloud field service management
The full Canadian lifecycle guide
Mobile field service app
What technicians see and do on a phone
Service management software
The wider office workflow around the calendar
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.