Field service CRM for Canadian service businesses

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:

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.

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.

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.

Where sales automation belongs, and why it is not here

The clean division: a sales CRM owns pipelines and campaigns, Opsler owns the operational record from the point work is won. One product attempting both usually does neither well, and for the large majority of small Canadian service businesses the sales process is a phone call and a quote — where a pipeline is ceremony and the record that earns money is the one showing what you did at that address and whether they paid for it.

So the word CRM means something narrower here than it does in a sales tool. Five things it deliberately does not carry, stated plainly so nothing is inferred:

• 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.

If you employ salespeople who work leads for weeks, forecast against targets and need reporting by rep, run a proper sales CRM for that team and let Opsler own everything from the point the work is won. Those two systems meeting at the handoff is a sensible architecture, and it is a different question from the one this page answers.

If your sales process is the phone ringing and a quote going out, you already have the whole thing here — and you are not paying for a pipeline nobody updates.