Product changelog and announcements

You can now send RCS messages to Rogers phone numbers, completing RCS coverage across Canada’s major carriers.

When requesting RCS Sender approval in Canada, Twilio will now submit the Sender for review across all major carriers, including Rogers. RCS Senders already approved by other Canadian carriers will automatically be submitted to Rogers for review and approval. No action is required.

To start sending branded RCS messages, go to the Twilio Console to create and submit an RCS Sender.

For more information, see our RCS documentation.

Short Code numbers are now supported as SMS senders in Twilio's Ireland (IE1) region for EU data residency. When using this feature, SMS message personal data sent or received via Short Codes is stored and processed in the EU up to the point it reaches Twilio's connections with telecommunications providers.

With this release, the IE1 region supports the following features:

• Short Code senders: Send and receive SMS messages with short codes in IE1. 

• Region Configuration API: Configure short codes for IE1 using the V3 region configuration API.

• Short Codes API: Set IE1 inbound webhook configurations using the ShortCodes resource.

• Messaging Services API: Add short codes to IE1 messaging services using the service ShortCodes subresource.

To learn more and get started, see the developer documentation.

We are excited to announce General Availability support for WhatsApp Embedded Signup Version 4. This release upgrades the existing WhatsApp Self Sign-Up onboarding flow in the Twilio Console, seamlessly aligning with WhatsApp’s recent account updates to deliver a cohesive, up-to-date sender registration process. The upgraded experience simplifies phone number setup and incorporates MM API Terms of Service acceptance directly within the flow. This update is required as part of WhatsApp’s planned deprecation of older versions, ensuring uninterrupted onboarding for WhatsApp senders.

Error code 30915 now applies consistently to A2P 10DLC campaign registration and Toll-Free Verification. When a Sole Proprietor registration is submitted with a business  but the available information shows it is actually a registered legal entity (for example, an LLC or corporation) error code 30915 will be returned. 

What changed

• 30915 is now non-program specific; the same code and guidance apply whether you register via A2P 10DLC or submit for Toll-Free Verification.
• In addition to a corporate identifier in the business or brand name (LLC, Inc., Corp.), 30915 can now be triggered when your website or public records indicate a registered corporation, or when tax documents or business registration documents reflect a legal structure that does not match a sole proprietorship.

What you should do if you receive 30915

• Update the submission to the correct business type. If your business is an LLC, corporation, partnership, or any other entity with an EIN or Canadian Business Number, register it as a Standard or Low-Volume Standard Brand (A2P 10DLC), or select the correct business type for Toll-Free Verification, not the Sole Proprietor flow.
• Provide valid business registration documentation that matches your legal business entity.
• Keep your details consistent. Make sure your business name, website, and supporting documentation align across the submission.

Learn more: 

• Error 30915 reference 
• A2P 10DLC: Gather the Required Business Information
• Transition from a Sole Proprietor to a Standard Brand

WhatsApp Usernames is now supported on the Twilio Platform and Messaging APIs for WhatsApp. WhatsApp now allows users to adopt usernames. A username can optionally mask a user's personal phone number and allows them to interact with businesses through Business Scoped User IDs (BSUID). Twilio exposes this identifier in message webhooks and in Event Streams event data. Meta is releasing this functionality in multiple waves, starting on July 7, with additional countries to follow at later dates. Please check our documentation for the latest rollout schedule.

Email notifications for A2P 10DLC campaign registrations to give you greater visibility into your onboarding pipeline are now live.
Automated email updates at four critical stages of the campaign lifecycle:

• Initial Registration: Confirmation that your campaign submission has been received and is entering review.
• Approval: Notification that your campaign is live and ready to route traffic.
• Rejection: Immediate alert if a campaign fails carrier or ecosystem validation, allowing you to address issues quickly.
• Resubmission: Confirmation when a corrected campaign has been successfully submitted for re-review.

Where are these emails sent?

• Standard Direct Customers: Notifications are sent directly to the address provided in your Brand registration or the specific A2P bundle email field (which can be viewed and updated anytime within the Console).
• ISV Customers & Subaccounts: To protect the end-customer experience, if a campaign belongs to a subaccount under an ISV, the notification will automatically route to the Parent ISV account’s Primary Customer Profile (PCP) email instead of the subaccount.

We are excited to announce that Apple Messages for Business (AMB) is now available in Private Beta on the Twilio platform. This release allows businesses to connect with their customers directly within the native Messages app on iPhone, iPad, and Apple Watch, providing a secure, branded, and highly interactive communication channel.

With Apple Messages for Business, you can go beyond plain text to deliver rich, end-to-end customer journeys with features like:

• Native Entry Points: Meet customers where they already are—integrated natively into Apple Maps, Safari, Siri, and iOS Search.
• Rich Interactive Features: Utilize List Pickers for product selection, Time Pickers for scheduling, and Rich Links for high-fidelity website previews.
• Secure Commerce: Enable seamless, one-touch payments using Apple Pay, authenticated via FaceID or TouchID.
• Branded Experience: Build trust with a verified sender logo and end-to-end encrypted messaging.

To learn more and request access to the beta, visit Twilio's Apple Messages for Business product page.

Intelligent Alerts is now GA for all Twilio Messaging customers sending SMS traffic. It uses anomaly detection to automatically monitor your messaging traffic for unusual spikes in selected error codes, helping you identify potential delivery issues faster.

You can now specify the SMS or MMS sender Twilio uses when an RCS message fails to deliver using the new "FallbackFrom" parameter in your /Messages API request. The FallbackFrom sender must be in the same account SID, but does not need to be in your Messaging Service's sender pool.

This can be useful if you need fallback messages to come from a specific number, instead of relying on Twilio's automatic selection. You can also use this to send from one RCS sender representing your brand, with different fallback numbers per department, store, or representative.

For more information, please see our docs.