Product changelog and announcements

You can now utilize the ampersand (&) character in Twilio Alphanumeric Sender IDs. This can help you send text messages from a sender that better represents your brand name: for example, Owl&Co. This feature is only available in Alphanumeric Sender ID-eligible countries. Please refer to this guide to learn how to use Alphanumeric Sender IDs with Twilio messaging services.

Sending WhatsApp messages with media now supports additional content types in a public beta, including Microsoft Word, Excel, PowerPoint, and certain audio files. See this document more information on all the different media types we support.

When users message a business from a "Click to WhatsApp" advertisement, Twilio will now pass additional information to inbound message webhook regarding the advertisement the user clicked on. This allows businesses to create workflows in WhatsApp that intelligently respond based on the originating advertisement. Businesses can also better understand their advertisement’s performance by tracking user responses to an advertisement.

To learn more about the new properties that are included on our request to your webhook, visit https://www.twilio.com/docs/messaging/guides/webhook-request#whatsapp-specific-parameters.

If you face errors in submission or brand verification when you submit your brand details for A2P registration, you will now see a simplified step in the A2P wizard in TrustHub. The multiple steps to edit your brand earlier have been simplified into a single step in the console. This will help you save time in registering your A2P brand and allow you to focus on the most important fields to review. The new design also provides transparency on the number of retries remaining.

You can read more about brand editing here.

If your concerns are not addressed through the instructions shown in the wizard or if you are an ISV API user, you can refer to the new comprehensive guide for troubleshooting your A2P brand here.

We are excited to announce that Message Scheduling is in public beta!

You can now schedule a message over SMS, MMS and Whatsapp using the Programmable Messaging API. Today, when you make an API request to Twilio’s Programmable Messaging API, a message is sent out instantaneously. With this new feature, you can intentionally delay or schedule the time a message is sent out up to 7 days in the future. This means you no longer have to rely on internal cron jobs or scheduling services.

Check out our documentation and blog post to learn more and try scheduling a message.

When you submit brand details for A2P registration, you will be shown feedback if the information could not be verified by the registration vendor, TCR. Based on this feedback, you can now edit the brand information, as explained here with an example of TrustHub UI in the Twilio console. If you are using the ISV APIs, you also have the capability to edit such a brand using APIs as explained here.

For the majority of brands facing verification failures, Twilio will allow you to update your brand up to three times via self-service, after which you would be redirected to customer support for further help. For a minority of brands facing failures, you will be redirected to customer support right away, since the problem can not be resolved via self-service.

Twilio will bear the costs of updating your brand. You can read more about updating your brand details and brand registration best practices here.

It is now possible to edit the addional website, business vertical, and about fields for your WhatsApp Senders within the Twilio Console.

1. Click here or navigate to Messaging > Senders > WhatsApp Senders.
   
2. Click "Edit Sender" on the sender you wish to update.
3. Under "Business Profile Information", you may now add or update the additional website, business vertical, or profile about fields.

ISV customers using the APIs to register brands for US A2P 10DLC will see two new values for brand registration status (‘status’ field):

1. IN_REVIEW
2. DELETED

Customers will also see new behavior for this field. You can check the github changelog here for the new enums available November 1. Starting December 1, using GET API to check brand registration Status will return ‘status’ as IN_REVIEW when your brand is under manual third-party review. The manual review can take 7+ days. Status ‘DELETED’ will be returned when a brand is deleted. Since a new status type can be a breaking change for you, please update your code before Dec 1.

Additionally, behavior of the ‘status’ field now represents a more accurate status of the brand as it is APPROVED only when your brand registration is complete and you can move to campaign creation. This eliminates the need for you to check multiple fields to know the action required from you on a brand. You can see the new behavior of status in the A2P wizard within Twilio Console, and in the API. Before December 6th, IN_REVIEW status will be visible on Console but not be returned in API to give adequate time for your API integration to be updated.

New U.S. A2P 10DLC registration flows are now available for 527 Political Organizations and K-12 Education customers. These new registration flows are available in both the A2P wizard in the Console as well as ISV APIs.

• 527 Political Organizations can now complete registration by providing their Campaign Verify token during A2P brand registration. This will qualify the brand for the Political special use case and unlock increased message limits
  • Onboarding Guide for ISVs
  • Onboarding Guide for Direct Brands
• K-12 Education customers can now register their campaigns using the new K-12 Education special use case. The K-12 Education use case offers both increased message limits and reduced carrier fees. Carrier post-approval required.
  • Onboarding Guide for ISVs
  • Onboarding Guide for Direct Brands

For more information on eligibility, messaging limits, pricing, and FAQs for these registration flows, please see our article on Special Use Cases for A2P 10DLC.