Sending Strategy Management

Sending Strategy represents one type of configuration for your sending resources. This configuration in its simplest form allows you to set manipulation for your senders on a country level for a specific channel (SMS/MMS) on an Entity or Application-Entity level (read more about Entity and Application here). Sending Strategies have additional functionalities on top of sender manipulations, like Sticky sender (same sender used for all messaging towards the same destination) and Geolocated sender (sender picked based on the local area code of the customer receiving the message). More about Sending Strategy Management, available features, and future development can be read here.

Sending Strategy types:

• Application-level Sending Strategy (also called the Default Sending Strategy)
  • A strategy that distributes sending across the pool of senders that are automatically fetched based on the definition you specified in Resources Associations.
• Entity/Application-level Sending Strategy
  • A strategy used for client-specific setup. You can define different rules, features, and limitations for each client of yours.
• Additional features
  • Geolocated Sender - by turning on this feature, traffic will be sent from one of the defined senders that have the same local area code as the customer receiving the message. Customers are more likely to positively react to a message if it comes from a number from their local state. Note: Geolocated sender can be used for terminating messages in North America only.
  • Sticky Sender - by turning on this feature, when a customer receives a message from one of the defined senders then the same sender will be used for all further messages sent to that customer. Customers are more likely to positively react to a message if it comes from a consistent number connected with some brand/company.
  • Note: A geolocated sender and a Sticky sender can be used in combination.
  • Sender Type Priority - enables you to define the priority of your senders in case you have more than one sender for a destination country.
  • Coming soon:
    • Default Sender - enables you to define a sender that would be used in case a message does not pass with your Entity-specific sender/s. This can be defined per each Entity differently or can be defined as a default sender on the Application level.

Note: When the "from" field (sender) is defined along with application and/or entity in the sending API call, it overrides the Sending Strategy configuration and sender manipulations will not apply