Use case · Plan & Service Management
Service Reactivation
Suspended subscriber restores their service after resolving the cause.
Order CaptureOrder MgmtProvisioningBilling
CustomerPrimary actor
Plan & Service ManagementCategory
4Modules involved
At a glance
TriggerCustomer wants service back
OutcomeService restored; billing resumed
Main flow
The usual path from start to finish.
- 1
Verify identity and reason resolved - 2
Clear holds (payment, fraud) - 3
Reactivate on the network - 4
- 5
Resume recurring billing from the reactivation date - 6
Exceptions & alternate flows
Unpaid balancePayment required first
Systems & modules involved
Order CaptureOrder MgmtProvisioningBilling
Business rules
- Proration on mid-cycle changes
- Commitment and early-change fees
- Compatibility between plans and add-ons
KPIs to watch
- Change order success rate
- Changes completed same day
- Bill disputes after changes
Standards & references
TMF622Product Ordering
TMF637Product Inventory
This page describes generic industry practice and public standards. It is not based on, and does not describe, any particular vendor's product or operator's systems.