Twilio is the most widely used SMS provider in the world and the safest default recommendation for most agencies, especially in the United States, Canada, or mixed international environments.
It is strong on delivery, carrier compliance, and global reach. The main thing agencies need to understand is that compliance, especially for US traffic, matters just as much as the credentials themselves.
Why Twilio is usually the default
Twilio is a practical default because it combines wide country coverage, strong deliverability, good documentation, and support for the compliance work required in North America.
- Local and toll-free numbers
- 10DLC support for the US
- MMS support in supported markets
- Alphanumeric sender IDs outside the US and Canada
- Coverage across a very large number of countries
What you need before starting
- A Twilio account
- A Twilio phone number or sender setup
- The Account SID and Auth Token from Twilio
- 10DLC registration if you are sending to US mobile numbers from a standard local number
Understand 10DLC and toll-free compliance first
If you are sending to US mobile numbers, compliance is not optional. Unregistered 10DLC traffic is blocked by carriers, so setup is not really finished until that part is handled.
Agencies can either go down the 10DLC route for local numbers or use toll-free numbers with their own verification path. Which route is best depends on how the agency wants the sender identity to behave and how fast it needs to launch.
- Brand registration is done once for the business identity
- Campaign registration is done for the messaging use case itself
- Toll-free numbers can be a practical alternative to local-number 10DLC in some cases
- Outside the US and Canada, alphanumeric sender IDs are often the better fit where supported
If you are registering on behalf of clients in Twilio, make sure the Twilio-side reseller or agency setup is handled correctly from the beginning.
Set up Twilio in the platform
Go to `Campaigns -> SMS Providers`, click `Add SMS Provider`, name the provider, choose `Twilio`, and continue through the setup flow.
| Field | What to enter |
|---|---|
| Phone Number | The Twilio number including country code |
| Account SID | The SID from the Twilio Console |
| Auth Token | The Auth Token from the Twilio Console |
| Sender Name | Optional and mainly relevant outside the US and Canada |
Test the connection and save
Use the provider test step to verify that Twilio credentials and the account state are valid before saving. If verification passes, save the provider and let it become the default or assign it where needed.
- A valid connection confirms the credentials are correct
- The provider can then be used as the agency default or assigned to organizations
Twilio and MMS
Twilio is one of the providers that supports MMS inside the platform. That matters when agencies want image-based review requests or more visual follow-up flows.
- MMS support is relevant mainly in the US and Canada
- An MMS send costs 1 extra credit on top of the text segment cost
- The phone number itself needs to support MMS
Cost expectations
Twilio charges directly for each SMS or MMS send, with rates varying by country and message type. The platform does not add markup to Twilio pricing itself.
For agencies, the real operational cost picture also includes carrier fees, compliance registration costs, and the customer plan credit model inside the platform.
How Twilio interacts with custom-plan credits
Twilio changes the delivery provider, not the campaign credit model. In normal agency-managed sending, SMS review request messages still consume the customer plan SMS credits according to message segment cost.
The key exception is customer-owned SMS provider usage. If a customer is sending through their own SMS provider connection on their side, those sends do not consume the agency-side SMS credits.
- Text segment count determines the SMS credit cost
- MMS adds one extra credit
- Agency-side Twilio sending still respects customer plan SMS limits