Product changelog and announcements

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.

You can now delete WhatsApp message templates in the Twilio Console. To delete a message template, click on the template name on the WhatsApp Message Templates page and then click “Delete” at the bottom on the page. Per WhatsApp guidelines, you may not reuse the name of a deleted template for 30 days after deletion.

Customers registering for U.S. A2P 10DLC should use the new name “Proxy” instead of the old name “Conversational” when registering for campaigns of this type. This change is applicable in the A2P wizard in the console as well as ISV APIs (Create Campaign Use Case step). ISV API customers need to update their API integration.

This name change is to better represent the campaign type, which is meant for proxy/pooled numbers supporting personalized services and non-exposure of personal numbers. Some customers had incorrectly registered campaigns as Proxy/Conversational which should’ve been registered as Customer Care.

You can read more about the Proxy campaign use case here.

Customers can now view the reasons for their brand registration failures in the A2P wizard in the console or via the ISV APIs for US A2P 10DLC. In the A2P Wizard in the Twilio console, brand failures will result in an error screen with reasons for the failure and instructions to fix your brand registration before you can move forward. The GET Brand API call returns the failure reasons for ISVs registering their customers via API. You can review the failure reasons and API details here and reduce the likelihood of your brand registration failing by following the brand registration best practices here.

Customers registering for their Primary A2P Brand for US 10DLC traffic automatically get their brand vetted by carriers through a process called Secondary Vetting. This vetting costs $40 and was being covered by Twilio till Sept 30. The Secondary Vetting fee will now be passed through to customers and reflect in customer bills as the waiver has ended.

Note Starter Brands and Starter Campaigns continue to remain free of charge.

Businesses can now move their existing WhatsApp Business API phone numbers to the Twilio platform at any time whether they were previously registered through a different Business Solution Provider or directly with Facebook. Upon a successful migration, the transferred number retains its display name, messaging limit tier, quality rating, and Official Business Account status. High quality message templates on the account that it was previously registered on will also be copied over to the new account on Twilio.

For more details on how to move WhatsApp numbers to Twilio, please take a look at this support article.