There are cases where control is highly relevant to the operation of CPaaS, as it helps prevent exceeding certain thresholds and avoids unwanted situations. The ability to establish boundaries that enable this kind of control is a highly convenient tool to rely on.
By the way, SCG provides direct control over Sender IDs, addressing the need to implement thresholds and assisting enterprise developers with these tasks, allowing them to focus on business processes.
This document provides the required procedure to implement the Sender ID control service that offers this functionality.
Sender ID Control
Sender ID control is an SCG feature that can be configured for any Sender ID on the the platform to prevent the delivery of messages from that Sender ID when the message falls outside the configured criteria or window. The restriction service is only supported for messages originating from the customer’s application.
A Sender ID restriction could be of 2 types:
- Delivery time window.
- Daily Message Volume limit (approximate).
How this works:
Customers with a valid Sender ID can request the addition of the restriction feature by contacting their account manager. Once provisioned, this configuration takes approximately 10 hours to take effect.
Customer can choose to enable a Delivery time window restriction and/or a Daily message volume restriction. Both restrictions can also be enabled on the same Sender ID simultaneously.
SMS/MMS capable sender IDs can be enabled with the restriction services.
Use Case: Delivery Time Window
Message Delivery Time Window: A time-based delivery window in which messages submitted and processed by SCG within a preset time frame are delivered to the end user.
The Message Delivery Time Window for a Sender ID has a few attributes:
• Is configured at Country-level.
• Can also be configured based on time-zone.
• Restriction can be applied to Sender IDs in the configured country.
• Messages that fall outside of the Delivery Time Window are rejected (FAILED).
• Messages rejected after enforcing the configured rule are not charged.
0 Comments