SMS Providers
To send SMS campaigns, connect an SMS provider. SMS is configured per workspace by each customer, so everyone uses their own SMS account and number.
Location (customer): Campaigns → SMS Gateways (/app/broadcasts/sms-gateways)
📸 Screenshot: The SMS Gateways page with provider options.
Supported providers
| Provider | Credentials needed |
|---|---|
| Twilio | Account SID, Auth Token, From number |
| Vonage (Nexmo) | API Key, API Secret, From |
| MessageBird | Access Key, Originator |
| SMSBD | API Key, Sender ID |
| REVE SMS | API Key, API Secret, Mask |
| BulkSMS BD | API Key, Sender ID |
| sms.net.bd | API Key, Sender ID |
| MimSMS | API Key, Sender ID |
Setup
- Go to Campaigns → SMS Gateways.
- Choose your provider.
- Enter its credentials (from your provider's dashboard).
- Save.
You can now select SMS as a channel when creating a campaign.
Getting your credentials
- Twilio — Console → Account Info (Account SID + Auth Token). Buy a number for the "From".
- Vonage — Dashboard → API settings (API Key + Secret).
- MessageBird — Dashboard → Developers → API access (Access Key).
- Regional gateways (SMSBD, REVE, BulkSMS BD, sms.net.bd, MimSMS) — get the API key and approved sender ID from the provider.
Delivery status callbacks
Some providers can report delivery status back to WhatsMine via a callback URL pattern:
https://your-domain.com/webhooks/sms/{provider}
where {provider} is one of twilio, nexmo, messagebird, smsbd, reve, bulksmsbd, sms_dot_bd, mimsms. Configure this in your provider's dashboard if you want delivery receipts reflected in WhatsMine.
Tips
- Sender ID rules vary by country — alphanumeric sender IDs may need pre-registration, especially in regions like the EU, India and Bangladesh.
- Test with a small audience first to confirm delivery and formatting before a big send.
- SMS sends count against your plan's
sms_per_monthlimit.
➡️ Next: AI Providers.