9bx Connect
Providers, sender IDs and routing
Connect the services that actually deliver your SMS, WhatsApp, email and push messages, and decide which one is used for what.
Contents
- What it is for
- Who can use it
- Where to find it
- Providers
- Sender IDs
- Routing
- Example scenario
- Tips
- Troubleshooting
- Related pages
What it is for
9bx does not send SMS or email by itself. You connect your own accounts with gateways such as Twilio, SSL Wireless, SendGrid, Mailgun, SMTP or a Dinstar SIM gateway. Then you set which provider handles which message and what happens when one fails.
Who can use it
- Providers and Sender IDs: Connections manage permission.
- Routing: Routes manage permission.
Before you start you need an account and API keys from each provider. 9bx cannot create these. Nothing sends until at least one provider is connected for the channel.
Where to find it
Chat & Messaging → Chat settings → Messaging → Providers, Sender IDs, Routing
Providers
Provider cards with status, test and default.
The screen explained
| Item | Meaning |
|---|---|
| Add provider | Opens the catalogue: search, filter by channel and country (Bangladesh, Global, Worldwide), Beta badge, Setup guide link. |
| A card | Name, Active or Off, Default, Test mode, Balance, "Up to N a day", "N per second", Last worked. |
| Check / Check again | Tests the connection ("Connection works" or "Connection failed"). |
| Send test message | Sends a real message through it. |
| Make default | Used when no routing rule picks another provider. |
| Turn on / Turn off | Routing skips a provider that is off. |
| Edit, delete | Delete means "Messages can no longer go through it." |
| Warning "Paused after repeated failures" | The provider failed several times in a row and is retried at the time shown. Others are used meanwhile. |
| Banner "Not set up yet: …" | Channels with no provider. |
Provider form fields: Name (shown in routing and the log), Keys (encrypted, never shown again), Settings, Default for [channel], Daily limit, Speed limit, Branch (only that branch's messages use it), On, and Test mode.
After saving, 9bx shows the Webhook address. Paste it at your provider so you receive delivery reports and replies. Each provider has its own hint, for example Twilio Console status callback or SendGrid Event Webhook. Change address makes a new one; the old one stops working. For Telegram no paste is needed (use Register webhook on the Telegram page).
Add a provider
- Press Add provider and choose the service.
- Enter Name and Keys. Press Save and check.
- Fix any error shown, then paste the Webhook address at the provider.
- Press Make default if it should be the main one for the channel.
- Press Send test message to your own phone.
Sender IDs
Chat & Messaging → Chat settings → Messaging → Sender IDs
The name, number or address your messages come from.
| Field | Meaning |
|---|---|
| Add sender ID | Opens the form. Without any, each provider's own sender is used. |
| Type | Name (letters) (up to 11 letters or digits, for example PADMANET), Phone number, Short code, SIM port, Email address, Email domain, WhatsApp number. |
| Provider | Leave empty to use with every provider of the channel. |
| Countries, Message types | Two-letter codes such as BD. Empty means all. |
| Registration | Not needed, Pending, Approved, Not approved, with a Reference. Some countries deliver only from approved senders. |
| Default sender | Used for the channel when nothing more specific applies. |
Country rules are shown as hints, for example "Letter sender IDs are not delivered in …. Use a number there." and "Marketing texts: prefix …".
Routing
Chat & Messaging → Chat settings → Messaging → Routing
Pick the channel tab, then rules are tried from top to bottom. The first matching rule wins and the rest are tried in order if it fails. A message matching no rule uses the default provider.
| Item | Meaning |
|---|---|
| Add rule | Opens the form. |
| When | Any message, A type of message (verification codes, transactional, marketing) or One event (for example ticket opened, missed call). Optional Country code, digits after +, such as 880. |
| Send through | Provider and Sender. |
| Share | Rules at the same priority split traffic by this number. |
| Stop here | If it matches, less specific rules are not tried as fallbacks. |
| On | Turn a rule off without deleting. |
| Drag handle | Drag to reorder. Higher rules are tried first. |
| Tried in this order | Preview of the chain. |
| Route test | Enter a number or address and press Test. It shows the providers that would be tried and why others were Passed over (for example Keys missing, Daily limit reached, Sender not registered) without sending anything. |
Example scenario
Padma Net Support connects SSL Wireless as default for SMS and Twilio as a backup. A rule "Verification codes → SSL Wireless" is placed first. When SSL Wireless is paused after failures, codes still arrive via Twilio. They use Route test with +8801711000111 to confirm the order.
Tips
- Always keep a default provider for each channel you use.
- Set a Daily limit on pay-per-message providers.
- Use Route test after every routing change.
Troubleshooting
"No default SMS provider: messages that match no rule can't be sent." Press Make default on one provider.
I see sent but never delivered. The Webhook address is not pasted at the provider.
A provider shows Paused. It failed repeatedly. Check keys and balance, then Check again.