Sending high volumes of messages in the US and globally can get very complex. Depending on the country and carrier you are sending messages to, your application may need to keep track of whether to use a short code or phone number, whether to use an Alphanumeric Sender ID or phone number, or which country choose when selecting a phone number for delivery.
By using a Messaging Service to send messages, enabled Twilio Copilot features can assist to improve the performance of the message.
A Messaging Service contains configuration options for your application, like the URLs that will be requested when you receive an incoming message on one of your numbers.
It also contains the configuration for your Copilot messaging features. Based on these features, Twilio will intelligently select the identity to use for sending your message or make content modifications.
So what can Copilot do for you? Let's dive into the features:
Sticky Sender makes sure the same
From phone number is selected every time your application messages 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
From phone numbers. This mapping is created after the first message is sent from your Service to a particular recipient. Any future messages sent to that recipient from the Service will also use the same
If Sticky Sender is turned off, all previously established mapping will not be referenced. However, if you toggle Sticky Sender back on in the future, any mappings previously created will be referenced again.
When a Twilio phone number is removed from your Messaging Service, all Sticky Sender mappings associated to the removed Twilio number are deleted.
For branded one-way messaging, many countries allow an alphanumeric string as the sender ID. Alpha Sender ID allows you to add your company name or brand to your Messaging Service. When sending messages to a country where an alphanumeric sender ID is accepted, Twilio will use your Alpha Sender ID as the
From parameter to deliver your message. A phone number from your Messaging Service will be selected if your recipient is in a country where alphanumeric sender IDs are not supported.
Alpha Sender IDs may be up to 11 characters. Accepted characters include both upper- and lower-case ASCII letters, the digits 0 through 9, and space: A-Z, a-z, 0-9. Alpha Sender IDs may not purely numbers.
In order to use Alpha Sender with your Messaging Service, Alphanumeric Sender ID must be enabled on your Account's SMS Settings.
Scaler distributes your outbound messaging traffic evenly across the phone
numbers in your Messaging Service to help you handle higher messaging volume.
When a message is sent from your Messaging Service, the
From number is selected
from among the phone numbers not currently being used to send a message.
When Sticky Sender is enabled, Copilot will prioritize any existing Sticky Sender mappings first then select the next available phone number from your Messaging Service that has the least amount of mappings.
Geomatch selects the Twilio phone number in your Messaging Service to match the country and area code of your recipient's phone number.
When sending messages globally, country geomatch automatically selects the Twilio phone number in your Messaging Service to match the country of your recipient’s phone number. If your Service does not include a Twilio phone number that matches the same country as the recipient, Twilio will first attempt to select a SMS-enabled US phone number before selecting another phone number to deliver your message. Your message will fail if there are no phone numbers available in your Service to deliver your message.
To use Geomatch, simply add phone numbers to your Messaging Service that match the countries of your recipients.
When a phone number of a new geographic country is added to your Messaging Service, Twilio will automatically select and remap any existing Sticky Sender mappings so that the From number can match the same country as your recipient's phone number.
When sending messages to the United States and Canada, Area Code Geomatch will select a local phone number with an area code that either matches or is an overlay of your recipient's number.
If a overlay or matching area code is not available. Copilot will select another US or Canadian phone number from your Messaging Service. Geographic proximity is not taken into consideration when selecting a phone number.
This feature is not available outside the the US and Canada.
Fallback to Long Code re-attempts message delivery using a long code phone number when select messages sent with a short code have not successfully been delivered.
When sending a message with your Messaging Service, Copilot will prioritize message delivery with a short code. If the short code message is 'undelivered' because the recipient is unable to receive short code messages, Copilot will re-attempt the message using a long code phone number in the same Messaging Service.
Please note that not all 'undelivered' messages are resent using a long code phone number. Successful message delivery via the long code is also not guaranteed.
You will be charged for both the short code message and the second message attempted over a long code phone number.
This feature should only be enabled if your users have opted into receiving SMS messages from you. All carrier compliance requirements and industry standards must be followed.
When your Messaging Service includes a shortcode, Twilio will always prioritize message delivery with the shortcode. If a carrier is not supported by a Twilio short code, Twilio will automatically deliver the message with a long code in your Messaging Service.
Please note, shortcode reroute, does not attempt to redeliver your message
over a long code due to a
Undelivered delivery status.
Sometimes a unicode character such as a smart quote ( 〞), a long dash (—), or a unicode whitespace accidentally slips into your carefully crafted 125 character message and now your message is segmented and priced at two messages instead of one.
When unicode characters are used in a SMS message, they must be encoded as UCS2. UCS2 characters take 16 bits to encode though, so when a message includes a unicode character, it will be segmented at 70 characters instead of 160 character per message segment.
Copilot's Smart Encoding helps detect those easy to miss unicode characters and replaces them with a similar GSM encoded character. This helps ensure that your message gets segmented at 160 characters and saves you from sending 2 messages.
Messages that include emoji or language based characters such as kanji are not transliterated with Smart Encoding. Please reference this list for the unicode characters Smart Encoding will replace.
Validity Period is the number of seconds messages sent from your Messaging Service will remain in Twilio's platform. If the number of seconds configured is exceeded, Twilio will fail the message and send a webhook to your status callback URL to notify your application.
The validity period can be set to between 1 and 14,440 seconds (a maximum of 4 hours).
Please note that Twilio's validity period only applies to messages while in the Twilio platform, messages may still be queued by carriers after the message has been sent to the carrier network.
MMS Converter will automatically deliver your MMS message as a SMS text message
with a shortened URL linking to your image when the
carrier is not supported to receive Twilio MMS Messages.
The shortened URL link (
http://m.twil.io/ followed by 7 unique characters) is
appended to the end of the message body and will remain active for 365 days.
Messages sent this way will be billed as SMS messages. If the appended URL causes the body of the text message to be greater than 160 characters, the message will be segmented and charged accordingly.
When Sticky Sender is enabled, Twilio's Copilot Features will follow the logic below to determine the optimal phone number to send your message from.