Telecom analytics dashboard: revenue, churn and usage

A telecom analytics dashboard compares service revenue, subscriber churn, and usage across commercial segments. Its first check is whether the subscriber movements explain the closing base. Its next job is showing whether a change came from subscriber volume, revenue per connection, or a different mix of plans and customers.

Start with one population and one reporting month

This is a commercial dashboard for an illustrative US mobile provider, not a network-monitoring display. The unit is an active billable connection, the reporting period is September 2026, and service revenue excludes equipment sales and taxes collected for others. Usage means billed mobile data in gigabytes for those same connections.

Specify the unit beside every measure. Verizon's 2024 annual report distinguishes accounts from connections and defines wireless churn using disconnections divided by average connections. Its revenue-per-account measure uses accounts instead. That distinction matters even when your own provider uses different commercial definitions.

Use the existing B2B telecom sales review questions for the broader commercial meeting. Keep detailed retention investigation on the separate telecom churn analytics page; this dashboard should reveal where that investigation is needed.

Build the input table from business exports

Bring opening and closing subscriber snapshots, activation and disconnection records, and earned service revenue and usage for the month. Aggregate billing lines to the connection and period before joining them to the subscriber register. A connection with several charge lines must still count once.

For this example, freeze plan, region, and tenure assignments at the opening cutoff. New additions enter the Recent group. Established means more than twelve months of tenure at that cutoff; Recent means the remaining connections. There are no plan migrations or regional transfers in this example. A live report needs separate bridge adjustments for those movements.

These are the complete illustrative input totals. Additions and disconnections are gross movements, and revenue is after service credits.

Compute the dashboard measures

Put the table in A:H, headers in row 1 and input rows in rows 2:9. Calculate closing connections in I2 and the average base in J2, then fill down:

=D2+E2-F2
=(D2+I2)/2

The opening-and-closing average is a transparent approximation for this example. If activation timing is uneven, use average daily active connections from the subscriber records consistently across all slices. Do not silently switch denominator methods between plans.

Monthly churn = Disconnections / Average active connections

Service revenue per connection = Monthly service revenue / Average active connections

Usage per connection = Monthly billed GB / Average active connections

For a plan name in L2, these formulas return that plan's revenue, average base, and disconnections:

=SUMIFS($G$2:$G$9,$A$2:$A$9,L2)
=SUMIFS($J$2:$J$9,$A$2:$A$9,L2)
=SUMIFS($F$2:$F$9,$A$2:$A$9,L2)

Microsoft's SUMIFS documentation explains how criteria select the rows being summed. Add a region or cohort criteria pair when comparing equivalent groups. Covirage is not affiliated with Microsoft or Verizon.

The table below shows alternative cuts of the same population. Do not add plan, region, and cohort subtotals together: each pair already covers the whole business. Monetary ratios and percentages are rounded to two decimals after calculation.

Reconcile before interpreting the picture

The subscriber bridge is 1,000 opening connections plus 80 additions minus 30 disconnections, giving 1,050 closing connections. Net additions are therefore 50. The average of 1,000 and 1,050 is 1,025, matching the summed slice averages.

Revenue also ties: $24,560 from Basic plus $24,660 from Plus equals $49,220. The whole-business revenue-per-connection figure is $49,220 / 1,025 = $48.02. Total churn is 30 / 1,025 = 2.93%; calculate it from totals rather than averaging displayed percentages.

Basic usage totals 12,280 GB, or 20.00 GB per average connection. Plus totals 20,550 GB, or 50.00 GB per average connection. Together they give 32,830 / 1,025 = 32.03 GB per connection. These usage averages describe the billed population; they do not establish service quality or profitability.

The Recent cohort's higher churn warrants checking its individual disconnections and activation histories. The East region's higher revenue per connection requires a plan-mix check before anyone attributes it to better pricing. The telecom customer analytics view supports the relationship review, while telecom marketing analytics handles acquisition questions.

Change one revenue input

Suppose a billing correction changes only Basic, West, Recent service revenue from $4,300 to $4,730. Subscriber movements and usage stay as recorded. This isolates a revenue change from volume and churn.

The company ratio rises by $430 / 1,025 = $0.42 per connection, rounded. The correction changes revenue without changing retention. Record the reason and period so the dashboard's explanation matches the corrected ledger.

Where it goes wrong

• Accounts mixed with connections. A multi-line account makes the two denominators materially different.
• Migrations recorded as churn. Moving between plans should not create a company-level disconnection unless service actually ends under your stated policy.
• Unequal exposure hidden by averages. Compare matching periods and use a consistent daily or opening-and-closing base.
• Billing periods mixed with usage periods. Late credits or delayed usage records need an explicit cutoff treatment.
• Aggregate differences treated as causes. Region, cohort, and plan mix can explain an apparent performance gap without a pricing or service change.

Review your commercial export in Covirage

Bring a prepared connection-period file containing subscriber movements, plan and cohort assignments, service revenue, and usage. Covirage maps the columns; its tools compute and check the comparisons, and the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.

See Covirage for telecom for the supporting industry context.