Cascades

Cascades are a mechanism for re—sending the same message through different communication channels (according to the established sequence of apps/services).

When cascading, the system first sends a message using app/service A. If the message is not delivered to the subscriber, it is redirected to app/service B, and so on, depending on the availability of subsequent apps/services in the cascade. Thus, there is practically no chance that the message will not be delivered and the probability of reading it upon receipt increases significantly.

The system administrator has access to the functionality of adding cascades for users.

When creating a new cascade, you must give it an arbitrary name, comment (optional) and specify the customer for whom the cascade is being created. Click “Save”.

In order for client messages to arrive in the cascade, you should configure the connection using the SMPP or HTTP protocols and, if necessary, install filters.

Next, create a set of cascading rules (alternately add the necessary applications and services to the cascade), and also set the order in which messages should be sent along the chain of added apps and services (“top to bottom” in order). To change the order, drag the added apps and services above or below, or delete unnecessary ones.

The system supports two types of cascading rules. The default type assumes that a simple sequence of apps and services is set for the cascade.

The second type involves a more fine-tuning of the cascade passage, depending on which carrier’s zone the message is being sent to. Suppose that in order to send messages to all numbers belonging to operator zone A, the cascade must implement the sequence: App A -> Service B -> App C, and to all numbers belonging to operator zone B, the cascade must perform the following sequence: App C -> Service B -> App A.

In both types of settings, for each app or service added to the cascade, it is possible to add a timeout setting after how many seconds the message should be activated by the next app/service. The timeout can be set either at the time of creating a new cascading rule, or after the rule is created.

The created cascade can be edited by the Administrator at any time.