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.
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.
Configure the parent account before provisioning senders. Complete the following tasks in the Twilio Console or referenced documentation:
- Create an account (required).
- Turn on two-factor authentication (required for paid accounts). You can enforce 2FA at every login or every 30 days; decide with your security team.
- Add users (optional). Assign the minimum necessary roles and configure notification preferences for each user.
- 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.
The sender (sometimes called the "from" number) determines throughput, available features, and regulatory obligations. Answer these questions to narrow the options:
- What is your use case? Throughput and feature needs depend on whether you send one-time passwords, notifications, marketing messages, or two-way conversational traffic.
- Where are your recipients located? Geography defines regulatory requirements and available sender options.
- 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.
- Set Geo Permissions (required)
- Evaluate sender types (required)
- Provision the selected sender (required)
- Port existing numbers (optional)
North American senders require verification or registration:
- A2P 10DLC: Register both your Brand and Campaign in Twilio Trust Hub. See How to register for A2P 10DLC.
- Toll-Free numbers: Complete Toll-Free verification in Trust Hub before sending. See How to verify a Toll-Free number.
- Short codes: Submit a short-code application; approval typically takes 8–10 weeks. See Starting a Short Code Application.
If SMS is restricted or heavily regulated in a target country, consider WhatsApp as an alternative.
- Review country-specific SMS guidelines (required)
- Check international number capabilities (recommended)
- Assess alphanumeric Sender ID (recommended)
- Set Geo Permissions (required)
- Identify required regulatory documents (required)
- Submit regulatory bundles (required)
You can also port an international number if that better serves your use case.