Service is a lost art: the PiiComm service standard

Most enterprise mobility providers sell Day One: sourcing, staging, configuration, rollout. PiiComm was built for Day Two — everything that happens to a fleet after the deployment ends, for the three to five years it stays in service.

This is the PiiComm service standard. It sets out the five commitments that make it up, where they came from, what happens when we fall short of them, and the operational machinery that holds them up. It is the most complete public statement of how we service Canadian mobile fleets.

Day Two: everything that happens after the deployment ends

Day One is visible, scoped and well funded. It gets a project manager, a weekly call and a risk register. Day Two gets a shared inbox — and it is the longer, more expensive half.

When Day Two isn’t anyone’s job, the failure pattern is consistent. A scanner dies. Internal IT has no configured spare, so they open a warranty claim that needs a serial number nobody recorded at deployment. Four days later the device ships for repair. Meanwhile a frontline worker has been doing a scanning job without a scanner, and nothing about it reached a report.

That is a small tax, collected constantly, invisible at the top. Across a few hundred devices and a few thousand incidents a year it stops being small — it just never arrives as a single number anyone has to sign off on.

In regulated operations it is not a tax but a clock. Under Canadian hours-of-service rules, a carrier whose electronic logging device malfunctions may run paper logs for 14 days while the unit is repaired or replaced. Fourteen days is generous until day 12, with no spare and no repair ETA, and a truck that has to roll.

“This technology was being deployed, but there was no real thought as to what happens after day one. It does break, it does fail, it does need to be replaced. That was a big gap.”

Shawn Sicard — Partner, PiiComm

Why service became a lost art in enterprise mobility

Service didn’t fade out of enterprise mobility because anyone stopped caring. It is a structural artifact of how the industry grew up.

The money was in hardware and deployments. Both are transactions with a clean finish line. Service is unglamorous, unbounded and hard to price, so it became an afterthought — a support line at the bottom of a statement of work, priced as a percentage of hardware, resourced accordingly.

Buyers absorbed the same assumption. Managing a fleet looks like something a capable IT team should handle, because managing a handful of phones is. The gap between those two things is enormous and nearly invisible until you are standing in it.

Two forces are widening it. The category is compounding: one industry forecast puts managed mobility services on a path from roughly US$8 billion in 2024 to over US$100 billion by 2035. Forecasts that steep deserve a grain of salt, but the direction is not in dispute — more devices, more suppliers, more platforms, more regulation.

At the same time, the people who would absorb that work are the scarcest and most expensive in the building. Canada’s tech workforce reached about 1.54 million in 2026 at a median wage of $103,104, roughly 49% above the national median, according to CompTIA’s State of the Tech Workforce Canada 2026. Those are the salaries being spent when a systems administrator files a warranty claim for a cracked scanner.

“Customers assume managed mobility is easy. They feel they can do it themselves, and then they’re not able to keep up on best practices, because they’re focused on the business on the other side. Are you focused on the business, or in the business? It’s hard to do both.”

Rick Robillard — Partner, PiiComm

PiiComm was founded in 2007 on the other side of that observation. Our founder was working inside a carrier, watching devices go into the field across Canada at scale and watching nobody take responsibility for what happened next. The phrase that started the company was four words long: service is a lost art.

The five commitments we hold to

Every provider says its service is excellent. The claim is free to make, which is why it is worth nothing on its own.

Ours is written down. An unwritten standard is whatever the person on shift decides it is that day, and it erodes quietly as a company grows. A written one can be held up against what actually happened last Tuesday — by a customer, and by us. These five apply to every client, at every size, on every issue, including the small ones.

“We make sure that we’re chasing them and they’re not chasing us.”

Adam Nicol — President & Chief Operating Officer, PiiComm

The third commitment is the hardest to sell and the one we care about most. Good managed mobility is felt as an absence — of tickets, of escalations, of Monday mornings that start with a device problem. It is difficult to take credit for something a customer never had to notice.

“A lot of customers don’t appreciate what we do because we don’t make noise. That’s our whole reason for being here — to take away the noise.”

Shawn Winter — Partner, PiiComm

Clients describe it in less flattering language:

“With PiiComm, they became the middle-man for me and resolve the issues that I can’t spend hours on the phone for.”

