Automate the ISP Subscriber Lifecycle as a State Machine
Coordinate lead, installation, activation, billing, support, migration, suspension and closure with explicit transitions.
Coordinate lead, installation, activation, billing, support, migration, suspension and closure with explicit transitions.
A customer record is not a lifecycle
Subscriber operations cross sales, survey, installation, inventory, billing, RADIUS, network devices, payments and support. Automation becomes reliable when each stage has entry criteria, an accountable owner, allowed transitions and compensating action for partial failure.
Commercial
Lead, quote, order, contract and package intent.
Delivery
Survey, equipment reservation, installation and acceptance.
Service
Provisioning, authentication, session and assurance state.
Finance
Invoice, payment, credit, suspension and final settlement.
Make states precise
“Active” is too broad. Separate order accepted, install scheduled, provisioned, entitled, online, restricted and closed. A subscriber may be entitled but offline, or online while an invoice is disputed.
Transitions should validate prerequisites and record actor, reason, policy version and external references.
Handle distributed failure
Provisioning may create a database row and fail on the router. Store desired and observed state, retry idempotently and present unresolved work in an exception queue.
Compensation is business-specific: release reserved equipment, void an invoice, restore a previous package or schedule field recovery. Never hide partial completion behind a green toast.
Design suspension and closure carefully
Distinguish voluntary pause, non-payment, abuse, technical hold and permanent termination. Communications, access and accounting differ.
Closure preserves financial and audit history while revoking credentials, releasing addresses and inventory, and respecting retention rules.
Evidence before rollout
| Signal | Required proof |
|---|---|
| Transition map | Allowed states, owners and prerequisites are documented. |
| Idempotency | Retry cannot duplicate invoice, payment or provisioning. |
| Observed state | Device and RADIUS outcome is read back. |
| Exceptions | Partial work has an owner and safe next action. |
| Closure | Access, inventory, money and retention are reconciled. |
Put the plan into operation
- Map. Document current states and manual exceptions.
- Clarify. Split ambiguous statuses.
- Instrument. Add audit and external references.
- Shadow. Compare automated decisions without action.
- Pilot. Enable bounded low-risk transitions.
- Expand. Automate only after exception rates stabilize.
The decision standard
Lifecycle automation is trustworthy when every transition is explainable, retries are safe, distributed failures remain visible and commercial, financial and network state can be reconciled at any point.
Research basis: TM Forum lifecycle concepts; state-machine design principles; ITIL service management practices. Validate implementation details against the releases, contracts, and local regulations governing your network.