If your organization runs one of the major EMM platforms, device policy and enrollment are probably under control. The EMM does what it was designed to do. But if you've ever chased a carrier to suspend a service line after an offboarding, manually reconciled a device inventory because your asset records didn't match what the carrier showed, or watched a lost-device report turn into a four-team coordination exercise, that's not your EMM failing. That's the gap around your EMM. And it's the gap this article is about.
Wondering whether your mobility challenges stem from your EMM or the processes surrounding it?
What your EMM does well
Let's start here, because the argument that follows only makes sense if we're clear about what's working.
Your EMM is genuinely excellent at what it was built for. Once a device is enrolled, it enforces security policies, pushes applications, remotely locks or wipes the device, and provides visibility into compliance status. Modern platforms like Intune, Jamf, and Workspace ONE also handle zero-touch enrollment well when paired with Apple Business Manager, Google Zero Touch, or Knox Mobile Enrollment. Devices power on, auto-enroll, and arrive ready to use. For corporate-owned device policy, this is mature, reliable technology.
So if your EMM is working, what's the problem?
The lifecycle doesn't start with the EMM
Before a device reaches your EMM, someone had to order it. That means interacting with a carrier: selecting a device from a product catalog, choosing a rate plan, activating a service line, arranging delivery. Carrier product catalogs change constantly, with new models, revised pricing, and updated plans. Most organizations manage this through carrier portals that are completely separate from the EMM and the asset management system.
The result is a structural gap between procurement and enrollment. Devices arrive without carrier data attached. Service lines are activated in carrier systems your CMDB can't see. Someone reconciles a spreadsheet to figure out which device belongs to which service line, usually quarterly, and usually imperfectly.
This isn't a failure of your EMM. It's a gap the EMM was never designed to close.
The lifecycle doesn't end with the EMM either
When a lifecycle event happens, such as a lost device, an employee offboarding, or a hardware refresh, your EMM handles its part. It wipes the device. It unenrolls it. But here's what it doesn't do:
| × |
Suspend or terminate the carrier service line. That's a separate action in a carrier portal, done by a different person, often days later, or not at all. |
| × |
Generate a return shipping label or coordinate logistics with the warehouse. The device physically moving back to IT is entirely outside the EMM's scope. |
| × |
Update the asset record in your ITSM platform with the outcome of the lifecycle event. The EMM and the asset system don't share a record. |
| × |
Capture residual device value at end of life or route the device to a buyback vendor. |
| × |
Keep your CMDB current when the carrier activates or terminates a service line outside your normal processes. |
"Active service lines on decommissioned devices. Asset records that don't match the carrier inventory. These aren't data quality problems. They're the natural result of systems that were never designed to stay in sync."
What this costs in practice
The gap between your EMM and the systems around it shows up in a few very specific places:
Provisioning delays. A new hire's device has to be ordered through the carrier, shipped to a central location, manually enrolled in the EMM, then shipped again. Because each step requires a human handoff between systems, a process that could take 24 hours routinely takes 10 days. The new hire works from a personal device and IT fields the escalation.
Zombie service lines. A device is wiped and unenrolled in the EMM when an employee leaves. The carrier service line stays active because suspending it requires a separate action in the carrier portal, and in the chaos of offboarding, it gets missed. Industry data consistently shows that 5–15% of active carrier lines in enterprise accounts are attached to devices that are no longer in use.
Lost-device incidents that require four people. A user reports a missing phone. IT needs to trigger a remote wipe in the EMM, contact the carrier to suspend the line, initiate a replacement order, and update the asset record. Four separate actions, four separate systems, coordinated by a team that has thirty other things to do that day.
📋 Is your EMM covering your full lifecycle?
A short five-minute assessment helps mobility teams identify exactly where their lifecycle breaks down and what it's costing them in time, money, and compliance risk.
The gap has a name: it's an orchestration problem
The missing piece isn't a better EMM. Modern EMM platforms are already very good. What's missing is a layer that connects your EMM to the systems around it, including carrier portals, logistics vendors, asset management, and ITSM. That way, a lifecycle event in one system triggers the right actions in all the others automatically.
This is what a mobile lifecycle orchestration layer does:
When a new hire is onboarded, it orders the device from the carrier, tracks the shipment, triggers enrollment via the EMM when the device powers on, and creates the asset record, all from one initiated action rather than four manual ones.
When an employee leaves, it triggers the EMM unenrollment, suspends the carrier service line, generates a return shipping label, and closes the asset record simultaneously. Not sequentially, not by four different people, and not with one step forgotten.
When a user reports a lost device, it guides them through locate-and-ring first, because most lost devices are just misplaced, and only escalates to lock, wipe, carrier suspension, and replacement order if recovery fails. One workflow, one record, no coordination required.
What this looks like with Zero Touch Mobility
Zero Touch Mobility (ZTM) from Samsung SDS is built specifically for this orchestration layer. It connects to your existing EMM, including Intune, Jamf, Workspace ONE, Knox Manage, and others, without replacing it. Your EMM keeps doing what it does well. ZTM handles the coordination around it: carrier operations, logistics, asset record management, and the end-to-end workflows that span all of them.
ZTM integrates directly with AT&T, Verizon, and Rogers for carrier MACD operations, including activating lines, suspending service, and terminating contracts, from inside the same system that manages the EMM enrollment. It imports the carrier product catalog automatically so device orders always reflect current pricing. It reconciles carrier inventory against your asset records continuously, surfacing orphaned lines and ghost devices as trackable tasks rather than quarterly surprises.
The result isn't a replacement for your EMM investment. It's the layer that makes that investment go further by connecting the moment of policy enforcement to the moment of procurement, the moment of offboarding to the moment of line termination, and the moment of asset retirement to the moment of value recovery.
ZTM is recognized in the 2025 Gartner Market Guide for Managed Mobility Services, and has received multiple ServiceNow Partner of the Year awards. It operates across 90+ countries and is deployed in enterprises across financial services, logistics, healthcare, retail, and the public sector.
Curious what the gap looks like in your operation?
We're not going to pitch you a platform you didn't come looking for. But if any of this sounds familiar, it's worth a conversation. Tell us about your current EMM setup and fleet size and we'll give you an honest view of where the gaps typically appear, and whether they're worth addressing now.
No commitment required. If you're not ready to talk, the platform overview gives you everything you need.