Robert Crooks — Supervisor, Technical Services, Ivaco Rolling Mills

What happens when we miss a service commitment

We will miss occasionally, and any provider who says otherwise is selling something. Three things then happen without you having to ask.

The issue escalates up the documented path because we raised it, not because you followed up. Your named account manager stays accountable for the resolution and for telling you where it stands until it closes. And the miss is logged and reviewed with you at your next service review, so the underlying pattern gets addressed rather than the single incident.

Inside the support model: service desk, spare pools and fleet visibility

A service charter is only as good as the machinery underneath it. Ours runs on six operational practices — none exotic, all expensive to build and tedious to maintain, which is why most organizations don’t.

A bilingual service desk, staffed in Canada

Your users reach one of our own technicians, in English or French, around the clock. Not a routing menu and not an offshore first line whose job is to take a message. We can answer on a dedicated line in your company’s name. The helpdesk model is built for frontline workers rather than IT administrators — the caller is usually mid-shift, holding a broken device, with a job to finish.

Escalation that doesn’t stall

Tier 1 triages and resolves what it can on the call, with first-call resolution as the target. Tier 2 handles deeper diagnosis. A documented route into engineering sits behind that. The ticket stays with us across every handoff, so you are never the party carrying context between two of our teams.

Spare pool management

The least glamorous practice on this list and probably the most consequential. We hold and maintain a pool of spares configured to your build. When a device fails, a working replacement goes out and the user keeps working. The alternative — ordering, waiting, or pulling from a drawer of half-configured hand-me-downs — is where most fleet downtime originates. Sizing that pool is its own discipline; we’ve written about what happens when organizations get it wrong.

Repair and warranty handling

We manage the repair cycle and the OEM warranty claim on your behalf. Your team never files one, never chases one, and never needs to know which devices are still in coverage, because we track it. This sits inside Lifecycle Management, alongside recovery, wipe and redeployment when people leave.

The AIM portal

AIM — Asset Intelligence Manager — has been in operation since 2007, the same year as the company. That is not a coincidence. A provider claiming to take away the noise has to give customers a way to verify it without calling, and that requires a system of record from the start rather than a dashboard bolted on later.

AIM is the central repository for a client’s fleet: every device, where it is, what state it’s in, what maintenance has occurred since deployment, how many units are in for repair right now, and what is approaching end of life. It tracks non-serialized items too — chargers, cradles, cases — which matters more than it sounds when a site is down for want of four mounting brackets. It currently tracks tens of thousands of assets for customers across the country.

The point isn’t the dashboard. It is that your reporting and ours come from the same place. When your account manager walks you through a service review, nobody is assembling a slide from a spreadsheet — you are looking at the record we work from daily, and you can log in and check it yourself at 11pm.

Named account management

One person who knows your environment, your sites and your constraints, running scheduled service reviews and following up on open issues and upcoming refreshes before you ask. The difference between a good managed mobility relationship and a transactional one usually comes down to whether somebody on the provider’s side thinks about your fleet when you aren’t.

“It’d be like buying a car and having to do your own oil changes from now on, and become a mechanic. You don’t want that, and our customers don’t want that either.”

Shawn Winter — Partner, PiiComm

Why sovereign managed mobility is a service question, not just a data one

Sovereignty is usually discussed as a data question: where records live, which laws reach them. That matters, particularly for a hospital, a police service or a federal department. In a service business it is also an operational question, and the operational version is more demanding.

Canada is difficult to service. It is enormous, the infrastructure is uneven, and any national fleet has devices in places where next-day anything is optimistic. Doing it well takes people who understand the geography, the carriers and the procurement rules, reachable and accountable when something breaks at 6am three time zones away. We’ve written separately on what national service delivery actually takes.

There is also a language obligation that isn’t optional. A frontline worker in Trois-Rivières with a dead handheld should get support in French from someone who can fix it, not a transfer and a hold queue. For healthcare and public sector clients a parallel obligation applies to the data: the ticket, the device record and the personal information attached to it stay in the country.

“Sovereign managed mobility means all practices, people, and accountability reside in Canada.”

Rick Robillard — Partner, PiiComm

Canadian technicians, Canadian facilities, service in English and French, and no offshore handoff at the point where a customer needs help. It isn’t a flag on a website. It’s who picks up.

