Network experience monitoring: from cell metrics to customer impact

Context

The operator is proud of network KPIs: 99.7% availability, 0.3% session failure rate. But NPS in the network is worse than at a competitor with worse cell-level metrics. Network team frustrated: “everything is working”.

CMO/CTO joint task force for reconciliation.

Diagnostic (5 weeks)

The audit showed:

• Network KPIs measured at cell level. Customer impact — not measured at all.
• 99.7% availability — average. In specific hot-spots reality is 90-92%.
• Incidents restored in 45 minutes average — but customers in the zone are without communication.
• No link from network NMS → customer-facing notification.
• Customer service has no access to live network status — speak blindly.

Root insight: technical excellence does not translate into customer perception without a translation layer.

Approach (10 months)

Months 1-3. Customer impact metrics. Each cell mapped to customer count in the zone. Incident severity scored on customer impact, not technical impact.

Months 3-5. Geofence-based alert pipeline. Network event → notification fabric → push/SMS to customers in the affected zone.

Months 5-7. Customer service integration. Live network dashboard in the contact centre. The operator on a call sees “this customer is in an incident zone, ETA 30 minutes”.

Months 7-10. Compensation automation. Significant outage (>2 hours) auto-triggers compensation (1GB free) for affected customers. No manual approval of each case.

In parallel — customer feedback loop: post-incident NPS survey, results back to network team.

Results

After 10 months:

• Inbound calls after incident: −40% (alert preempts).
• Post-incident NPS: +18 points.
• Customer perception of network reliability: +14 points (despite the same cell-level KPIs).
• Compensation cost: $300k annually (a fraction of the losses that previously came via churn).
• Network team morale: improved — visibility clearly shows customer value.

What is critical

CMO+CTO joint sponsorship. Without cross-functional alignment each team blames the other.

Customer-impact KPI redefinition. Cell-level KPIs stay, but customer-impact dominates dashboards.

Compensation automation. Manual approval — slow and inconsistent.

Customer service integration. Without live status — operators say “I don’t know” = trust destroyed.

What would not have worked

Notification without compensation. “We know we have a problem but do nothing” — worse than silence.

Compensation for every minor incident. Cost balloons, perceived value drops.

Cell-level KPIs replaced entirely. Network team needs operational metrics for troubleshooting.

How SamaraliSoft engages

An engagement of this class — 9-12 months. Diagnostic 4-6 weeks, design 6-8 weeks, phased implementation.

Related

• /en/solutions/telecom-network-experience-platform/ — network experience
• /en/use-cases/telecom-network-anomaly-customer-alert/ — alert use case
• /en/architecture/telecom-observability-stack/ — observability
• /en/insights/telecom-customer-trust/ — trust