The hardest part of choosing a managed mobility services (MMS) provider is not finding one—it is telling the difference between the ones that operate and the ones that outsource. Every provider’s website promises full lifecycle management, cost savings, and a single point of contact. The gap between the pitch and the reality only becomes visible after you have signed a three-year contract and your IT team is still shipping broken scanners. This guide gives you the practitioner’s framework for separating operational partners from marketing claims.
The single question that separates operational MMS providers from resellers
You are on a vendor evaluation call. The provider walks you through a polished slide deck: sourcing, staging, MDM, decommissioning, all five pillars. Everything looks comprehensive.
Then you ask one question: “When a Zebra TC53 breaks at our Winnipeg distribution centre on a Saturday night, walk me through exactly what happens—who touches the device, where does it go, and how long until the worker has a replacement in hand?”
The answer to that question—the specificity, the hesitation, the redirect to “we work with partners”—tells you more about the provider than 40 slides ever will.
Why this question works
Most MMS providers claim full lifecycle coverage, but the operational reality varies dramatically. The global managed mobility services market includes hundreds of providers, yet only a fraction operate their own staging, repair, and service desk infrastructure—the rest subcontract critical functions to third parties you will never meet and cannot vet.
The provider’s answer to “who actually does the work?” is the single most revealing question in any MMS evaluation.
The hidden vendor sprawl problem
In 15 years of managed mobility, the most common post-contract regret we hear from IT leaders is not about price or features. It is about discovering that their “managed” provider subcontracts staging to one company, repair to another, and MDM administration to a third—creating the same vendor sprawl they were trying to eliminate, just hidden behind a single invoice.
When something goes wrong—and in mobile operations, something always goes wrong—you need to know who is accountable. If the answer is “our partner handles that,” you have not hired a managed provider. You have hired a broker.
Lifecycle coverage—verifying what “full service” actually means
“Full lifecycle” is the most overused and least verified claim in managed mobility. When a provider says they cover sourcing through decommissioning, the follow-up is not “great”—it is “show me the facility.”
Five lifecycle stages and the proof to demand at each
Every MMS evaluation should verify capability at each stage of the device lifecycle. Not definitions—you can find those on any managed mobility services overview—but operational proof.
- Strategic Sourcing: Ask who negotiates your OEM pricing. Is the provider a Premier partner with direct OEM relationships, or are they reselling through distribution? The answer determines whether you get allocation priority during supply constraints or join the back of the queue.
- Staging & Deployment: Ask where devices are configured. Can you visit the facility? Who are the technicians, and what certifications do they hold? If the answer involves a third-party logistics provider, your “staged” devices may arrive with nothing but factory defaults and a user manual.
- Lifecycle Management: Ask how break/fix repair, hot spare pools, and ongoing device support actually work. Where is the repair depot? What is the turnaround time commitment, and what happens when they miss it?
- MDM Administration: Ask whether the provider administers your MDM environment or simply sells you a software licence. There is a difference between having SOTI installed and having certified administrators actively managing policies, compliance, and incident response.
- Secure Decommissioning: Ask for a sample chain-of-custody record from a previous client engagement. Can they show you timestamps, location data, technician identification, and certified data erasure documentation that meets NIST 800-88 standards?
The fragmentation cost
Organisations that fragment their mobility management across multiple vendors lose visibility and accountability. In-house mobility management programmes typically involve four to six separate vendor relationships for hardware, MDM software, carrier services, repair, and staging.
If your MMS provider is stitching together the same number of subcontractors behind the scenes, you have not consolidated anything. You have just added a middleman who now sits between you and the people actually touching your devices.
The staging test—ask to see the floor
If a provider stages devices in their own facility, they almost certainly have the operational infrastructure for everything else. If they do not, everything downstream is outsourced.
This is the simplest litmus test in MMS evaluation: ask to tour the staging operation.
We have had prospective clients visit staging facilities and watch a technician configure a Zebra TC72 with SOTI enrolment, three line-of-business apps, a Bluetooth ring scanner pairing, and an asset tag—in under 12 minutes. That specificity is what separates a staging operation from a provider that drop-ships factory-sealed boxes and calls it deployment.
A provider who hesitates at this request—or offers to “arrange something with our partner”—is telling you everything you need to know about where the actual work happens.
Canadian operational sovereignty as a selection criterion
When a Zebra handheld with cached patient records breaks at an Ontario hospital and gets shipped to a US repair depot, the hospital’s PHIPA obligations do not pause at the border. Neither do their PIPEDA breach notification requirements.
The question of where your MMS provider operates is not a brand preference—it is a compliance decision with documented legal consequences.
Why data residency matters for MMS
Canadian privacy law holds the data controller accountable for personal information even when processed by a third party. Under PIPEDA, organisations remain accountable for personal information transferred to a third-party processor, including cross-border transfers.
If your MMS provider processes device data outside Canada—whether that is repair diagnostics, MDM telemetry, or asset management records—your privacy impact assessment requirements and breach notification obligations change. Your procurement team needs to document that they evaluated this risk.
Quebec Law 25 adds another layer
For organisations operating in Quebec, Law 25 requires privacy impact assessments for any transfer of personal information outside Quebec and imposes mandatory breach notification with specific timelines.
A managed mobility provider that processes device data outside Quebec—let alone outside Canada—triggers PIA requirements that an in-province provider does not. If you have even a single distribution centre or retail location in Quebec, this is not a theoretical compliance exercise. It is a procurement filter.
Bilingual service delivery as a procurement requirement
Bilingual (English/French) service capability is not cultural courtesy—it is a procurement gate for federal, Quebec, and many healthcare contracts.
We have seen MMS evaluations for Quebec healthcare organisations disqualify otherwise strong providers in the RFP scoring because they could not demonstrate 24/7 French-language service desk capability. It was not a tiebreaker—it was a mandatory requirement that eliminated three of five shortlisted vendors before technical evaluation even began.
When evaluating providers, verify not just that they “offer” French service, but that the service desk is staffed with French-speaking agents around the clock. A provider that routes French calls to a translation service or limits French support to business hours will not survive a federal or Quebec healthcare procurement scoring matrix.
Rugged device expertise—the capability gap most evaluations miss
Your fleet is 60% Zebra scanners, 25% Honeywell handhelds, and 15% corporate smartphones. You evaluate three MMS providers. All three can manage the smartphones.
Only one has certified Zebra technicians, an OEMConfig-capable MDM team, and a repair depot that stocks TC-series parts. The other two will subcontract your rugged device repair to a third party you have never vetted—and your devices will sit in a queue behind that third party’s other clients.
The smartphone blind spot
Most “how to choose an MMS provider” guides treat devices as a generic category. They are not.
Managing a fleet of Zebra TC-series scanners and Honeywell handhelds requires fundamentally different capabilities than managing corporate iPhones: OEMConfig expertise, rugged device repair certification, industrial accessory management, and hot spare pools sized for mission-critical environments where a broken scanner means a stopped warehouse line.
Zebra Technologies reports that its rugged mobile computing and scanning devices are deployed across 95% of Fortune 500 companies. If your fleet includes rugged devices—and in transportation, retail, healthcare, manufacturing, and warehousing, it almost certainly does—your MMS provider’s OEM partnerships and repair certifications are not nice-to-haves. They determine whether a broken scanner means a same-day swap or a two-week wait.
OEMConfig—the technical detail that reveals operational depth
OEMConfig profiles for Zebra Android devices contain hundreds of configurable parameters that standard MDM templates do not expose. Battery optimisation settings. Scanner beam intensity. Display timeout policies tuned for warehouse lighting conditions. Trigger mapping for left-handed versus right-handed workers.
We have inherited fleets from previous providers where the MDM was technically “managing” the devices but had never configured OEMConfig—meaning every operational parameter was still at factory defaults. The devices were enrolled. They were not managed.
Ask your prospective provider to show you an OEMConfig profile they have deployed for a similar device type. If they cannot produce one—or if the conversation pivots to “our MDM supports OEMConfig”—you are talking to a provider who manages smartphones and handles rugged devices as an afterthought.
The distinction matters most when it matters most: at 2 a.m. when a TC52 will not pair with a ring scanner and the night shift supervisor needs a fix before the truck leaves the dock.
Knowing whether a provider can handle your rugged devices is only half the evaluation. The next question is whether their MDM administration goes deeper than a software licence—and whether their pricing model actually reflects the operational scope you need.
How to evaluate an MMS provider’s MDM administration depth
Owning an MDM licence and operating an MDM environment are as different as owning a commercial kitchen and running a restaurant. The licence gives you the tools. The administration gives you the outcomes.
This distinction trips up more evaluations than any other. A provider shows you a SOTI dashboard, walks through the feature set, and quotes you a per-device licence fee. You assume you are getting managed MDM. What you are actually getting is software with a support contract—and the expectation that your team will configure policies, troubleshoot enrolment failures, and respond to compliance alerts.
Platform certification and daily operational proof
When evaluating MDM administration as a managed service, verify three things: platform certifications, dedicated administrator headcount, and evidence of active management.
Platform certifications matter because MDM environments are not interchangeable. A provider certified on SOTI MobiControl operates differently than one certified on 42Gears or VMware Workspace ONE. Ask which platforms they are certified on—and whether they can show you a certification credential, not just a partnership logo.
Dedicated administrator headcount tells you whether MDM administration is a core function or a side task. A provider with two MDM administrators managing 50 client environments is not providing the same service as one with a dedicated team monitoring compliance dashboards, responding to policy violations, and pushing application updates during maintenance windows.
Evidence of active management is the hardest to verify and the most important. Ask the provider to show you a compliance dashboard from an active client environment—anonymised, but real. Ask them to walk you through how they handled a recent MDM policy conflict.
The policy conflict test
Here is a specific question that separates administrators from salespeople: “What happens when a SOTI lockdown profile and a line-of-business app’s permission requirements contradict each other?”
The answer reveals operational depth. A provider who troubleshoots MDM daily will describe the diagnostic process—checking policy inheritance, reviewing app manifest requirements, testing in a staged environment before pushing to production. A provider reading from a feature sheet will pivot to talking about SOTI’s capabilities rather than their own process.
What does a managed mobility services provider actually cost?
Pricing is the question every IT leader asks second—after “what do you actually do?”—and the question every MMS provider avoids answering publicly.
The range is wide because the scope varies enormously.
Published benchmarks and what drives variation
Tellennium, one of the few providers to publish pricing benchmarks, cites a range of $3 to $20+ per device per month depending on service scope and device type. That spread is not price gouging—it reflects fundamentally different service models.
At the low end, you are getting basic smartphone management: MDM licence pass-through, a help desk ticket system, and maybe some reporting. At the high end, you are getting full lifecycle management for rugged devices with hot spare pools, a certified repair depot, bilingual service desk, and telecom expense management bundled in.
The question to ask is not “what is your per-device price?” but “what is included at that price, and what costs extra?”
The hidden cost you are already paying
The more revealing cost comparison is not “MMS fee versus no MMS fee.” It is “MMS fee versus the mobility spend you cannot currently see.”
Enterprises typically overspend 10–30% on mobile carrier plans due to zero-use lines, plan misalignment, and charges that never get disputed. For a fleet of 5,000 devices averaging $40 per month per line, a 15% overrun is $360,000 per year—often recoverable within the first quarter of a managed telecom expense engagement.
In almost every new fleet onboarding, we find 8–15% of active SIM lines are either zero-use or assigned to devices sitting in a drawer. That discovery alone—before any operational improvement—typically covers several months of MMS fees.
If you want to see what your carrier invoices are actually costing you before committing to a full MMS evaluation, ClearSight TEMs AI surfaces zero-use lines and cost anomalies within minutes of invoice upload, at $99 per month per billing account. It is a zero-friction way to quantify the problem before deciding how to solve it.
The evaluation framework—seven criteria that reveal the real provider
After 20 years of managing enterprise device fleets and watching organisations evaluate MMS providers, these are the seven criteria that consistently separate the providers who deliver from the ones who disappoint.
- Operational infrastructure ownership. Ask whether staging, repair, and service desk functions are performed in-house or subcontracted. If the answer involves “partners,” ask to meet them. If you cannot meet them, you cannot vet them—and you will not know who is handling your devices until something goes wrong.
- OEM partnership tier and device-specific certification. A Premier Zebra partner has direct OEM relationships, allocation priority during supply constraints, and access to technical resources that resellers do not. Ask for the partnership tier documentation, not just a logo on a slide.
- MDM platform certification and dedicated administrator headcount. Verify which platforms the provider is certified on and how many administrators they have dedicated to MDM operations. A provider who “supports” SOTI is not the same as a provider with certified SOTI administrators actively managing client environments.
- Data residency and privacy compliance documentation. Ask where device data is processed, stored, and backed up. Ask whether the provider can produce documentation showing PIPEDA alignment, and—if you operate in Quebec or healthcare—whether they can demonstrate Law 25 or PHIPA compliance in their data handling processes.
- Bilingual service capability. For Canadian operations, ask whether the service desk is staffed with French-speaking agents 24/7 or whether French calls are routed to translation services. The difference determines whether you can serve federal, Quebec, and many healthcare contracts.
- Telecom expense management integration. Ask whether carrier invoice auditing, plan optimisation, and zero-use line identification are included in the service or treated as a separate engagement. A provider that manages devices but ignores carrier spend is leaving your largest mobility cost unmanaged.
- Secure decommissioning process with chain-of-custody proof. Ask for a sample chain-of-custody record from a previous engagement showing device intake, data erasure certification (NIST 800-88), and final disposition. If the provider cannot produce one, their lifecycle coverage ends before the finish line.
When your evaluation reveals you need more than a software vendor
If you have applied the criteria above to your shortlist, you have likely noticed a pattern: most MMS providers can check three or four boxes. Very few can check all seven—particularly the Canadian operational sovereignty, rugged device expertise, and bilingual service requirements that define whether a provider can actually serve Canadian enterprise operations.
PiiComm exists because that gap exists.
We manage 500,000+ devices across thousands of Canadian locations—not through subcontractors, but through our own staging facilities, our own certified technicians, and our own 24/7 bilingual service desk staffed in Canada. We hold Premier partnership status with Zebra Technologies, the highest tier available, because rugged device management is our heritage, not an afterthought. We are certified on SOTI and 42Gears, with dedicated MDM administrators who troubleshoot policy conflicts daily—not sales teams who demo dashboards.
Every function in our five service pillars—Strategic Sourcing, Staging & Deployment, Lifecycle Management, MDM as a Service, and Secure Decommissioning—is executed in-country by our own team. That is not a brand claim. It is an operational fact you can verify by touring our facility.
Request a mobility assessment to see how your current programme scores against these seven criteria—and where the gaps are costing you.
Frequently asked questions about managed mobility service providers
What is the difference between a managed mobility provider and an MDM vendor?
MDM is software that controls devices. MMS is a managed service that operates the entire device lifecycle—procurement, staging, repair, telecom management, and decommissioning—with MDM as one component. An MDM vendor sells you a licence. An MMS provider operates your environment.
How much do managed mobility services cost per device?
Published benchmarks range from $3 to $20+ per device per month, depending on service scope and device type. Basic smartphone management sits at the low end; full lifecycle rugged device programmes with repair depot, hot spares, and TEM sit at the high end. Always ask what is included at the quoted price.
What questions should I ask when evaluating an MMS provider?
The most revealing question is operational: “Walk me through exactly what happens when a device breaks at one of our sites on a weekend.” The specificity of the answer—who touches the device, where it goes, how long until the worker has a replacement—reveals whether the provider operates or subcontracts.
Do I need a Canadian-based managed mobility provider?
If your organisation is subject to PIPEDA, PHIPA, or Quebec Law 25, your MMS provider’s data handling location directly affects your breach notification obligations and privacy impact assessment requirements. A provider processing device data outside Canada changes your compliance posture.
Can a managed mobility provider work with my existing MDM platform?
Yes. A qualified MMS provider administers your existing MDM environment—SOTI, 42Gears, Intune, VMware, or others—rather than replacing it. The value is in certified administrators actively managing policies, compliance, and incident response, not in software substitution.
What is the difference between MMS and telecom expense management?
TEM focuses specifically on carrier invoice auditing, plan optimisation, and cost recovery. MMS encompasses TEM as one component within a broader lifecycle service that includes device procurement, staging, management, and secure decommissioning. Some MMS providers include TEM; others treat it as a separate engagement.
How long does it take to transition to a managed mobility provider?
Onboarding timelines vary by fleet size and complexity, but a typical enterprise engagement moves from contract signing to operational handover in 60–90 days. Fleet discovery and MDM migration planning consume the first 30 days, with staged device enrolment and service desk cutover following.
The evaluation that matters happens after the demo
Every MMS provider’s demo looks polished. The dashboards are clean. The slides are comprehensive. The promises are identical.
The difference becomes visible only when you ask questions the slides were not designed to answer. When you request a facility tour and watch the hesitation. When you ask for a chain-of-custody record and receive a template instead of an actual document. When you probe on French service capability and hear “we can arrange that” instead of “our service desk is staffed 24/7 in both languages.”
The seven criteria in this guide are not theoretical. They are the questions that surface the gap between the pitch and the operation—the questions that would have saved dozens of IT leaders we have spoken with from signing contracts they regretted within six months.
Your evaluation committee has the slides. Now they need the questions that reveal what the slides do not show.