Skip to contentSkip to navigationSkip to topbar
On this page

Prepare your sender strategy


During the "Prepare your sender strategy" milestone of the Programmable Messaging API onboarding guide, you will:

  • Create and configure the parent Twilio account that owns all sub-accounts and messaging resources.
  • Select the sender type (for example, A2P 10DLC, Toll-Free number, short code, or alphanumeric Sender ID) that fits your use case, geography, and feature requirements.
  • Start any mandatory verification or regulatory registration for the selected sender.

Choosing an unsuitable sender can delay launches and create avoidable costs, so follow the recommendations in this guide.

Who are your stakeholders at this stage?

  • Business team: Ensure that your initial decisions on sender types align 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 to avoid billing-related setbacks in the future.
(information)

Info

The steps appear in a logical sequence, but you can complete many of them in parallel.

Each action in this guide is labeled required, recommended, or optional.


Step 1: Create and configure your account

step-1-create-and-configure-your-account page anchor

Configure the parent account before provisioning senders. Complete the following tasks in the Twilio Console or referenced documentation:

  1. Create an account(link takes you to an external page) (required).
  2. Turn on two-factor authentication(link takes you to an external page) (required for paid accounts). You can enforce 2FA at every login or every 30 days; decide with your security team.
  3. Add users(link takes you to an external page) (optional). Assign the minimum necessary roles(link takes you to an external page) and configure notification preferences(link takes you to an external page) for each user.
  4. Create API keys (recommended). Use API keys instead of the primary Account SID and Auth Token to authenticate requests.

Your account is now ready to scale.


Step 2: Choose and begin to provision your sender

step-2-choose-and-begin-to-provision-your-sender page anchor

The sender (sometimes called the "from" number) determines throughput, available features, and regulatory obligations. Answer these questions to narrow the options:

  1. What is your use case(link takes you to an external page)? Throughput and feature needs depend on whether you send one-time passwords, notifications, marketing messages, or two-way conversational traffic.
  2. Where are your recipients located? Geography defines regulatory requirements and available sender options.
  3. What behavior do you expect? Decide whether you need one-way, two-way, or high-volume messaging features.

Select the path that matches your primary sending region.

Sending to North America

sending-to-north-america page anchor
  1. Set Geo Permissions(link takes you to an external page) (required)
  2. Evaluate sender types(link takes you to an external page) (required)
  3. Provision the selected sender(link takes you to an external page) (required)
  4. Port existing numbers(link takes you to an external page) (optional)

North American senders require verification or registration:

Sending to countries outside North America

sending-to-countries-outside-north-america page anchor

If SMS is restricted or heavily regulated in a target country, consider WhatsApp as an alternative.

  1. Review country-specific SMS guidelines(link takes you to an external page) (required)
  2. Check international number capabilities(link takes you to an external page) (recommended)
  3. Assess alphanumeric Sender ID(link takes you to an external page) (recommended)
  4. Set Geo Permissions(link takes you to an external page) (required)
  5. Identify required regulatory documents(link takes you to an external page) (required)
  6. Submit regulatory bundles (required)

You can also port an international number(link takes you to an external page) if that better serves your use case.

Next: Build your account