A mobile field service app for Canadian teams
Judge field software on a phone, in a mechanical room, with one bar of signal and cold hands. That is where it is used. Almost every decision about it, though, gets made at a desk with good wifi — which is why so many teams buy something that demonstrates beautifully and then gets abandoned by the third week.
This page walks through what a technician can actually do on site with Opsler, in the order they would do it, and is specific about the two things this category is vaguest on: whether it is a real app, and what genuinely survives without a connection. Both answers have a caveat, and both caveats are here rather than in week three.
What a field service app should let technicians do
Strip out the marketing and a mobile app for field service work needs to do five things for the person holding it. Everything else is the office’s requirement wearing a field costume.
- See today. What is assigned to me, in what order, at which addresses.
- See the history. What happened at this address last time, and what it cost. This is the one that separates a job list from a field service mobile app worth using.
- Record what happened. Photos, notes, a signature, time on the job.
- Change the state. En route, arrived, done — so the office stops phoning to ask.
- Handle the money. An estimate on the spot, an invoice from the completed work.
The terms blur — mobile field service app, mobile apps for field service, field management app, mobile field service software, plain field service app — and they all describe roughly that list. The distinction that actually predicts satisfaction is whether the phone sees the same records as the office or a stripped-down copy of them. A cut-down field view means the technician cannot answer a customer question without a phone call, which defeats the purpose. Opsler gives the field the same customer, job, quote and invoice records the office is working in, with what people can see governed by their role rather than by their device.
Browser-installed app versus native iPhone and Android apps
Opsler installs from a supported browser. You open it on the phone, add it to the home screen, and from then on it launches from its own icon in its own window. It is not in the App Store and not on Google Play.
Both approaches are legitimate, and pretending otherwise would be the kind of claim this page exists to avoid. The honest comparison:
| Installed from the browser | Native store app | |
|---|---|---|
| Getting it onto a new hire's phone | Send a link; they add it to the home screen | Search the store, download, sign in |
| Updates | Arrive when you next open it | Store update, sometimes queued behind review |
| Mixed iPhone and Android crews | One address, same behaviour | Two builds, occasionally out of step |
| Finding it by searching an app store | Not possible | Yes |
| Deep device integration | Limited to what the browser exposes | Fuller access |
| Working with no signal | Specific scope — see section 8 | Varies by product; often broader |
Choose on the last three rows, not the first three. If your technicians expect to install things by searching an app store, or you need device capabilities a browser does not expose, buy a native product — ServiceM8 and Dusk both publish one. If what you actually want is for everyone to be on the same version without anyone managing that, the browser route is the simpler answer, and it is why Opsler chose it.
Install and sign in on supported devices
Opsler runs on a modern browser on desktop, Android and iPhone. Installing is the browser’s own add-to-home-screen action — the exact wording differs between iOS and Android, which is worth a sentence in whatever onboarding note you send a new technician.
The practical consequence is that onboarding is a link rather than a project. A technician starting Monday gets sent an invitation, signs in on whatever phone they already own, and is looking at their jobs. There is nothing to procure and no device standard to enforce, which matters for a trade where people bring their own phones and change them without telling anyone.
One thing worth testing rather than assuming: how it behaves on an older phone. A five-year-old Android with a cracked screen is a normal piece of field equipment, and the honest way to find out whether the experience holds up is to install it on one before you commit rather than on the newest handset in the office.
Open the customer, property and job record in the field
Opening a job shows the customer, the service address, the access notes, the scope, and the history of work at that property. Not a summary of it — the record.
The history is what changes the visit. A technician arriving at a walk-up in Montréal for a heating complaint can see the unit was serviced fourteen months ago, what was replaced, and what the customer was charged. That is the difference between asking the tenant to explain the problem from scratch and walking in already knowing half the answer. Over a winter it compounds into hours.
Where the property is managed, the record keeps the service address and the billing address apart, so a technician sees the building they are standing in while the invoice goes wherever it should. Job history stays attached to the property rather than to whoever is paying this year.
One limit to state here rather than let anyone assume otherwise: there is no equipment register. A technician cannot pull up a specific rooftop unit with its model, serial and full service history as a record in its own right. Those details live in the job notes and the photos attached to previous visits, which for most service work is enough and for asset-heavy maintenance contracts is not.
Create and update estimates and invoices
Money is handled from the phone, not just recorded for the office to handle later. A technician can build an estimate on site from your price book, and raise or edit an invoice from completed work.
The value is in the timing rather than the feature. An estimate written in the driveway while the customer is still standing there converts at a different rate from one emailed on Thursday. A diagnostic that turns into a $1,900 repair is a conversation you want to have with the numbers on the screen, not from memory.
Invoices carry your Canadian tax treatment — GST at five percent by default, or HST where your province uses it — with the breakdown calculated rather than typed. They move through draft, approval where your business requires it, sent, and paid.
Two boundaries. Payment is recorded, not processed — there is no card reader in the app and no money passes through Opsler, though you can attach your own payment link so the customer pays you directly through your own processor. And sending a quote out for customer approval needs a connection, because the approval happens in the customer’s browser — you can draft it underground and send it when you surface.
Use token-based customer access without an app download
Customers get a link, per job. They open it in whatever browser is already on their phone, see their job, and can message about it. No account, no password, nothing to install.
That constraint is the point. Asking a homeowner to download an app so they can see a service appointment is a request most of them will decline, and any adoption figure that depends on it should be treated sceptically. A link works on the first try, for everyone, including the customer’s tenant or their adult child who is letting you in.
Be precise about what this is, though. It is per-job access to that job — not a standing customer portal with an account, a login and a history of everything you have ever done for them. If your evaluation calls for a full self-service portal where customers manage their own records, this is not that, and you should test it rather than take the category word at face value.
What works offline—and what does not
“Works offline” is the least reliable phrase in this category, because it is technically true of almost everything and useful only when someone tells you the scope. Here is the scope.
| With no connection, a technician can… | |
|---|---|
| Complete a job with before and after photos | |
| Capture the customer's signature | |
| Tick through checklist items | |
| Add notes to the job | |
| Change job status — start, en route, arrived, complete | |
| Create an estimate | |
| Create or edit an invoice | |
| Open the dispatch board | |
| Reschedule or reassign work | |
| Look up a customer never loaded on that device | |
| Send a quote for customer approval |
Everything in the first group is stored on the device and syncs when signal returns — at the next intersection, in the truck at the end of the day, or the following morning. Nothing depends on the technician remembering to press anything.
The pattern is simple enough to explain to a crew in one sentence: what you do to a job in front of you works offline; what needs to reach the office or the customer in that moment does not. For a Canadian service business — basements, mechanical rooms, rural service areas, underground parking — the first group covers the situations where signal actually fails.
This is narrower than “full offline”, and deliberately described that way. Some native competitors offer broader offline capability. If your technicians routinely spend whole days out of coverage rather than minutes, test that specifically before choosing anything, including this.
Security, permissions and lost-device checks
Phones get left on roofs, dropped in snowbanks and handed to whoever is covering a shift. The questions worth asking are about access rather than about the hardware.
Who sees what
Access follows the role. An administrator sees the business; office staff see the operational side; a field technician sees their work and the customers attached to it; a customer sees one job through their link. The dedicated office-staff role is a Pro feature — on the free plan the two seats are one admin and one technician.
A device that goes missing
Deactivate the person and that phone stops reaching your data. Access is tied to the account rather than to a registered device, so there is no separate device list to maintain — which is one fewer thing to forget. Note that the free plan applies a cooldown before a technician seat can be replaced; find that out now rather than on the morning you need to swap someone.
What is still yours to do
Screen locks, remote wipe and device management are the phone’s responsibility, not the software’s, and no field service vendor should tell you otherwise. If you handle sensitive customer information, those controls belong in your own policy alongside whatever software you choose.
Mobile field service app evaluation checklist
Do all of this on a technician’s phone, not yours, and outdoors in February if you can arrange it.
- Install it on the oldest phone in the crew. If it struggles there, it will be abandoned there.
- Open a job and try to answer a customer question from the history without ringing the office. This is the whole value of the category in one test.
- Turn on aeroplane mode. Complete a job with two photos and a signature, add notes, change the status. Reconnect and confirm every piece of it arrived.
- Build an estimate on site with the customer watching. Time it. If it is slow, it will not happen in real life.
- Send yourself the customer link and open it as a customer would, on a phone with no account.
- Try it with gloves on. This sounds facetious and it is the single most common reason Canadian field crews stop using an app in January.
- Deactivate a test technician and confirm their device loses access.
- Count seats: at US$25 per seat per month with no minimum, four technicians and an office manager is five, billed in US dollars.
Steps one to seven run on the free Budding plan with no card — two seats, 50 jobs a month. For how the office half works, see field service dispatch software for the day-of board and field service scheduling software for the diary.
Common questions
No. Opsler installs from a supported browser — you open it on the phone, add it to the home screen, and it launches with its own icon in its own window rather than inside a browser tab. There is no App Store or Google Play listing, and there will not be one. That is a trade with real advantages and one real cost, and it is worth understanding both. The advantages: nothing sits between a fix and your technicians' phones, because there is no store review queue; a new hire in March is working in the time it takes to send them a link; and it works the same on whatever mix of iPhones and Androids your crew actually carries. The cost: you cannot find Opsler by searching an app store, and a small number of deep device integrations available to native apps are not available to us. If your business has a policy requiring store-distributed software, or your technicians expect to install things by searching the App Store, that is a legitimate reason to choose a different product, and ServiceM8 and Dusk both publish native apps.
It stays on the device and syncs whenever the phone next has a connection — at the end of the day in the truck, or the next morning. Nothing is lost by the passage of time and nothing needs the technician to remember to press anything. The practical thing to understand is which work this covers, because it is specific rather than total: completing jobs with photos and a signature, checklists, notes, job status changes, and creating estimates and invoices. It does not cover the office half — the board, the diary, or looking up a customer that was never loaded onto that device. The design assumption is that the field works offline and the office works online, which matches how the two halves actually operate.
Deactivate their account from the admin side, and that device stops being able to reach your data — there is no separate device registry to clean up, because access follows the person rather than the hardware. Two things are worth knowing alongside that. Because Opsler installs from the browser rather than as a store app, there is no separately downloaded application package sitting on the phone to worry about; what is on the device is a shortcut and cached working data. And on the free plan there is a cooldown before a technician seat can be replaced, which is worth knowing before you need it rather than at the moment you do. If you handle sensitive customer information, pair this with the normal device-level protections — a screen lock and remote wipe from your own mobile management — because those are the phone's job, not the software's.
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.