Field service CRM for Canadian service businesses
A customer rings and says “you were here last spring”. Whoever answers either knows what happened, or spends the next four minutes apologising and searching. That gap is what a field service CRM is for — and it is a different problem from the one a sales CRM was built to solve.
This page is about the operational customer record: who they are, which properties they own, everything you have quoted, done and billed there, and how that hands over into scheduled work. It is deliberately narrower than the full lifecycle guide, and section nine is explicit about the sales and marketing features Opsler does not have.
What makes a CRM useful for field service
A sales CRM is organised around an opportunity moving toward a close. Everything in it — stages, probabilities, forecasts, activity logs — exists to answer “will this deal land, and when”. That is a good design for selling software. It is the wrong shape for a business that fixes furnaces.
A CRM for field service is organised around a different question, and field service customer management follows from it: what has happened at this address, and what happens next? The relationship does not close when the deal is won — that is when it starts. A customer you served in 2023 is worth more than a prospect, because they will call again, and the record of what you did for them is what makes the second visit profitable.
That reframing has three consequences worth checking in any product you evaluate, whether it calls itself a field service CRM, CRM field services, or field service customer relationship management.
- History has to be complete, not summarised. Quotes, jobs and invoices all attached to the customer — not a note saying “serviced 2023”.
- The property matters as much as the person. People move; buildings do not. History that follows the payer instead of the address loses its value the moment a rental changes hands.
- The field needs it too. History locked in an office system is history the technician standing at the panel cannot use.
Create a consistent customer and prospect record
Not everyone who calls becomes a customer, and a system that only has customers forces you to either create fake ones or keep enquiries somewhere else. Opsler holds both, and they are different records.
A lead is someone who has enquired. It carries a name, phone, email, address, where they came from — website, referral, cold call, social media, advertisement, walk-in or other — a priority you set of low, medium, high or urgent, and a status through six stages:
| Status | What it means |
|---|---|
| New | Captured, nobody has spoken to them yet |
| Contacted | First conversation has happened |
| Qualified | Real work, worth quoting |
| Unqualified | Not a fit — wrong trade, wrong area, wrong scale |
| Converted | Became a customer and a job |
| Lost | Went elsewhere or went quiet |
Winning the work converts the lead into a customer and a job in one step, so nothing is retyped and the source is preserved. Knowing that eleven of last quarter’s thirty jobs came from referrals is the kind of thing that changes where you spend money, and it costs nothing to capture at the point the phone rings.
A customer is someone you have worked for: contact details, a service address, an optional separate billing address, an alternate phone, notes, a province for tax, and running counts of total jobs and active warranties. Customers are unlimited on every plan including the free one.
Duplicates, caught at the door
Try to create a lead with a phone number that already belongs to an unconverted lead and Opsler refuses it. That sounds minor and is the difference between a customer list you trust and one you do not — the same person entered three times by three people is how history fragments, and once fragmented it is hard work to rejoin. Worth testing deliberately during any evaluation: enter the same prospect twice on purpose and see what the software does.
Connect properties, contacts and service locations
Service work happens at addresses, and the relationship between the person and the address is rarely simple. Opsler separates the service address from the billing address on the customer record, and every job carries its own address.
That covers the arrangement most Canadian service businesses actually meet: a property management company in Vancouver engages you, the work is in a suite, and the invoice goes to the management office. The job files against the building; the money goes where it should; and when the management contract moves to a different firm next year, the building keeps its service history.
Be clear about the limits here
There is no separate property register. A customer holds one service address plus an optional billing address; where a customer has many properties, each job carries its own address rather than hanging off a site record. In practice that means you can always see the work done at an address, but you cannot report by property across a portfolio, or hold notes and documents against a building independently of the jobs.
Nor is there an equipment register. No record for a specific rooftop unit with its model, serial, install date and warranty tracked in its own right — that context lives in the job notes and photos from previous visits. For a business managing a handful of properties per customer this is a non-issue. For one managing hundreds of units under contract it is the reason to choose something else, and you will know which you are.
Keep quotes, jobs and invoices in customer history
This is the part that separates a customer list from a CRM worth having. Everything commercial attaches to the customer: every quote you sent and whether it was accepted or rejected, every job with what was done, the photos and the notes, and every invoice with whether it was paid.
The practical payoff arrives on the second call. A commercial kitchen in Calgary rings about a cooler running warm. Before anyone leaves, you can see you were there eight months ago, replaced a condenser fan motor, charged $860, and that the invoice was paid in eleven days. You know what to send, what to charge, and that they pay. None of that required anyone to remember anything.
Rejected quotes stay in the history too, which is more useful than it sounds — a customer who declined a $6,000 replacement last year and is now on their third repair is a specific and winnable conversation.
What history does not include: any record of communication that happened outside Opsler. Phone calls, texts and emails from your own inbox are not logged against the customer, because there is no telephony and no email integration. If you need every touchpoint captured automatically, that is a general-purpose CRM feature and section nine is where that boundary is drawn.
Hand approved work into scheduling and dispatch
The handoff from “they said yes” to “someone is going” is where work is most often dropped, because in most businesses it crosses a boundary between two systems or two people.
In Opsler the accepted quote becomes the job, carrying its line items, the customer and the address. That job appears in the unscheduled queue, which is visible on the same board as the day’s assigned work — so accepted-but-unbooked work is in front of whoever schedules rather than in an inbox. Booking it and assigning it to a technician takes the record the rest of the way.
The single failure this prevents is the accepted quote that nobody books. It is the most expensive administrative error a small service business makes, because the customer has already said yes and the first sign of the problem is usually them phoning to ask when you are coming.
Where it goes from there is covered elsewhere: field service scheduling software for the diary and repeat work, and field service dispatch software for the day-of board and reassignment.
Give office and field teams the right context
A customer record that only the office can reach is half a system. The technician standing in the mechanical room is the one who most needs to know what happened last time.
Opening a job on a phone shows the customer, the address, the access notes, the scope and the property’s history — the same records the office is looking at, not a stripped-down field copy. The technician can add notes that become part of that history, so the next person to attend reads what actually happened rather than what was scheduled to happen.
Access differs by role rather than by device. Office staff work across the operational picture; a field technician sees their assigned work and the customers attached to it rather than your entire customer list; the customer sees one job through a link, with no account and nothing to install.
Worth knowing for a small team: the dedicated office-staff role is a Pro feature. On the free Budding plan the two seats are one admin and one technician, so the moment you want a third person with their own scoped access, that is the upgrade trigger rather than job volume.
Permissions, privacy and data-quality checks
Permissions
Four levels of access: administrator, office staff, field technician, and the customer’s per-job link. Deactivating someone removes their access immediately, and because access follows the account rather than a registered device, there is no device list to clean up afterwards.
Privacy, stated carefully
You are holding names, addresses, phone numbers and photographs of people’s homes, which is personal information and carries obligations under Canadian privacy law. What Opsler provides is role-based access control and the ability to revoke it. What Opsler does not provide, and does not claim: any privacy certification, an attestation of compliance with Canadian privacy legislation, or Canadian data residency — hosting is in the United States. If your obligations require records to stay in Canada, that is a hard boundary and it should end the evaluation here rather than after a migration.
Data quality
A CRM degrades in predictable ways, and the two worth actively managing are duplicates and orphaned history. Opsler blocks a duplicate lead by phone number at creation, which stops the most common source. The one to watch is jobs raised against a hastily created customer rather than the existing one — worth a five-minute check monthly rather than an annual clean-up, because merging history after the fact is considerably more work than avoiding the split.
Ask any vendor, including this one, how you export your customers and job history. A confident answer is a good signal, and you want to know it before you have three years of records rather than after.
Sales automation and marketing features: what Opsler is not
The clean way to think about this: keep a sales CRM for pipelines and campaigns if you need one, and use Opsler for the operational record from the point work is won. The two jobs are genuinely different and one product doing both usually does neither well.
Specifically, Opsler has none of the following, and you should not infer them from the word CRM.
- Email sequences, drip campaigns or marketing automation. No scheduled sends, no nurture flows, no open or click tracking.
- Lead scoring. The lead priority field is set by a person choosing low, medium, high or urgent. Nothing is calculated from behaviour, and calling it a score would misdescribe it.
- Pipeline forecasting. No weighted deal values, no expected close dates, no revenue projection, no reporting by salesperson.
- Telephony or omnichannel support. No click-to-call, no call recording, no shared inbox, no live chat.
- AI sales tooling. No suggested next actions, no generated outreach, no propensity modelling.
Jobber, Zoho, Salesforce and Microsoft all publish CRM capability of various depths alongside their field service products, and Zoho and Salesforce in particular are built to connect field work to a full sales CRM. If your business genuinely has a sales function, that is a sensible architecture and worth looking at properly.
For the large majority of small Canadian service businesses, though, the sales process is a phone call and a quote. Adding a pipeline to that is ceremony, and the record that actually earns money is the one showing what you did at that address and whether they paid for it.
Field service CRM evaluation checklist
Test with your own customer list, including the messy records. The tidy ones never reveal anything.
- Enter the same prospect twice on purpose. See whether you are stopped and how clearly.
- Set up a customer whose billing address differs from the service address. Invoice it and confirm where it went.
- Take a lead from first call through to a converted customer with a booked job. Confirm the source survived the conversion.
- Open a customer with several past jobs and time how long it takes to answer “what did we do here last time and what did it cost”. Under ten seconds or it is not doing its job.
- Do the same test on a technician’s phone, on site.
- Check what a field technician can see. If they can browse your whole customer list, decide whether you are comfortable with that.
- Ask how you export customers and job history, and in what format.
- Count seats: at US$25 per seat per month with no minimum, an owner, an office manager and three technicians is five seats, billed in US dollars.
Unlimited customers on the free Budding plan means steps one to five can be run on your real list without paying anything — two seats, 50 jobs a month, no card. Step six needs the Pro office-staff role, covered by the 14-day trial.
Common questions
No to all three, and it is worth explaining what does exist so the answer is useful rather than just negative. There is a genuine prospect record: a lead carries a name, phone, email, address, a source, a status through six stages, and a priority of low, medium, high or urgent. It converts into a customer and a job when you win the work. What there is not: a visual pipeline with weighted deal values and forecast totals, email sequences or drip campaigns, any marketing automation, and no lead scoring — the priority field is set by a person, not calculated from behaviour. That last distinction matters. A lead score implies the software is watching engagement signals and ranking prospects for you; Opsler's priority is you deciding this one is urgent. Calling it scoring would be a small lie that would set the wrong expectation, so we do not.
For most small service businesses, yes, and for a few, no — the dividing line is whether you have a sales function separate from your operations. If quotes go out from the same people who do the work, one system holding customers, prospects, quotes and jobs is simpler and more accurate than two systems that need to agree with each other. If you employ salespeople who work leads for weeks with multiple touchpoints, forecast against targets, and need pipeline reporting by rep, Opsler will frustrate them. It has no forecasting, no activity tracking against a rep, no commission reporting and no email integration. Run a proper sales CRM for that team and let Opsler own the operational record from the point work is won.
Access follows the role. An administrator sees the business; office staff see the operational side; a field technician sees their assigned work and the customers attached to it rather than your whole customer list; a customer sees a single job through a link with no account. Deactivating someone removes their access immediately. On storage, the honest answer for a Canadian buyer: data is hosted in the United States, and there is no Canadian data residency option. If a client contract or an internal policy requires Canadian hosting for customer records, that rules Opsler out and it is better to know now. Opsler makes no claim to any privacy certification — what it provides is role-based access, and how you handle personal information under Canadian privacy law remains your business's obligation.
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.