Welcome to the "Prepare your sender strategy" milestone of the Programmable Messaging API Onboarding Guide. In this section, you will create and configure your parent account, make informed decisions about what senders to use for your business, and begin the process of provisioning them. It is not uncommon for businesses to choose the wrong sender type and doing so can lead to costly problems down the road. We strongly advise you to follow the recommendations summarized here.
Who are your stakeholders at this stage?
- Business Team: Ensure that your initial decisions on sender types are in line with your organization’s long term goals for marketing and growth.
- Finance Team: Proactively agree on the expected upfront and monthly costs associated with your chosen sender types so that you don’t run into billing related setbacks down the line.
This guide will cover how to:
- Create and configure a parent account.
- Choose a sender.
- Review and start the relevant regulatory requirements for your sender(s).
The actions featured in this milestone are presented in a sequence but they are not strictly linear.
The action(s) associated with each step below are marked as
optional to help you navigate this guide efficiently while providing all the information needed to develop a solid messaging program.
Before we can start provisioning senders for your account, we need to ensure that you have a well-configured parent account. This process is straightforward, but there are a few easy configurations you can do now to ensure that you have the strongest foundation possible as you advance through onboarding.
Read about the actions below and navigate to the relevant documentation to complete your account creation and configuration.
- Create an account (required)
- Enable two factor authentication (2FA - required for paid accounts): we recommend erring on the side of caution and requiring 2FA on every login but you also have the option to require this every 30 days. Discuss these options internally with your security and administrative team and decide on what works best for you.
- Add Users to your Account (optional): on this page you can add teammates and provide them with a given role to fit their Twilio account access needs. We advise keeping administrative access at a minimum. Once teammates have roles in the account, you can set up notification preferences for them so that they can get critical information in a timely manner.
- Create API Keys for your Account (recommended): within the Twilio Console, you can authenticate your API usage using account credentials, account SID, or through an API Key. We highly recommend utilizing API keys as it’s the most secure.
Well done! You now have a working, configured account built for scale.
One of the benefits of a message is the ability to reach a consumers’ handset and land on their lockscreen. To get there, you’ll need to select a sender or phone number that meets your use case, geographic, and feature needs.
We recommend considering these three basic questions as you choose your sender type:
- What is your use case? This will indicate the type of throughput and features you’ll require.
- Where are your recipients? This will dictate the regulatory requirements you’ll need to complete.
- What is the expected behavior? This will indicate the features (such as a one-way or two-way communications) you’ll need your sender type to be able to perform.
Your sender choices and the process of provisioning them will look different depending on whether or not you are sending to North America. Choose the path below that best describes your sending location.
Navigate to the relevant documentation to choose and start the process of provisioning your sender.
- Set your Geo Permissions (required)
- Choose the sender that will meet the needs of your use case(s) (required)
- Provision the sender you need (required)
- Port existing numbers (optional)
It’s worth noting that all senders in North America will require some form of verification or registration to protect consumers from bad actors, ensure the high deliverability of messages, and preserve the value of the channel for all senders. Here’s a summary of what to expect.
- For Application-to-Person (A2P) 10-digit long codes (standard phone numbers with a local area code prefix), you’ll need to register both your Brand and Campaign in the Twilio Trust Hub. For more information, please check out the How to register for A2P 10DLC support article.
- For Toll-Free phone numbers (10-digit numbers beginning with an 8XX- prefix) you will need to complete the mandatory verification process in the Twilio Trust Hub before sending messages. For more information, please check out the How to verify a Toll-Free number support article.
- For short codes (five- to six-digit messaging-only numbers) businesses must complete a registration process that can take 8-10 weeks. For more information, please check out the Starting a Short Code Application support article.
With Twilio’s Messaging APIs and more than 65-thousand phone number prefixes, you can reach consumers in over 180 countries. However, some countries have restrictions on the sender type used to reach consumers, including registration requirements. If SMS is not a viable option for your sending locations, WhatsApp can often offer a great alternative.
Navigate to the relevant documentation to determine the right sender(s) for you and begin the regulatory process.
- Review country-specific SMS guidelines (required)
- Learn about international phone number capabilities (recommended)
- Learn about an alphanumeric Sender ID (recommended)
- Set your Geo Permissions (required)
- Identify the required regulatory documentation for the countries on your list (required)
- Submit your regulatory bundles (required)
At this point, you should be ready to provision the type of sender you need. You can also consider porting an international phone number if appropriate for your business.