SMS campaigns in Omni are sent through your own account with an SMS provider. Messages go out from your sender ID or number, and your provider bills you for them directly. Each workspace connects its own provider.
Where: Campaigns → SMS gateways (/app/broadcasts/sms-gateways)
Supported providers
| Provider | What you'll need |
|---|---|
| Twilio | Account SID, Auth Token, From number |
| Vonage (Nexmo) | API Key, API Secret, From name |
| MessageBird | API Key, Originator |
| Plivo | Auth ID, Auth Token, From (sender or number) |
| Telnyx | API Key (V2), From number, Messaging Profile ID |
| Infobip | API Key, Base URL (for example xyz.api.infobip.com), Sender |
| ClickSend | Username, API Key, From |
| Amazon SNS | AWS access key ID, secret access key, region, Sender ID, SMS type (Transactional or Promotional) |
| MSG91 (India) | Auth Key, Sender ID (6 characters), Route, DLT Template ID |
| Fast2SMS (India) | API Key, Sender ID, Route |
| SMSBD, REVE SMS, BulkSMS BD, sms.net.bd, MiMSMS (Bangladesh) | API Key and Sender ID (REVE also needs an API Secret and sender mask) |
Setting up a provider
- Go to Campaigns → SMS gateways.
- Pick your provider and enter the credentials from your provider's dashboard.
- Save. You can now choose SMS as the channel when you create a campaign.
To switch providers, save a different one. To remove one, delete its credentials from the same page.
Where to find your credentials
- Twilio: Console → Account Info shows the Account SID and Auth Token. Buy or verify a number to send from.
- Vonage: Dashboard → API settings.
- MessageBird: Dashboard → Developers → API access.
- Plivo / Telnyx / Infobip / ClickSend: in each provider's API or developer settings.
- Amazon SNS: create an IAM user with permission to publish SMS, and use its access keys.
- Regional gateways: request an API key and an approved sender ID from the provider.
Sender ID rules
Rules for who may send SMS, and under what name, depend on the destination country:
- India: commercial SMS must be registered on the DLT platform. You need an approved sender ID (header) and approved templates; MSG91 asks for the DLT Template ID.
- Bangladesh, the EU, and many other countries: alphanumeric sender IDs often need to be registered in advance.
- United States and Canada: application-to-person SMS from ordinary long-code numbers requires 10DLC registration through your provider.
Your provider's documentation has the current rules for each country you send to. Check them before your first large send.
Good practice
- Test with a small audience first to confirm delivery and how the message looks.
- Include an opt-out instruction in promotional messages where the law requires it.
- SMS counts against your plan. Each message sent uses your plan's monthly SMS allowance; see Billing and plans.
Related: Campaigns · Email for campaigns
Still stuck?
Open a ticket from Support inside the app, or send us a message and we'll help you get it working.
Contact support