What a service standard is worth over the life of a fleet

The return on a service standard shows up slowly. Nearly 20 years in, the measure we take most seriously is that the customers who joined early are mostly still here — through hardware generations, through the shift from capital projects to service models, through their own reorganizations.

That retention doesn’t come from winning a bid. It comes from what happens in the years afterward.

This category has seen a lot of ownership changes, and service is usually the first thing quietly deprioritized after one. Staying Canadian-owned and staying in a single business has let us keep the standard stable long enough for it to mean something — which is the only way a standard ever does.

“It’s one thing to get the contract. It’s what you do afterwards that defines who you are as a company.”

Shawn Sicard — Partner, PiiComm

Service and support questions we get asked

What is Day Two in managed mobility?

Day Two is everything that happens to a device fleet after deployment ends: breakage, repair, replacement, configuration drift, warranty expiry, refresh and decommissioning. Day One — sourcing, staging, configuration and rollout — is a project with a finish line. Day Two runs for the working life of the fleet, usually three to five years or longer, and is where most of the operational cost and risk sits.

What is PiiComm’s service standard?

PiiComm’s service standard is five written commitments: we own the problem, we follow up rather than waiting to be chased, we keep device issues away from your team, we stay engaged after the rollout, and we remain accountable in Canada. It applies to every client regardless of size, contract value, or how small the issue is.

What happens when a mobile device fails?

Your user contacts PiiComm’s service desk, where a Tier 1 technician triages and attempts to resolve the issue on the call. If the device needs replacing, a configured spare ships from the pool so the user keeps working, and PiiComm manages the repair or the OEM warranty claim on the failed unit. The ticket stays with PiiComm until it closes — your team doesn’t chase the manufacturer.

Is PiiComm’s service desk located in Canada?

Yes. PiiComm’s service desk is staffed by PiiComm employees in Canada and operates in English and French, around the clock. Calls are not routed offshore and are not handled by a subcontracted third party. For public sector, healthcare and government clients, this keeps both the support interaction and the data behind it inside the country.

What is spare pool management?

Spare pool management means PiiComm holds and maintains a pool of spare devices configured to your build and sized to your fleet and breakage rate. When a device fails, a ready-to-use replacement goes out rather than your user waiting on a repair turnaround or a new order. PiiComm maintains the pool, keeps its configuration current, and reports on its status in the AIM portal.

What is the AIM portal?

AIM — Asset Intelligence Manager — is PiiComm’s client-facing management portal, in operation since 2007. It is the central record for a client’s fleet: device location and status, repair progress, maintenance history since deployment, warranty position, end-of-life reporting, and non-serialized items such as accessories. It currently tracks tens of thousands of assets for customers across Canada, and clients log in directly rather than requesting reports.

What happens if PiiComm misses a service commitment?

Three things happen without the client asking. The issue escalates up the documented path on PiiComm’s initiative rather than on the client’s follow-up, the named account manager stays accountable for the resolution and for keeping the client informed, and the miss is logged and reviewed at the next scheduled service review so the underlying pattern gets addressed.

What should you ask a managed mobility provider about support?

Ask who answers the phone and where they sit. Ask what happens to a failed device in the first hour, not the first week. Ask whether spares are held and configured in advance or ordered on demand. Ask who files the warranty claim. Ask what reporting you receive without requesting it, and on what cadence. Those five answers separate a support line from a support model.

Where to start

A service claim is easy to write and almost impossible to verify from a web page, so don’t take this one on faith. If the Day Two problem is something you’re currently absorbing without naming, book a walkthrough and we’ll show you the desk, the reporting and the AIM portal your team would be working with — run by the people who’d be running your account.

If you’re earlier than that, start with the economics. Our Lifecycle Management guide covers what Day Two costs when nobody owns it.

Managed mobility services, it’s all we do.

References

• CompTIA, State of the Tech Workforce Canada 2026 — workforce size, growth and median wage figures.
• Transport Canada, Electronic logging devices for commercial drivers and motor carriers — malfunction and paper log provisions under the Commercial Vehicle Drivers Hours of Service Regulations.
• Market Research Future, Managed Mobility Services Market Report — market size and forecast to 2035.