SMS
SMS overview
Each application owns a tenant on the fleet SMS router, with its own provider account.
Status: preview
The SMS router is multi-tenant and in production for other fleet products. DevSewa brokers it per application: the console signs every call as the devsewa app and names your engine tenant, and the router lets that app act only on tenants it owns. The connector is built; it opens for an account once the pairing between DevSewa and the router is applied for that environment.
Live versus test
Your live application maps to router tenant
<tenant>. A test application never creates a router tenant: DevSewa simulates delivery and verification, so it cannot use or bill a provider account.What you configure
| Tab | What it holds |
|---|---|
| Providers | One entry per provider (SMS Nepal, Twilio, …) with your credentials. Secrets are write-only; the console shows a masked preview. |
| Routing | Per operation (send, verify) and country prefix: primary provider, whether fallback is allowed, and a per-message cost ceiling. |
| Send & verify | A test message and a full OTP round trip against your configuration, so you see exactly what a user would. |
Money safety
- A tenant with no provider account of its own is refused. There is no fallback to a DevSewa or fleet account.
- Credentials belong to the router tenant, not to DevSewa; disabling a provider stops sends immediately.
- Every provider change, routing change and test send is written to your audit log.