1. Scenario overview
Suspend and resume decide whether a SIM can reach the network. A plan change swaps the plan. Activation is the first time a SIM is turned on. Suspend covers overdue payment, data used up, a policy violation, and a device being taken back. Resume can wait for a person to approve it, or it can start as soon as payment lands. SimtoLink supports one SIM or a batch, records why it was suspended, and lets you configure the resume approval.
Automatic suspend fires on rules such as data used up or payment past due, with no one at the keyboard. In B2B2C, a successful payment resumes the SIM, linked to payment integration. After the suspend command goes out, it syncs with the operator and the status updates at minute level.
2. Core capabilities
When to suspend, and doing it by hand
When a SIM is suspended: overdue payment, data used up (linked to the overage policy), a violation, and a device taken out of service. Each suspend stores a reason, which the resume approval can follow. By hand: suspend one SIM or a filtered batch. Resume can be “a person approves” or “payment resumes it.” Approval can have several levels, and the record is kept.
Automatic suspend and B2B2C resume
Automatic suspend: when data runs out or payment is past due, the platform sends the suspend to the operator. It sits with overage management and usage billing. B2B2C resume: a customer who was suspended for non-payment pays in the self-service portal, and the payment callback resumes the SIM. WeChat and Alipay close the loop from payment to resume.
Reasons and approval
A suspend record keeps the time, the reason, and who did it. Resume can pass automatically, for example when a consumer payment lands, while a business account still needs a person. Grouping reasons — the share of overdue payment, the share of data used up — is what operations uses to adjust the offer.
Batch actions and a preview
Filter a batch by project, customer, or plan. Preview who it will hit before you run it, so a mistake is caught first.
3. The flow
4. Suspend and resume, plan change, and activation
The three jobs stay separate. The differences:
| Capability | What it owns | When it applies |
|---|---|---|
| Suspend and resume | Connectivity: suspend cuts the network, resume restores it | A SIM that is already active |
| Plan change | Swap the plan: a different data tier | A SIM that is already active |
| SIM activation | First use: stock becomes available | A SIM that is not yet active |
Suspend and resume only decide whether the SIM can connect. They do not change the plan. What happens when data runs out — suspend, or bill by usage — is the overage policy. This page sends the suspend command.
5. Where teams use it
- Overdue payment: Suspend automatically, and resume when the customer pays. Common in B2B2C.
- Data used up: Follow the overage policy. Suspend, or bill by usage.
- Device taken back: Suspend by hand when a device leaves service, so charges stop.
- A batch: Suspend or resume by project or by customer, for a project close or a migration.
6. What changes in daily operations
Suspend and resume keep SIM state disciplined. Automatic suspend lowers the unpaid-balance risk. Resume on payment is what consumer customers expect. Approvals can be traced, which compliance asks for. Reason categories give operations something to analyze. Minute-level sync with the operator means the command takes effect without a lag.
7. How to put it in place
Put an approval on suspend and resume so a click cannot cut a line by accident. Automatic suspend can follow data usage alerts and overage management. On the consumer side, payment resumes the SIM. Sensitive business actions should take more than one approval, and the record should stay. A batch can be filtered by project, customer, or plan, and you preview the impact before it runs.