A2P 10DLC Campaign Vetting Delays: Twilio cannot approve 10DLC Campaigns ourselves, and must rely on third parties who control our connections to carriers to sign off. These external processes are creating several week delays for our customers. We continue to escalate these issues and are working to reduce delays wherever possible. Further details will be shared in the Campaign Vetting Changes article as they become available.

What is Sticky Sender and how does it work?

Sticky Sender makes sure the same From phone number is selected when sending messages via Messaging Services a particular recipient. This allows your application to consistently send messages to your user from a single recognizable phone number.

When Sticky Sender is enabled, Twilio will maintain a mapping of the To and From phone numbers. This mapping is created after the first message is sent from your Messaging Service to a particular recipient. Any future messages sent to that recipient from that Messaging Service will also use the same From number.

Disabling and re-enabling Sticky Sender

If Sticky Sender is turned off, any existing mappings will no longer be referenced, but they will not be instantly deleted. This means that if you toggle Sticky Sender back on in the future, any existing mappings will be referenced again, unless they expired due to age (see below).

Removing a number from the Messaging Service

When a Twilio phone number is removed from your Messaging Service, all Sticky Sender mappings associated to the removed Twilio number are deleted.

Sticky Sender time-to-live (TTL)

Effective May 1, 2022, Twilio is implementing a data retention policy that automatically deletes stale Sticky Sender mappings that have not been used in over a year. Any Sticky Sender mappings that are actively used will be unaffected.

For full details, see Messaging Services - Sticky Sender.

Have more questions? Submit a request
We can’t wait to see what you build.
Powered by Zendesk