Service management software for Canadian small businesses
Search for service manager software and you will get four unrelated products: software for businesses that send people to customer sites, software for running an IT department, software for answering support tickets, and a utility for managing services on a Windows machine. They share a word and nothing else.
This page answers the first one — a small Canadian business that repairs, maintains or services things for customers, and wants the work from request to paid invoice in one place. Section two sorts out which of the four you are looking for, and section nine says plainly when you should be buying something else. If that is you, we would rather you found out here than after a trial.
Field service management versus ITSM and helpdesk software
The fastest way to tell which one you need is to ask what your business is actually tracking. Each category is organised around a different record, and that record shapes everything else about the product.
| Category | The question it answers | Core records | Yours if… |
|---|---|---|---|
| Field service management | Who is going to the customer's site, and what happened when they got there? | Customers, properties, jobs, quotes, invoices | Your people travel to the work. This is Opsler. |
| IT service management (ITSM) | How do we run IT support against agreed service levels? | Incidents, problems, changes, service catalogue, SLAs | You run an internal IT function or an MSP. |
| Customer support helpdesk | How do we answer inbound customer questions across channels? | Tickets, conversations, macros, satisfaction scores | Your team answers email, chat and calls rather than attending sites. |
| Service manager utilities | How do I manage services running on this machine? | Processes and system services | You are a systems administrator and landed here by accident. |
The test that settles it: does somebody travel to the customer? If a person gets in a vehicle and goes to an address, you want field service management. If the work is resolved from a desk, you want a helpdesk or an ITSM platform, and this page is not for you — section nine has recommendations.
The overlap that confuses people is real, though. Both categories triage incoming requests, both assign work to a person, both track it to completion, and both close with a record of what was done. What differs is what happens in the middle: a helpdesk optimises the conversation, and field service optimises the visit. Software built for one handles the other badly, which is why generic service business management software so often disappoints both.
The other names for the same answer
Once you have established that your people travel, the remaining vocabulary is mostly a question of who is doing the searching. An owner tends to look for small business service software, because the size of the business is the constraint they feel. An operations lead tends to look for field service management cloud solutions, because they are thinking about where it runs and who can reach it. Somebody who has just inherited a spreadsheet looks for service business management software and hopes for the best.
All three land in the same place. The one distinction underneath the vocabulary that genuinely changes the answer is scale, and it is worth being blunt about it because it decides your shortlist more than any feature does.
How small is small
Opsler is built for roughly one to fifteen people. Below that it is comfortably more than a diary and a notebook, and the free plan means the decision costs nothing. Above it you start meeting the ceilings: no equipment or asset register, no service-level agreement automation, no subcontractor portals, no multi-company consolidation, and no work-order hierarchies for jobs that decompose into sub-tasks.
The failure mode to avoid is buying enterprise software early. A platform built for two hundred technicians carries configuration weight — record types, approval hierarchies, permission matrices — that a four-person business will spend months learning and never recover the cost of. The reverse mistake is cheaper to fix: outgrowing a small product means a migration, which is unpleasant but finite. Given the choice, outgrow something.
Capture the service request and customer context
Work arrives by phone, by email, or through your own booking page, and the first decision is whether the caller is already a customer. Both paths lead somewhere structured.
For someone new, a lead record holds their name, phone, email, where they came from — website, referral, a walk-in — a status and a priority you set. When the work is won, that lead converts into a customer and a job rather than being retyped. If the phone number already belongs to an unconverted lead, Opsler rejects it as a duplicate, which quietly prevents the mess of three half-records for the same person.
For an existing customer you go straight to a job against their record, with the address and history already attached.
Requests that come in through your branded booking page land in a pending queue rather than straight onto the schedule. Somebody reviews them before they become committed work, which is the correct default — a booking form that writes directly into your calendar is a booking form that will eventually put a fictional job in it.
What this is not: a ticket queue. There is no first-response clock, no priority escalation, no automated routing by category, and no satisfaction survey attached to a conversation thread. Requests become jobs, and jobs are managed as work.
Connect customers, properties and service history
A customer record carries 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.
For a small business the accumulated history is the asset. A commercial appliance repair company in Halifax attending its fourth call at the same restaurant can see what was replaced in each of the previous three, what it cost, and who went. That turns a diagnostic visit into an informed one, and it is the argument for keeping records in a system rather than in a filing cabinet and one person's memory.
The billing split does real work in Canadian commercial service. The restaurant calls you, the landlord pays, and the two are different records — Opsler files the job against the property and sends the invoice to the billing address.
The limit, stated once: there is no equipment or asset register. You cannot track a specific walk-in cooler with its own model, serial and service interval as a record in its own right. That detail lives in the job notes and photos. Deeper customer and prospect handling is covered on the field service CRM page.
Prepare the quote and approve the work
Some service work is quoted and some is done on the spot; a small business does both in the same week and needs the software to handle both without ceremony.
Quoted work: an itemised quote built against the customer and property from your own price book, each line with its quantity, rate and tax treatment. The customer approves from an emailed link — one-time code to their email, then a signature typed or drawn, timestamped against the quote. Accepted, it becomes the job with its lines intact.
Unquoted work: raise the job directly, do it, and invoice from what was done. No quote step, no empty approval to click past.
Approval in the other direction — your own — is an account-level setting: whether invoices need office sign-off before they go out. For a business where technicians raise invoices on site, that check is worth having on. For an owner-operator it is friction, and you turn it off.
Schedule and complete the service job
A job is booked into a slot and assigned to someone. It moves through five states — pending, assigned, in progress, completed, cancelled — and both the office and the person doing the work see the same state without anybody phoning to ask.
Booking someone onto two overlapping jobs raises a conflict that names the clash rather than silently accepting it. Each person's availability shows as available, busy or offline, with their booked windows.
Completion requires evidence: at least one before photo, one after photo and a signature. For service work that closes most disputes before they start — the condition on arrival is documented, and so is the state you left it in.
Repeat work — a quarterly maintenance visit, an annual inspection — runs as a recurring series generating jobs 30 days ahead, on the Pro plan. It generates on the interval you set; it does not choose dates intelligently or reschedule itself around a delay. Scheduling in more depth belongs to the field service scheduling software page.
Create the invoice and track its status
The invoice is raised from the completed job, carrying what was actually done rather than what was originally quoted — which matters, because the difference between those two is where small service businesses lose money.
It moves through a defined path: draft, pending approval where your business requires it, approved, sent, paid. Being able to see at a glance which invoices are sent and unpaid is, for most small businesses, the single most valuable screen in the product — more valuable than the schedule, because unbilled and unpaid work is invisible until someone goes looking for it.
Payment is recorded rather than processed. Opsler marks an invoice paid, tracks what is outstanding, and records the method — cash, cheque, or a bank transfer including Interac e-Transfer for Canadian accounts. It is not a payment processor, takes no platform fee, and money never moves through it.
Customers can still pay online. You attach your own payment link — the Stripe or Square page you already use — to an invoice or a job, and the customer sees it when they open their job link, paying you directly at your own processor rates. Opsler records that the invoice was settled. Worth doing the arithmetic when you compare vendors: a platform that processes payments for you generally takes a percentage on top of its subscription, and on a few hundred thousand dollars of annual invoicing that percentage is usually the larger number.
Mobile, accounting and GST/HST boundaries
Mobile
Opsler installs from a supported browser on desktop, Android and iPhone rather than from an app store. Offline, a technician can complete jobs with photos and a signature, tick checklists, add notes, change status, and create estimates and invoices — all syncing on reconnect. The board and the diary need a connection.
GST and HST
A Canadian account invoices in Canadian dollars. Tax is a named rate with a type — GST at a five percent default, HST where your province uses it — and you choose whether it applies to labour, parts, or both. More than one configuration can exist, with one as your default, and the breakdown calculates per line.
What that is not: Opsler 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 an invoice meets a CRA requirement. Configure it with your bookkeeper, not from a marketing page.
Accounting, and the subscription
Opsler exports QuickBooks-formatted and Xero-formatted CSV files that you import yourself, on the Pro plan. That is a download and an upload — not a connection, not two-way, not real time, and nothing flows back. And the subscription is billed in US dollars at US$25 per seat per month, with data hosted in the United States rather than in Canada. Both are real considerations for a Canadian buyer and neither improves by being buried.
When to choose specialist ITSM or customer-support software
If you got this far and the fit feels wrong, it probably is. Four signals mean you are shopping in the wrong category, and acting on them now saves you a trial and a migration.
- Nobody travels. If the work is resolved from a desk, everything Opsler is organised around — addresses, site visits, job photos, signatures — is overhead you will never use.
- You are measured on response times. Contractual service levels with escalation and breach reporting are the core of ITSM and absent here. Opsler tracks job states, not resolution clocks.
- Your volume is conversations, not visits. Hundreds of inbound messages a day need a ticket queue with routing, macros and canned replies. Opsler has no ticket queue.
- You need remote monitoring. Watching systems and raising work automatically when something breaches a threshold is remote monitoring software. Opsler has no monitoring, no alerting and no condition-based job creation.
Where to go instead: an ITSM platform if you run IT services against agreed levels, a helpdesk product if you are answering customer conversations at volume, and a remote monitoring and management tool if you are watching infrastructure. All three are mature categories with good products, and none of them is what this page describes.
The mirror image is worth stating too. If people do travel to sites, an ITSM platform will make you build addresses, job photos and mobile completion out of a ticket object that was never meant to hold them. Both mistakes are expensive; they are just expensive in opposite directions.
Service management software evaluation checklist
Seven checks. The first one is the only one that matters if you get it wrong.
- Confirm the category. Does somebody travel to the customer? If not, stop and read section nine again.
- Take one real service request from the phone call to a paid invoice. Count the screens and the retyping.
- Enter a commercial customer whose landlord pays. Invoice it and check where it went.
- Complete a job on a phone with no signal, including photos and a signature.
- Configure GST or HST for your province, produce a real invoice, and show your bookkeeper before you commit.
- Export a month of invoices and actually run the import into your accounting package.
- Price it in the currency you will be billed in. At US$25 per seat per month with no minimum, an owner, an office manager and two technicians is four seats in US dollars.
Steps two to four run on the free Budding plan — two seats, 50 jobs a month, unlimited customers, no card. Step six needs the Pro export and the 14-day trial covers it. For the same lifecycle with dispatch, mobile and plan comparison in full, the Canadian field service management guide is the wider page.
Common questions
No, none of the three, and the distinction is worth understanding rather than treating as a gap. Opsler has no incident, problem or change management, no service catalogue, no SLA definitions and no automated breach escalation, and no ticket queue with priorities and macros. Those are the defining features of IT service management and customer-support platforms, and they exist because those disciplines measure themselves on response and resolution times against a contract. Field service work is measured differently — on whether the technician arrived, what they did, and whether it was billed. A job in Opsler carries a status, a scheduled time and an assignee, which is the field-service equivalent of a ticket, but nothing in the product tracks a resolution clock or escalates when one is breached. If you need SLA reporting, buy an ITSM platform; they are excellent at it and Opsler is not attempting to compete.
Scope and starting point. This page is written for a small service business whose work begins with a customer request — a repair, a maintenance visit, a callout — and it stays close to that thread: request, quote, schedule, complete, invoice. The broader Canadian field service management guide covers the same lifecycle plus the parts that only matter once you have several people running it, including dispatch mechanics, mobile evaluation, and how the plans compare. If you are a two- or three-person operation trying to work out whether software helps at all, this page is the right size. If you are comparing products for a growing team, start with the hub.
Yes for applying them, no for filing them, and the difference is where people get caught. A Canadian account works in Canadian dollars and lets you configure a named tax rate with a type — GST at five percent is the default, and HST is available for provinces that use it. You choose whether that rate applies to labour, to parts, or to both, which matters when the treatment differs between the two, and the breakdown calculates per line and totals on the invoice. What Opsler does not do is file or remit anything: no Canada Revenue Agency connection, no business-number validation, and no certification that an invoice satisfies a CRA requirement. Separately — and this catches people — the Opsler subscription itself is billed in US dollars at US$25 per seat per month, not in Canadian dollars. Your invoicing currency and your subscription currency are 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.