OCTOCX delivers the
ultimate telecom CX.

OCTOCX captures on-device telemetry from Android phones, modems and IoT modules across 5G NR, LTE, UMTS and GSM. Coverage spans both consumer and enterprise fleets.

OCTOCX runs alongside infrastructure monitoring, not in place of it. We export to Grafana, Prometheus, Splunk and Snowflake via standard connectors, and push events into ticketing (ServiceNow, Jira) and BSS workflows over REST and Kafka. Your engineers keep their existing dashboards — we add the device layer they were missing.

Probe-based tools measure performance from fixed locations. Crowdsourced platforms rely on voluntary user-initiated tests. OCTOCX operates as an operator-controlled agent embedded inside your subscriber app, capturing continuous session-level data from every active device across your entire fleet, under your governance. The result is complete coverage, not sampled coverage, with the ability to act on what is detected. The deeper difference is access. OCTOCX operates through Carrier Privileges, a signed authorization that lets the operator's own agent read and correct network configuration directly on the device. Probe-based and crowdsourced tools never reach this layer. They can observe from the outside but cannot act on the device itself.

Yes. Correction runs through Carrier Privileges, which grants the operator's agent the authority to validate and rewrite APN, VoLTE, VoWiFi, roaming and preferred-network settings against the operator profile. Because this authorization sits at the device level, fixes apply silently in the background with no app update, no support call and no truck roll.

Carrier Privileges is a device-level authorization that grants the operator's embedded agent permission to read and modify network configuration without user action or an app update. It is the foundation that makes silent correction possible. No external probe or crowdsourced platform can access this layer, which is why OCTOCX can act on what it detects rather than only report it.

Trigger remote speed tests, run latency and jitter sessions, push APN/VoLTE/roaming corrections, schedule a test call (AutoCall) or run a full remote diagnostic. Every task is logged with full traceability for audit and compliance.

DEVICECX is one platform with two surfaces. Engineers get session-level device state, RAN event search and IMS migration validation. Commercial teams get aggregated KPIs and KQIs, NPS-to-network correlation, churn risk by device and ARPU exposure per degradation zone — all from the same source of truth.

OCTOCX never captures communication content — no call audio, no message bodies, no browsing data. Sensitive identifiers and location coordinates are encrypted or anonymized per deployment policy. Only network-layer signals (RSRP, MOS, throughput, IMS state, etc.) and device profile fields are kept.

The SDK samples every 5–10 seconds (configurable) and batches uploads to minimize radio wake-ups. Typical overhead is under 0.5% daily battery and under 2 MB/month of data per device. No background work runs while the operator app is closed.

A single-market pilot typically goes live in 4 to 6 weeks covering SDK integration, dashboard configuration and cohort rollout. Multi-market expansion follows once pilot KPIs are validated.

Data is stored in the region of your choice — EU (Frankfurt or Madrid), US East, or on-premises inside your operator infrastructure. The platform is GDPR-compliant by design: no communication content captured, identifiers pseudonymized per deployment policy, and a DPO sign-off is part of every enterprise contract. OCTOCX is ISO 27001 certified.

Raw device-level telemetry is retained for 90 days by default. Aggregated KPI and KQI data is retained indefinitely. Custom retention policies are available for enterprise customers.