Cloud field service management software for Canada
Field service management software is a category name for something quite ordinary: keeping one thread from the first phone call to the moment the invoice is marked paid. The reason it needs a name at all is that the thread usually breaks — in the gap between the quote and the booking, or between the work being done and someone remembering to bill for it.
This is the Canadian hub. It maps that whole lifecycle, sets out Opsler's exact plan and product limits, and is direct about Canadian specifics — GST and HST on your invoices, the fact that the subscription is billed in US dollars, and the fact that data is not hosted in Canada. Where a topic has its own page, this one hands you over rather than repeating it.
What field service management software connects
Every vendor in this category publishes a feature list, and the lists are nearly identical. A more useful question is which records the software holds and whether they are genuinely joined, because that is where products differ and where the feature list is silent.
Field service management software should connect five things: the customer, the property where work happens, the money you quoted, the work you did, and the money you were paid. When those five are one thread, questions like “what did we do at that address last year and did they pay for it” take ten seconds. When they live in five tools, that question takes an afternoon and often goes unasked.
The category answers to several names. Buyers type it both ways round — cloud field service management software, and field service management software cloud — along with field services management, field service software Canada and field service management software Canada, and for a small business they all point at the same need. The phrase field service management software for small business is the one worth paying attention to, because scale changes the answer completely. Software built for a hundred technicians carries configuration weight that a four-person shop will never recover the cost of learning.
Opsler is built for the small end and is explicit about where that stops. No enterprise asset management, no equipment register, no service-level agreement automation, no subcontractor portals, no multi-company consolidation. If you need those, this page will have saved you an evaluation.
What “cloud” actually buys you, and what it costs
The word is used so routinely that it has stopped meaning anything, which is a shame because the trade-off is real and worth understanding before you sign anything.
On the useful side: there is no server in the back office, no version number to worry about, and nothing to install on a machine. A new technician gets a login rather than an IT visit. Updates arrive without anyone scheduling them. The office and the field see the same records at the same time, which is the actual point — field service software cloud products exist because the alternative was a desktop database that only the office could reach, and a technician phoning to ask what was on the job sheet.
On the other side, three things a Canadian buyer should weigh honestly. Your records live on infrastructure you do not control, which makes your export path part of the purchase rather than an afterthought — ask how you get your customers and job history out before you put them in. The office needs a working connection to do office things; only the field half of Opsler works offline. And where that infrastructure physically sits is a question with a real answer, covered in section eight, because for some Canadian contracts it is decisive.
None of that is an argument against cloud software. It is an argument for asking the three questions, and most vendors in this category would rather you did not.
Map the lifecycle from enquiry to invoice status
Ten stages, each with a record behind it. The value is not in any single stage — it is that each one inherits from the last, so nothing is retyped and nothing is reconstructed from memory.
| Stage | Record | What it holds |
|---|---|---|
| Enquiry | Lead or customer | Name, phone, source and priority, or straight to a customer record |
| Site context | Customer + service address | Separate billing address where a property manager pays |
| Quote | Itemised quote | Built from your own price book; single price or three tiers |
| Approval | Recorded acceptance | One-time emailed code plus a typed or drawn signature, timestamped |
| Job | Job with line items | Converted from the quote — nothing retyped |
| Schedule | Booked slot | Calendar and availability, with conflict checking |
| Dispatch | Assignment | Day-of queue, lanes per technician, reassignment |
| Field work | Job record | Photos, signature, notes, status, time intervals |
| Invoice | Invoice | Raised from the completed job with GST or HST applied |
| Payment status | Invoice state | Draft, approval where required, sent, paid |
Two joins in that table carry most of the weight. Quote to job means an accepted price becomes scheduled work with its line items intact. Job to invoice means what was actually done becomes what is billed. Break either one and you are back to re-keying, which is where the money leaks — the variation agreed on site that never reached the invoice, the completed job nobody billed.
One job through all ten stages
A property manager in Ottawa emails on a Tuesday about a rooftop unit short-cycling at a strip plaza. That becomes a customer record with the plaza as the service address and the management company as the billing address — two different places, recorded once.
A technician attends, diagnoses a failed contactor and a compressor drawing high amps, and that visit closes as its own completed job with photos of the nameplate and the readings. The replacement is quoted at $4,180 across seven lines — unit, crane time, refrigerant, disposal, electrical, labour, and a return commissioning visit. The quote goes out; the property manager opens it on a phone four days later, enters the code emailed to them, and signs. Timestamped.
Approved, it becomes a job carrying all seven lines. It is booked for the following Wednesday, assigned that morning to two technicians, and completed with before and after photos and a signature. The invoice is raised from that job: seven lines, $4,180, HST applied at the Ontario rate you configured, addressed to the management company and filed against the plaza.
Nothing in that sequence was typed twice, and eighteen months later when the same plaza has another unit fail, the whole history is on the property. That is the entire argument for the category, and it is worth testing on one of your own jobs rather than taking anyone's word for it.
Keep customers, properties and job history together
The customer record holds contact details, a service address, an optional separate billing address, notes, and every job done at that property. Customers are unlimited on every plan, including the free one, which matters because a service business accumulates them faster than it accumulates anything else.
The billing split is the feature that earns its keep in Canadian property work. A condo corporation in Mississauga engages you, the work happens in unit 704, and the invoice goes to the property manager. Opsler files the job against the service address and sends the invoice to the billing address, so the building keeps its history even when the management contract changes hands.
Before the customer exists there is a lead record — name, phone, source, priority, status — which converts into a customer and a job when the work is won. Duplicate phone numbers are caught at creation, which is a small thing that prevents a large mess. That side of the product is covered on the field service CRM page.
The limit worth knowing early
There is no equipment or asset register. You cannot create a record for a specific rooftop unit or boiler — model, serial, install date, warranty expiry — and track its service history independently of the jobs performed on it. Each job carries its own address, and history is assembled from the jobs. For most residential and light commercial work that is sufficient. For asset-heavy maintenance contracts where you report by unit rather than by customer, it is a genuine and unbridgeable gap in the current product.
Create quotes and move approved work forward
Quotes are itemised, built against a customer and a property from a price book you maintain. Each line has its own quantity, rate and tax treatment. You can offer a single price or three tiers on one document where the customer picks a level.
One detail to check before you send a tiered quote, because it produces an awkward phone call otherwise: the tiers are cumulative. The middle tier bills its own line plus the first tier's, and the top tier bills all three. Confirm the total the customer will actually see rather than assuming the tier line is the tier price.
Approval happens in the customer's browser. They open an emailed link, enter a one-time code sent to their email, choose a tier if you offered them, and sign — typed or drawn. No account, no password, nothing to install. The approval is stored against the quote with its timestamp. It is not a formal e-signature product, and for work where you need evidentiary weight you should run one alongside; for a $2,800 furnace replacement it is more than most businesses have today.
Accepted, the quote becomes the job with its line items intact. What Opsler will not do is chase the quote for you — there is no automated follow-up sequence and no open tracking. You can see which quotes are sitting unanswered and for how long; the phone call is yours to make.
Schedule, dispatch and update field jobs
Two distinct jobs live here, and they have their own pages because the buying questions differ. In outline:
Scheduling is the diary — availability, booking a customer into a slot, rebooking cancellations, catching double-bookings before they become phone calls. Repeat work runs as a recurring series generating jobs 30 days ahead on the Pro plan. Field service scheduling software covers it properly.
Dispatch is today — a priority-sorted queue of unassigned work, a lane per technician, assignment and reassignment, and the five job states that keep the office and the field in step without phone calls. Field service dispatch software is the detailed page, including the section on what is and is not automated.
The short version of that last point, since it is the most misrepresented thing in this category: route optimisation is real and is a Pro feature you trigger yourself; GPS exists as location stamps at four moments in a job rather than as live tracking; and there is no skills matching, no automatic assignment and no capacity optimisation of any kind. Every job is placed on the board by a person.
Support office and field teams across devices
The office works on a desktop; the field works on a phone in a mechanical room. The same records serve both.
Opsler installs from a supported browser on desktop, Android and iPhone, and then behaves like an installed app. It is not distributed through the App Store or Google Play. That is a deliberate trade rather than an omission: no store review between a fix and your technicians' phones, no download step when you hire someone in March, one address that works on whatever device is in the truck. If your business specifically requires a store-listed app, that is a fair reason to choose differently.
Offline coverage is narrow and specific, which is better than a vague promise. Technicians can complete jobs with photos and a signature, tick checklists, add notes, change job status, and create estimates and invoices without a connection — all syncing when signal returns. The diary and the dispatch board need a connection. Plan for the field to work offline and the office to work online. The mobile field service app page has the device-by-device detail.
Roles separate what people see: an administrator, office staff, field technicians, and a customer view. The dedicated office-staff role is a Pro feature — on the free plan you have one admin and one technician, which is workable for a two-person business and not for a three-person one.
Handle invoices, GST/HST and accounting exports carefully
This is where Canadian buyers should read most closely, and where a distinction gets blurred so often that it is worth stating twice.
Your invoices are Canadian
A Canadian account works in Canadian dollars, formats dates the Canadian way, and runs on Eastern time. Tax is set up as a named rate with a type: GST is the default at five percent, and HST is available for provinces that use it. You choose whether a rate applies to labour, to parts, or to both — useful when the treatment differs — and you can hold more than one configuration with one marked as your default. The breakdown calculates per line and totals on the invoice. A province field on the customer record supports this.
Your subscription is American
Opsler charges US$25 per seat per month in US dollars. It does not bill in CAD, and what appears on your statement moves with the exchange rate. Data is hosted in the United States; there is no Canadian data residency. If a client contract or a procurement policy requires Canadian hosting, Opsler cannot meet it.
What tax handling is not
Opsler applies the rate you configure and shows the breakdown. It does not file or remit GST/HST, does not connect to the Canada Revenue Agency, does not validate a business number, and does not certify that any invoice satisfies a CRA requirement. Configuring a tax rate is a bookkeeping decision — take a real invoice to your accountant before you rely on it.
Accounting is a file, not a connection
Opsler exports QuickBooks-formatted and Xero-formatted CSV files that you import yourself, on the Pro plan. Not a sync. Not two-way. Not real time. No automatic reconciliation. Invoices move through draft, approval where your business requires it, sent, and paid — and payment is recorded rather than processed: Opsler is not a payment processor, charges no platform fee, and money never passes through it.
Compare plans, limits, support and Canadian requirements
The published limits, without the asterisks. Everything below is a real boundary in the product rather than a soft guideline.
| Budding (free forever) | Pro | |
|---|---|---|
| Price | Free | US$25 per seat per month, no minimum |
| Seats | 2 — 1 admin and 1 technician | 1 included, US$25 per extra seat |
| Jobs | 50 per month | Unlimited |
| Customers | Unlimited | Unlimited |
| Inventory | 100 items, 1 location | Unlimited items, multiple locations |
| Dispatch board | Included | Included |
| Quotes and invoices | Included | Included |
| Recurring job series | — | Included, generated 30 days ahead |
| Route optimisation | — | Included, user-triggered |
| GPS milestone stamps | — | Included, four moments per job |
| Technician timers | — | Included |
| Office-staff role | — | Included |
| QuickBooks / Xero CSV export | — | Included |
| Trial | Not needed — free forever | 14 days, no credit card |
Canadian requirements worth putting on your own shortlist, whoever you buy from: which currency the subscription is billed in, whether the vendor supports HST as well as GST, where data is hosted, and whether support hours overlap your time zone — a vendor answering from Sydney is awkward in Vancouver. Opsler's answers are USD, yes, the United States, and email support. Two of those four will suit you and two may not, which is the point of asking.
What switching actually costs
The subscription is the visible number and rarely the largest one. Budget for the rest honestly: getting your customer list in, deciding how much job history comes across, and the fortnight where your team runs two systems because nobody trusts the new one yet. On a small team that fortnight is the real cost, and it is why testing on live work — not demo data — matters more than any feature comparison.
Two questions to ask every vendor on your list, including us. How do customers and properties get in, and in what format? And how do they get out again if this does not work — can you export your customers, jobs and invoices, and what shape are they in when you do? A vendor who answers the second question comfortably is usually worth more trust than one who only wants to discuss the first.
If a genuinely free plan is what you are after, the free field service software comparison sets Opsler's Budding plan against Zoho FSM, ServiceM8 and Dusk on the same criteria, with dated sources — and running a free plan on real work for a month is the cheapest way to answer the switching question before you commit.
Field service management software evaluation checklist
Run one real job end to end. Not a demo job — one you actually did last week, with its awkward details intact.
- Create the customer with a service address and a different billing address. Take it all the way to a paid invoice and check where the invoice went.
- Quote it, approve the quote from your own phone as the customer would, and confirm the job inherits every line without retyping.
- Schedule it, then break the schedule — reassign it, and confirm the technician learns about the change without a phone call.
- Complete it on a phone with no signal. Photos, signature, notes. Reconnect and confirm nothing was lost.
- Configure GST or HST for your province and produce the invoice. Show it to your bookkeeper before you commit.
- Export to your accounting package and actually run the import. This is the step most often described optimistically.
- Ask the four Canadian questions from section 9 — currency, HST, hosting, support hours — of every vendor on your list, and write the answers down.
- Count seats. At US$25 each with no minimum, an owner, an office manager and four technicians is six seats billed in US dollars. Compare that against your current spend, converted honestly.
- Give it to the person who will actually use it most — usually whoever answers the phone — and let them try to book a week without help. Software chosen by an owner and used by an office manager fails on usability more often than on features, and you will learn more in that hour than from any comparison table.
Steps one to four run on the free Budding plan with no card. Steps five and six need Pro, and the 14-day trial covers them. If the answer to step seven is that you need Canadian data residency, stop there — that is a boundary Opsler does not cross.
Common questions
Neither, and both deserve a straight answer because they are real reasons to choose someone else. Opsler's subscription is billed in US dollars at US$25 per seat per month; your card issuer handles the conversion, so what lands on your statement moves with the exchange rate. Jobber, being Canadian, bills in CAD. Data is hosted in the United States — there is no Canadian data residency option. If your business has a procurement requirement or a client contract specifying Canadian hosting, that rules Opsler out and you should not spend further time on it. What is genuinely Canadian is the other half: the invoices you issue to your own customers. A Canadian account works in Canadian dollars, applies GST at five percent by default or HST where your province uses it, formats dates the Canadian way and runs on Eastern time. Your subscription currency and your invoicing currency are separate settings, and conflating them is the most common misreading of this page.
It is aimed squarely at small — roughly one to fifteen people — and it will frustrate you above that. The tell is what happens as you grow: Opsler has no enterprise asset management, no equipment or asset register, no work-order hierarchies, no service-level agreement automation, no subcontractor portals and no multi-company consolidation. A four-technician HVAC business in Winnipeg is well served. A hundred-technician operation running provincial contracts with SLA penalties is not, and Microsoft Dynamics 365 Field Service or Salesforce Field Service exist for exactly that. The free Budding plan is a fair way to find out which side of the line you are on: two seats, 50 jobs a month, unlimited customers, and no card required.
Opsler produces QuickBooks-formatted and Xero-formatted CSV files that you download and import into your accounting package yourself. That is the whole of it, and the wording matters because the category uses "integration" loosely. It is not a connection, not a two-way sync, not real-time, and there is no automatic reconciliation — nothing flows back from your accounting software into Opsler, and nothing pushes across on a schedule. The export is a Pro feature. If a live accounting connection is what you are buying, several competitors offer one and you should weigh that seriously rather than assume a formatted file is close enough. Practically, most small businesses export monthly and the import takes a few minutes; the question is whether your bookkeeper is happy with that rhythm.
Where to go next
Field service dispatch software
The day-of queue, assignment and exceptions
Field service scheduling software
Calendars, booking, rebooking and conflicts
Mobile field service app
Devices, installation and offline scope
Field service CRM
Customers, prospects, properties and history
Free field service software
Free plans compared on dated criteria
Opsler pricing
US$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.