1. Scenario overview
Traffic alerts are a notice sent before the problem lands. They fire when data is about to run out, has already gone over the plan, or looks abnormal. That is a different job from traffic statistics, which look back at usage, and from overage management, which decides what happens after the plan is used up. Alerts are about warning people in time. You can set several tiers — for example, remaining 20%, 10%, and 5% — and you can also warn on overage and on a sudden spike.
When an alert fires, it can go out by SMS, email, in-app message, or webhook. In a B2B2C setup the same alert can reach the end user with a renewal link, so they renew or move up a plan before the SIM stops and the complaint comes in.
2. Core capabilities
Alert types and tiers
About to run out: fire on a remaining-data percentage or an absolute amount. At 20%, 10%, and 5% remaining you can send a separate alert, either only the first time or once at each tier. Overage: warn when usage continues after the plan is used up. Sudden spike: warn when one SIM or one pool grows far too fast in a short window, which is how unauthorized use and a misbehaving device show up. A traffic pool can alert on the pool total. A single-SIM plan can alert on that SIM.
Multi-channel notices
SMS, email, in-app message, and webhook are all optional. Route each alert type on its own channel: an urgent tier by SMS, a routine tier by in-app message. Webhook: when an alert fires, the platform POSTs JSON to a URL you choose, so your own systems, DingTalk, or WeCom can pick it up and push the alarm without a person in the middle.
Renewal prompts for B2B2C
Send the alert to the end user's phone or email, with a link into the self-service portal. One click finishes the renewal, which lifts conversion. Tied to user self-service and plan changes, the path runs from alert to renewal to upgrade.
Abnormal usage
A spike is the signal for unauthorized use or a device that is not behaving. Rules can use a time window and a usage threshold, so operations and risk teams hear about it before the bill or the outage.
3. How an alert runs
4. Alerts, statistics, and overage
Traffic alerts, traffic statistics, and overage management answer different questions.
| Dimension | Traffic alerts | Traffic statistics | Overage management |
|---|---|---|---|
| Focus | A notice before the problem | Usage analysis after the fact | What to do once the plan is used up |
| Core capabilities | Tiered alerts, multi-channel notices, renewal prompts | Usage totals, trend analysis, spotting overage | Usage-based billing, suspend, throttle, automatic add-on packs |
| When it acts | About to run out, already over, or abnormal | No automatic trigger | After the plan is used up |
| What teams need | An early warning and fewer stopped SIMs | Usage you can trace and trends you can read | A configurable overage policy and arrears you can hold down |
They work as a set. Alerts warn early so fewer SIMs run over. Overage management sets the policy after the plan is used up. Traffic statistics are the usage record the other two rely on.
5. Typical use cases
- Data about to run out: alert at 20%, 10%, and 5% remaining, so the user has time to renew or upgrade.
- B2B2C renewal prompt: the alert carries a self-service renewal link. One click finishes the renewal and conversion goes up.
- Abnormal usage: a spike raises an alert, so unauthorized use and a misbehaving device show up for operations and risk.
6. Why it matters
Traffic alerts on the SimtoLink IoT Cloud Platform surface data risk before it becomes an outage. Several tiers mean the first warning is not the last possible moment. B2B2C renewal prompts lift conversion and cut the number of stopped SIMs. Spike alerts make unauthorized use and abnormal devices visible. With overage management and user self-service, the path from alert to renewal stays in one place.
7. Implementation notes
Set more than one tier, such as 20%, 10%, and 5%, so the user is not hearing about it too late. In B2B2C, put a renewal link in the message. Send different alert types on different channels. A webhook can hand the event to an operations system, DingTalk, or WeCom. SimtoLink can help you set the rules and the channels.