Home›Telecom›Use cases›Stage 3 — Service Suspension← Use case library
Use case · Collection & Dunning

Stage 3 — Service Suspension

Service suspended after final dunning due to persistent non-payment.

CollectionDunning SchedulerProvisioning
SystemPrimary actor
Collection & DunningCategory
3Modules involved

At a glance

Trigger

Debt persists after final notice

Primary actor

System

Outcome

Service restricted until payment

Main flow

The usual path from start to finish.

  1. 1
    Check exemptions (vulnerable customers, disputes)

  2. 2
    Suspend outgoing services

  3. 3
    Notify customer

  4. 4
    Keep emergency access

  5. 5
    Monitor for payment

Exceptions & alternate flows

Payment received

Immediate restoration

Systems & modules involved

CollectionDunning SchedulerProvisioning

Business rules

KPIs to watch

Standards & references

TMF678Customer Bill Management

Related pages

Collection & Dunning→Provisioning & Activation→Previous: Stage 2 — Escalation Notice→Next: Payment Received — Collection Closed→Telecom Use Case Library→

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.