Skip to content

Use cases

Network intelligence your whole organization can act on

Telemetry source

On-device · per subscriber

Latency

< 60 seconds, end-to-end

Coverage

5G NR · LTE · UMTS

Deployment

SDK · operator-tailored · remote-tunable

10 / 10 Shown

The most expensive support ticket is the one generated on day one. A new subscriber inserts the SIM, the network registers it, and the device still lands on a wrong APN, an unregistered IMS, or data that never comes up. The subscriber blames the operator, and the first interaction with the brand is a support call.

SDKCX eliminates that call. Running inside the carrier app with Carrier Privileges, it reads the real configuration state of the device the moment the SIM goes active, compares it against the operator's correct profile, and applies the fix directly. The correction engine is deterministic — same input, same output, fully auditable — and the same validation runs continuously, so configurations that break later, after OS updates, device swaps or roaming events, are corrected the same way.

Across production deployments, OCTOCX has executed over 3 million device diagnoses, with 1 in 3 devices receiving an automatic configuration correction — and operators reporting support ticket reductions of up to 30%.

Relevant teams:
Customer Experience · L1 Support · Network Engineering
Key signals:
configuration correction rate · time-to-first-connection · first-boot QoE · ticket deflection rate · corrections per device lifecycle

When a degradation is reported, the first question is always the same: is it the network, the config, or the device? OCTOCX answers it in seconds.

Every active device streams signal, IMS and bearer state continuously. When an alert fires, NOC teams drill from fleet view to a single IMSI in two clicks — with the full session timeline, RAN events, and configuration state at the moment of the incident.

No more "we can't reproduce it." The evidence is already there.

Relevant teams:
NOC · Network Engineering · L1/L2 Support
Key signals:
RSRP · SINR · IMS state · handover events · bearer drops

By the time a subscriber calls to cancel, the network problem that drove them there is weeks old. OCTOCX closes that gap.

Individual device QoS profiles are built continuously — signal quality, data experience, voice reliability — and correlated with actual churn events. The result is a predictive model grounded in real network experience, not survey data.

CX teams get a ranked list of at-risk subscribers with the specific network condition driving the risk — so intervention is targeted, not generic.

Relevant teams:
Customer Experience · VP Commercial · CX Lead
Key signals:
QoS profile trends · NPS correlation · geographic experience gaps · device-level churn index

Detecting an at-risk subscriber is only half the job. Acting on it, at the right moment and through the right channel, is where revenue is retained or created.

REMOTECX turns the operator's installed base into a direct engagement channel. Segments are built from real device context: plan usage, device capability, geography, experience quality. Campaigns for renewals, upsells, plan migrations or win-back reach the subscriber on the device, and remote tasks execute through Carrier Privileges without requiring the subscriber to do anything.

Combined with Churn Prevention, the loop closes: risk is detected, the intervention is targeted, and the outcome is measured per campaign.

Relevant teams:
Commercial · Marketing · Customer Experience
Key signals:
campaign conversion rate · segment reach · lifecycle stage per subscriber · retention delta per intervention

An eSIM can provision perfectly in the platform and still fail on the device.

A successful download is not a successful connection. The profile installs, the platform reports success, and the subscriber still lands on the wrong APN, an unregistered IMS, or dead data on first boot. The provisioning layer never sees it, because from the platform side everything worked.

OCTOCX measures the first session from inside the carrier app the moment the eSIM goes live. If the configuration is wrong, it is corrected in the background before the subscriber notices. Every activation is confirmed against real device state, so onboarding and commercial teams know connection succeeded, not just that the profile shipped.

Relevant teams:
Customer Experience · Network Engineering · Commercial
Key signals:
first-session QoE · APN state · IMS registration · activation confirmation rate · time-to-first-connection

IMS migrations are high-risk. A 3% regression in VoLTE registration across a large cohort is invisible in core infrastructure KPIs — but shows up immediately in device telemetry.

OCTOCX captures VoLTE and VoWiFi registration success rates per device cohort before and after the migration cutover. Degradation zones are detected geographically within hours. If a cohort crosses a threshold, an alert fires before the first NPS drop is registered.

Pre/post deltas are exportable for engineering review and regulatory reporting.

Relevant teams:
Network Engineering · NOC · Regulatory
Key signals:
VoLTE registration rate · IMS failure codes · geographic degradation zones · cohort deltas

Fraudulent SIM activations are designed to look like normal onboarding. They are invisible to infrastructure monitoring because the infrastructure sees a valid SIM, a valid activation, and a valid signal.

Device-level telemetry sees something different: the same device fingerprint activating multiple SIMs in a short time window, in the same location, none of them subsequently used for data or voice.

In a production deployment, this pattern exposed a sales team member reporting fraudulent new subscriber activations at scale. The anomaly was only visible because OCTOCX tracks at the device, not at the SIM.

Relevant teams:
Revenue Assurance · Compliance · Operations
Key signals:
device fingerprint clustering · activation density · SIM usage post-activation · spatial correlation

Enablers and MVNEs operate many brands on shared infrastructure, but each brand's subscribers live on different SIM profiles with different configurations. Building and maintaining an app per brand is not viable.

OCTOCX solves this at the SIM layer. A single application, signed once through Carrier Privileges, is authorized across the SIM profiles of every brand the enabler serves. On first boot, SDKCX reads the SIM and applies the correct configuration for that brand automatically. New brands are onboarded by signing their SIM profiles, not by shipping new software.

The enabler gains fleet-wide observability with per-brand segmentation, and each brand gets auto-configuration and support visibility without owning any code.

Relevant teams:
MVNE Operations · Product · Commercial
Key signals:
per-brand device fleet · SIM profile detection · configuration success rate per brand · cross-brand benchmarks

Regulators increasingly require operators to prove network quality of service with subscriber-level evidence — not aggregate infrastructure metrics.

OCTOCX generates reports from actual device measurements: signal quality, data throughput, voice reliability and coverage — per subscriber, per geography, per reporting period. The data is collected passively and continuously, so no additional test infrastructure is needed.

Reports are exportable in structured formats ready for submission. Every measurement carries device context, timestamp and location for full auditability.

Relevant teams:
Regulatory · Legal · Network Engineering
Key signals:
device-measured QoS · coverage by geography · SLA compliance rate · audit trail per measurement

Traditional capacity planning relies on infrastructure utilization metrics — which only tell you what the network is handling, not what the subscriber is experiencing.

OCTOCX adds the missing layer: real throughput, latency and congestion signals from the devices in each cell and geography. Areas where infrastructure looks healthy but subscriber experience is degrading surface before they generate complaints.

Equally important — underutilized areas with good device experience are identified and fed back to commercial teams as growth opportunities, closing the loop between network operations and sales strategy.

Relevant teams:
Network Engineering · Commercial · Operations
Key signals:
per-cell device throughput · congestion hotspots · utilization vs experience delta · geographic growth zones

See your network through the device.

Book a 30-minute demo. We'll show you OCTOCX on a real operator fleet.