Every operator already knows their ARPU number. What’s harder to see is how much of it sits untapped on the network from subscribers whose devices were never set up to deliver data through proper device OTA configuration. That gap isn’t a subscriber problem. It’s a configuration problem, and it’s fixable.
Acquiring new subscribers is expensive; growing ARPU for telecom operators from the existing base is often the most efficient path to data ARPU growth — and when certain devices on the network aren’t recognised accurately, that growth path takes a direct hit. That’s exactly why unconfigured, invisible devices are such a costly blind spot.
A Mixed Device Landscape Across Regions
No two markets look the same when it comes to device mix. Mature markets skew heavily toward smartphones, while emerging and price-sensitive markets carry a much larger share of feature phones and unbranded phones. Almost everywhere, though, feature phones remain a constant — a lower-cost segment that never fully disappears, even as smartphone adoption grows.
This mix matters because each device type interacts with the network differently: some support OTA configuration, some need guided manual setup, and some carry null or false IMEIs that make identification difficult from the start. If configuration efforts focus only on mainstream smartphones, a meaningful chunk of the subscriber base—often including a large feature phone segment and unbranded devices in telecom networks—is left behind.
That’s a problem because every correctly configured device can use data and other services the operator already offers to generate revenue. Addressing configuration across the entire device mix, not just the easy majority, is what turns a fragmented subscriber base into a fully monetisable one.
Where Most ADMS Platforms Fall Short
Most operators already deploy an Automatic Device Management System (ADMS), also referred to as ADM, and often called the operator’s OTA provisioning platform for OTA device management. These terms describe the same network solution and are used interchangeably throughout. In principle, this is exactly the right idea for enabling subscribers on data: detect the device connecting to the network, look up its make and model, and automatically provide APN auto-configuration and other correct settings — no manual entry, no support call, no friction for the subscriber.
In practice, most ADMS platforms in the market today work well only for one segment of the device population: known devices. They’re built around IMEI detection. For branded smartphones, this approach works well and scales easily across the network.
Unbranded handset manufacturers skip IMEI registration to avoid the cost, resulting in null IMEI or false IMEI devices.
- Null IMEI devices: The device reports no IMEI at all.
- False IMEI devices: The device reports an IMEI cloned from another phone. Faced with this, most ADMS platforms in the market fall back to one of two outcomes, neither of which actually solves the problem
- No configuration at all: The device isn’t recognised, so no settings are pushed, or often just a bare APN name is sent, and the subscriber is left to configure manually, which most never do.
- A generic, blanket configuration: A generic OTA setting is pushed across to unidentified or unbranded devices, regardless of their actual make or model. This approach carries very low accuracy.
The Invisible Subscriber Problem
Every operator has them: subscribers connecting to the network on devices the ADMS can’t identify. These aren’t churned-out subscribers or inactive SIMs — they’re active, paying subscribers sitting on the network with a device that was never properly set up. And because a poor customer experience is one of the most common and hardest-to-diagnose drivers of early churn, this invisible segment doesn’t just sit quietly under monetised; it steadily leaks away, often without the operator ever identifying misconfiguration/no configuration as the root cause. (write in pointers)
This is precisely the gap that most ADMS platforms in the market were never designed to close.
Devicemax ADMS: Built for Complete Device Coverage
This is where Devicemax ADMS differs. Where most platforms in the market stop at IMEI-based detection and fall back to generic settings for anything outside that, Devicemax ADMS is designed around the assumption that a meaningful share of any operator’s subscriber base will include devices that don’t identify themselves, and builds specific capability to reach them, rather than treating them as an edge case.
A few things set it apart from typical ADMS deployments:
| Aspect | Other ADMS Platforms | Devicemax ADMS |
|---|---|---|
| Detection method | Relies solely on IMEI-based lookup | Backed by Netra’s pattern-based recognition engine. |
| Unbranded / grey market devices | Treated as an edge case or left unconfigured | Supports unidentifiable devices as they are a meaningful part of the base |
| Null / false IMEI handling | No configuration, or falls back to a generic setting | Identified using Netra with up to 90% accuracy |
| Configuration accuracy for unidentified devices | Low — generic, blanket APN settings pushed regardless of actual device model | High — model-specific configuration once the device is resolved |
| Impact on ARPU | Leaves a segment of subscribers invisible and under-monetized | Converts previously unconfigured subscribers into active ARPU contributors |
How does Devicemax ADMS configure unidentified devices?
One of the core features of Devicemax ADMS is Netra, a specialised device recognition engine purpose-built for devices that can’t be identified through IMEI-based lookups. Netra identifies null-IMEI and false-IMEI devices, including unbranded and unrecognised handsets, with up to 90% accuracy. Once a device is recognised, it remembers that identity, so the next time it latches onto the network, Devicemax ADMS can configure it in real time.
Why This Matters
Unbranded devices don’t just generate support tickets — they quietly erode ARPU, often without operators realising it.
A subscriber whose device never gets the correct internet settings underuses data or churns to a competitor after a frustrating first-week experience. Multiply a few percentage points of unconfigured or misconfigured devices by a large subscriber base, and the lost data revenue adds up quickly. Faster, accurate configuration is directly tied to higher data usage and service adoption, which is exactly why device detection and configuration sits so close to the ARPU line on an operator’s dashboard, not just the OPEX line.
The catch is that most ADMS platforms assume every device has a traceable IMEI. Unbranded handsets break that assumption — which is precisely the gap Devicemax ADMS, with Netra as one of its core capabilities, was built to close.
The Bottom Line for Operators
Unbranded devices aren’t going away — in many markets, they represent a considerable share of the active subscriber base. Operators running a device management platform that only handles known devices are leaving data revenue, service adoption, and customer experience on the table.
Devicemax ADMS is built to go further: full-spectrum device detection, pattern-based recognition through Netra for devices standard lookups miss, automatic OTA device management wherever possible, and guided self-service for the rest—all backed by over a decade of specialised expertise in device identification and OTA delivery.
Wherever this situation exists in your subscriber base — null IMEIs, false IMEIs, or unbranded handsets — Devicemax ADMS is a platform built specifically to reach it.
