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?
This guide will cover how to:
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 required
, recommended
, or 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 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.
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 lock screen. 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:
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.
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.
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.
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.