SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Australia Sender ID Compliance for Verify and Authy

Australia's Communications and Media Authority (ACMA) has introduced a new Sender ID Register known as ACMA Assist. Starting July 1, 2026, all Alphanumeric Sender IDs used to send SMS in Australia must be registered on this centralized registry. This guide walks you through how to send OTP messages to Australia via Twilio Verify and Authy APIs.

What do I need to do?

To determine the actions relevant to you, please answer the following questions:

  1. Are you an Independent Software Vendor (ISV)? 
    Do you provide messaging services to other businesses (your customers) through your Twilio account? If yes, jump to Independent Software Vendors (ISV)
  2. Do you intend to use Twilio’s common sender ID: TWVerify? (easiest option)
    Would you like to use Twilio’s common sender ID: TWVerify with a standardized format for your Australian OTP messaging? If yes, jump to Direct Customers (Non-ISV) using TWVerify
  3. Do you want to use your own brand name? 
    Do you want your company or product name to appear in the Sender ID or the message body? If yes, jump to Direct Customers (Non-ISV) Registering a Branded Sender

 

Direct Customers (Non-ISV) using TWVerify

To make it easier for Twilio Verify/Authy customers, Twilio has already registered the Twilio-owned TWVerify sender ID for your standard SMS OTP use cases and will ensure your brandless OTP messages are sent exclusively from the TWVerify common sender ID. Here’s an example of what this looks like:      

From: TWVerify 
Message body: “Your OTP code is 123456.”

Required Actions

Compliance Requirements: You must create a business type Primary Customer Profile (PCP) in the Twilio Trust Hub and provide business details, including a government-issued ID for your authorized representative. 

 

Direct Customers (Non-ISV) Registering a Branded Sender

If you want your SMS OTP messages to include your own brand name in the sender ID or the message body, you must register a branded sender ID through the Twilio Console. Before you start registering your sender IDs on Twilio Console, gather the following:

  • Business details: Entity type, official business name, and contact info
  • Authorized representative: Name, contact info, and government-issued ID for the person authorized to manage your sender IDs
  • Evidence of use case (only for non-Australia based businesses): Documentation linking the requested sender ID to the official brand (e.g., trademark docs or business registration)

You can find detailed information on documentation required here.

How to submit information for sender ID registration on Twilio Console

Note: If you already send SMS OTP traffic to Australia today, you may have received a previous customer advisory with instructions on how to prepare for this submission process.

For complete details on each step, refer to the Australia sender ID Onboarding Guide.

  1. Navigate to the registration form on Twilio Console (Phone Numbers -> Alphanumeric sender IDs -> Australia registration form).
  2. Enter the sender ID you want Twilio to register on ACMA Assist (2-11 characters) and make sure it follows the requirements for a registrable sender ID in Australia.
  3. Select the country where your company's headquarters is located.
  4. Identify if your messages are Transactional or Promotional.
  5. Specify that you're a Direct Customer then select a customer profile or create a new customer profile to provide your business information.
  6. Provide the following details about your sender ID and make sure to indicate that you’ll be using your sender ID for Twilio Verify’s products.
  7. Provide evidence of how the sender ID is connected to your business/brand.
  8. Verify the identity of your representative by using one of two methods:
    1. Officer ID: Upload or live-capture a government-issued ID for a company officer listed on the relevant company extract ; or
    2. Authorized Rep + LOA: Upload government-issued ID and a Letter of Authorization (LOA) signed by a listed company officer of the relevant entity 
  9. Upload supporting documents.
  10. Provide an email address and/or status callback webhook where you'd like to receive status updates for your Twilio submission.
  11. Follow on-screen instructions to complete identity verification.
  12. Review all details carefully, then click “Submit registration”.

Note: Processing takes up to 15 business days, so submissions after June 1 may not be approved before the July 1 enforcement date.

 

Independent Software Vendors (ISV)

If you’re an ISV (you provide messaging services to other businesses), you’ll need to accept the Twilio partnership terms. This applies whether you or your end customers are using TWVerify or if you're registering a branded sender ID for yourself or your end customers. Depending on which of these two options you choose, the way in which you accept the Twilio partnership terms differs and is detailed below:

Required Actions

Using the TWVerify sender ID

If you plan to send either a portion or all of your customers’ SMS OTP messages using TWVerify, follow the link below to review and accept the partnership terms. Twilio may contact you with additional questions to verify your information.

Please have your company's authorized representative complete the form below to acknowledge and agree to our Sender ID partnership terms here.

Registering a Branded Sender ID

If you are registering your own or your customers’ Branded Sender IDs and not using TWVerify, the terms and conditions for partnering with Twilio are available within the registration flow on the Twilio Console.  

Before you start registering your sender IDs on Twilio Console, gather the following:

  • Business details: Entity type, official business name, and contact info
  • Authorized representative: Name, contact info, and government-issued ID for the person authorized to manage your sender IDs
  • Evidence of use case (only for non-Australia based businesses): Documentation linking the requested sender ID to the official brand (e.g., trademark docs or business registration)

You can find detailed information on documentation required here.

How to submit information for sender ID registration on Twilio Console for ISVs

Note: If you already send SMS OTP traffic to Australia today, you may have received a previous customer advisory with instructions on how to prepare for this submission process.

For complete details on each step, refer to the Australia sender ID Onboarding Guide.

  1. Navigate to the registration form on Twilio Console (Phone Numbers -> Alphanumeric sender IDs -> Australia registration form).
  2. Enter the sender ID you want Twilio to register on ACMA Assist (2-11 characters) and make sure it follows the requirements for a registrable sender ID in Australia.
  3. Select the country where the company's headquarters is located.
  4. Identify if the messages are Transactional or Promotional.
  5. Specify that you are an Independent Software Vendor (ISV) and read and check the box for the Partnership Agreement specified in Option A - Partner with Twilio.
  6. Select a customer profile or create a new customer profile to provide your business information.
  7. If you're registering a sender ID for your own use, use a Primary Customer Profile. If you're registering the sender ID for one of your end customers, use a Secondary Customer Profile and register the sender within the corresponding subaccount. 
  8. Provide the following details about the sender ID and make sure to indicate that you’ll be using the sender ID for Twilio Verify’s products.
  9. Provide evidence of how the sender ID is connected to your business/brand or your end customers’ business brands.
  10. Verify the identity of your representative (or the representatives of your end customers) by using one of two methods:
    1. Officer ID: Upload or live-capture a government-issued ID for a company officer listed on the relevant company extract (the company extract of the end customer entity); or
    2. Authorized Rep + LOA: Upload government-issued ID and a Letter of Authorization (LOA) signed by a listed company officer of the relevant entity (the government-issued ID of and a LOA from your end customer entity). 
  11. Upload supporting documents.
  12. Provide an email address and/or status callback webhook where you'd like to receive status updates for your Twilio submission.
  13. Follow on-screen instructions to complete identity verification.
  14. Review all details carefully, then click “Submit registration”.

Note: Processing takes up to 15 business days.
 


 

 

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