Wireless Dealer KPIs: Metrics Beyond Activations

Wireless dealer KPIs should answer more than how many lines a store activated. They should show whether transactions were completed, where errors occurred, whether customers returned for refills, and how consistently each location performed.

That distinction matters for prepaid dealers and multi-location retailers. A store can report high activation volume while pending transactions remain unresolved or support demand increases. A smaller store may produce fewer activations but complete them more reliably and generate stronger repeat activity.

The goal is not to track every available data point. It is to create a practical view of output, transaction quality, customer activity, payout visibility, and location performance.

 Why activations are not enough

Activations are an important output metric, but they do not explain the quality of the underlying work. A total activation count cannot tell an owner whether a transaction completed on the first attempt, remained pending, required support, or led to a later refill.

It also creates a weak comparison between locations. Two stores with the same number of activation attempts may have different staffing levels, operating hours, customer mix, and error patterns. Comparing volume without that context can lead to the wrong operational decision.

A useful report connects each result to a management question:

• Did the transaction reach a completed status?
• Where did the process slow down or fail?
• Did the original activation lead to additional service activity?
• Which store or service needs attention this week?

Completed versus pending transactions

The first rule for prepaid dealer reporting is to keep transaction statuses separate. Do not combine completed, pending, failed, or rejected activity into one activation total.

Use the statuses available in the applicable reporting system and define them clearly:

Initiated → Completed / Pending / Failed

Then calculate:

• Activation completion rate = completed activations ÷ initiated activations
• Pending transaction rate = pending transactions ÷ initiated transactions
• Transaction error rate = failed or rejected transactions ÷ initiated transactions

For example, a store that starts 100 activations, completes 82, has 10 pending, and records 8 failed transactions should report 82% completed, 10% pending, and 8% failed. Pending work is unresolved; it should not be counted as completed output or treated as an automatic failure.

Add an aging view when the system supports it. Same-day pending work and older unresolved transactions require different follow-up. Use one consistent date rule—initiation date, final-status date, or a documented cohort method—so late completions do not distort two reporting periods.

Wireless dealer KPIs by store and service

Each KPI should be available by location and service. That lets a dealer compare like with like instead of relying on one company-wide average.

The 10 metrics that matter
 

Keep the denominator consistent. If a service has different eligibility or completion rules, define it separately instead of forcing every transaction into the same calculation.

Errors, attach rates, refills, and support cases

These four measures add context to activation volume.

Errors. Group errors by the step that failed, such as payment, eligibility, customer information, provisioning, or system access. The category points to the next action: clarify the process, coach the team, update instructions, or request partner support.

Attach rates. Define the eligible base before measuring the rate. An attach can be an additional product or service connected to the primary transaction. Review the result by store and category so a strong overall rate does not hide a weak location.

Refills. Measure refills against the right customer group. A refill during the activation week is different from a refill 30 days later. If active-line data is available, use customers with at least one refill divided by eligible active customers. If it is not available, report refill transactions per 100 completed activations and compare consistent cohorts.

Support cases. Track support cases per 100 transactions and, when possible, resolution time. Separate routine questions from transaction-blocking cases. Repeated cases by store or service usually deserve a workflow review.

Measure each store in context

Filter the dashboard by three dimensions:

• Location: store, region, or dealer account
• Service: activation, refill, financing, or another supported category
• Period: day, week, month, or activation cohort

Normalize comparisons using open days, operating hours, or staff hours when those fields are reliable. A store that operated three days should not be compared directly with one that operated six days.

If a dealer also uses financing, keep it separate from activation reporting. Track applications, approvals, financed transactions, and time to approval as a distinct service line. CTI’s finance partners and payment solutions page describes flexible payment options, approvals, integrations, and staff workflow support. Those measures should complement the wireless dashboard, not be mixed into activation totals.

Build a wireless dealer KPI dashboard

A useful dashboard should make the next action visible. Use one row for each store and review period, with filters for service, carrier, and transaction status.

Keep three rules visible:

1. Status definitions: document what initiated, completed, pending, failed, and cancelled mean.
2. Denominator rules: state whether each rate uses all transactions, eligible transactions, or a cohort.
3. Action ownership: show who reviews the exception and when the result will be checked again.

Do not merge activations, refills, and other services into one total. Their timelines and completion rules can differ. Separate service lines make the report easier to interpret and keep the review focused.

If your team needs help connecting transaction activity with location-level follow-up, ask CTI about dealer reporting and support.

How to run a weekly KPI review

A weekly review should lead to a decision, not another spreadsheet. Use the same cutoff and sequence every week:

1. Validate the data. Confirm the same reporting period, time zone, and status definitions for every location.
2. Review output and exceptions. Check completed activations, pending transactions, errors, completion time, and support cases.
3. Review customer activity. Compare refills, attach rates, and service mix with the location’s activation volume.
4. Check payout visibility. Confirm that eligible activity has a recorded status for the current reporting period.
5. Assign one action. Name the owner, define the corrective step, and set the next review date.

For low-volume locations, review the count beside the percentage. One transaction can create a large rate and should not trigger a conclusion by itself.

Owners, thresholds, and corrective actions

Use the first four to six weeks to establish a baseline for each store and service. Internal baselines are more useful than generic benchmarks because operating hours, staffing, customer mix, and service availability differ by location.

Use a simple control system:

• Green: within the normal baseline
• Amber: approximately 10% worse than the four-week baseline or one repeat exception
• Red: approximately 20% worse than baseline, two consecutive review periods, or a blocked high-priority workflow

At the next meeting, record whether the action improved the metric, produced no change, or requires escalation.

Align the reporting process with CTI’s dealer model

CTI’s wireless programs for retailers and distribution partners are designed for businesses adding wireless, connectivity, and payment services through carrier relationships, distribution support, account management, onboarding, and ongoing operational assistance. That makes store, service, and support visibility relevant to the dealer conversation.

The reporting fields available to a dealer can vary by program and transaction type. Do not assume that every location or service uses the same status structure. Before building the final dashboard, confirm:

• Which transaction statuses can be reported
• Whether activity can be separated by location and service
• How refills, support cases, and payout status are recorded
• Which team owns transaction questions and escalations
• Whether finance activity should be reviewed in a separate report

Because reporting fields can vary, confirm the fields available for your dealer setup before finalizing the dashboard.

Frequently Asked Questions

What are the most important wireless dealer KPIs?

Start with completed activation rate, pending transaction rate, error rate, refill rate, attach rate, support case rate, payout status visibility, and location productivity. Add service mix and completion time when the data is available.

Why should dealers separate completed and pending transactions?

Completed transactions show finalized output. Pending transactions show unresolved work. Combining them can make a location look more productive than it is and hide the queue that needs attention.

How should a dealer calculate refill rate?

Use customers with at least one refill divided by eligible active customers when that data is available. Otherwise, report refill transactions per 100 completed activations and compare consistent cohorts.

What should a multi-location KPI dashboard include?

Include location, service, period, transaction status, completed activity, errors, refills, attach rates, support cases, payout status, and an owner for each exception.

How can CTI help with dealer reporting?

CTI can discuss the support and operating resources available for an eligible dealer program. Talk with CTI about your reporting and dealer support needs before finalizing the dashboard definitions.