ServiceNow has become the system of record for IT operations. Incidents, changes, assets, and configuration items all converge on one platform, and that consolidation is exactly what makes the remaining gaps so visible.
For most organizations, the largest of those gaps is mobile.
Want the full breakdown before you keep reading?
Explore the three tiers of mobile management in ServiceNow.
Why mobile breaks the CMDB
Unlike laptops and servers, mobile devices are not found by ServiceNow Discovery. There is no agent to scan them. Their lifecycle data lives in external systems, EMM/UEM platforms, enrollment platforms like Apple Business Manager and Knox Mobile Enrollment, telecom carrier portals, and logistics providers, and none of it synchronizes with the CMDB on its own.
The consequences are familiar to any asset manager:
- Stale CI records. A device changes carrier plan in a carrier portal, migrates between EMM tenants during an acquisition, or is retired without ever being unenrolled, and the CMDB never hears about it.
- Orphaned service lines that keep billing against devices that left the fleet months ago.
- Manual spreadsheet reconciliation that consumes mobility and asset teams every audit cycle.
- Compliance exposure at precisely the moment the CMDB is supposed to be trusted: audit, offboarding, lost and stolen events.
The blind spot isn't a tooling failure. It's structural. And ServiceNow offers three distinct tiers of response to it.
Three tiers, one platform
Our new white paper, Managing Mobile Devices in ServiceNow: From Basic Tracking to Full Lifecycle Automation, evaluates all three, not as competing products, but as a cumulative maturity progression:
The Three Tiers of Mobile Management in ServiceNow
Includes
Builds on
Each tier builds on the one below it.
Tier 1: Base Asset Management. Included with every ITSM license. Devices can be recorded as assets, but there's no CI class specific to mobile, no EMM or carrier connectivity, and every lifecycle state change is manual. Right for very small, stable fleets.
Tier 2: HAM Pro. ServiceNow's module built for hardware asset management adds normalized models, prescriptive request-to-retire flows, the mobile CI class, and Service Graph Connectors that sync EMM data into the CMDB. A strong home for most midmarket fleets, but its connectors sync data; they don't orchestrate enrollment, carrier operations, or logistics. That connectivity is a substantial engineering effort to build and maintain yourself.
Tier 3: Samsung SDS Zero Touch Mobility (ZTM) for ServiceNow®. A certified ServiceNow Store application built natively on the Now Platform, ZTM is the orchestration layer for mobile. Where HAM Pro tracks hardware as records, ZTM acts on the fleet: it provisions, enrolls, migrates, locates, reclaims, and reconciles, turning the CMDB from a system of record into a system of execution for enterprise mobility. Every ZTM subscription includes a HAM for ZTM entitlement, so the incremental investment goes toward the mobile automation layer rather than a second license plus custom development.
How to choose, without guessing
Device count is the number everyone reaches for first, but it's rarely the whole answer. Operational complexity is the stronger signal: fleet churn, the number of EMM platforms and carriers in play, geographic footprint, and how much daily operations depend on devices being provisioned and reconciled correctly.
The white paper turns that into a working evaluation: a 16-point capability comparison across all three tiers, a decision framework built on those operational factors, a practical scalability test for keeping implementation cost aligned with software investment, and end-to-end use cases, including new-hire provisioning that compresses days of coordination across multiple portals into one automated run.
It also answers the questions platform owners ask before any Store app is admitted: scoped application, Store-delivered updates certified against current family releases, data residency inside your own instance, and connectors maintained by Samsung SDS as vendor APIs evolve.
The question that actually matters
The test is not whether mobile data reaches the CMDB. It's whether it arrives as clean, correctly classified, reconciled asset records.
That distinction is the difference between an inventory that is audit-ready and one that needs manual remediation before anyone can trust it.
If your organization runs a substantial mobile fleet, or if mobile is becoming operationally critical faster than your tooling can keep up, the white paper gives you the framework to decide which tier fits and when it makes sense to move up.
Read the full comparison
Managing Mobile Devices in ServiceNow: From Basic Tracking to Full Lifecycle Automation is a technical evaluation for platform owners and IT asset managers.
