Definition
Traffic alert is a notice sent before the fact, when an IoT SIM card or a data pool is about to run out, is already over the allowance, or is using data in an unusual way. It is not traffic overage, which acts after the allowance is gone, and it is not traffic statistics, which analyzes usage afterward. An alert is the reminder that comes first.
Types of Warnings
- About to be exhausted: triggered according to remaining traffic percentage (e.g., 20%, 10%, 5%) or absolute value, with multiple levels of reminders.
- Overuse: warning when exceeding usage after the data plan is depleted.
- Abnormal surge: warning when usage abnormally increases in a short period, useful for detecting theft or abnormal devices.
Warning Threshold Configuration
The platform supports configuring warning thresholds by SIM card, data pool , project, etc. In single-card scenarios, multiple levels like remaining 20%, 10%, and 5% can be set; for a data pool, thresholds can be set for total pool usage or per-card usage. Abnormal surges can be configured with rules like "daily usage exceeds N times the daily average." Thresholds support flexible configuration to meet different business sensitivity requirements.
Notification Channels
Channels are SMS, email, in-app messages, and webhooks. In a B2B case the notice can go to operations staff or the customer’s administrator. In a B2B2C case it can go to the C-end user, with a renewal link into user self-service, so the user renews in time and the suspension rate falls. A webhook can reach the enterprise’s own system and open a ticket or a support case from the same alert.
Application Value
A traffic alert cuts unexpected suspensions caused by running out of data, which users notice. A sudden-surge alert helps find stolen use and devices that are behaving oddly, so the allowance stays where it belongs. A reminder beforehand can send the user to renew or move up a tier, which raises traffic billing revenue. Together with traffic overage and overage billing, the alert is the early part of usage control.
Configuration recommendations
It is recommended to configure multi-level alerts based on business sensitivity: high-value cards can be set at 30%, 20%, 10%, 5%, etc.; cost-sensitive scenarios can be set at 20%, 5%. Abnormal spike alerts can have rules such as 'daily usage exceeds three times the average of the past 7 days.' Notification channels can be selected according to the scenario: B2B prioritizes email and Webhook; B2B2C prioritizes SMS and in-app messages. To avoid user fatigue from frequent alerts, alert intervals can be set (e.g., the same card can only be alerted once within 24 hours).
Integration with traffic overage
Traffic warning and traffic overage management form a closed loop: warnings remind users to renew or upgrade their data plan before usage is exhausted, reducing the occurrence of overage; if the user does not handle it in time, overage management executes pay-as-you-go billing, suspension, speed limiting, or automatic renewal after usage is exhausted. It is recommended that warning tiers and overage strategies be configured collaboratively. For example, after a 5% warning, if the user does not renew, automatic suspension is executed when the data is exhausted to avoid the risk of arrears.