Check SMS credit, delivery reports, and templates — then send changes through approval.
SMS Alert handles the outbound notifications your on-call process depends on. Luumen reads your credit balance, sender IDs, delivery reports, and template list on request, so you can see why a notification did or did not land. Changes to templates, contacts, and groups are previewed first, then applied once you approve. Luumen connects with an API key.
23 tools: 8 read, 15 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed SMS Alert run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — change user password, create new contact, create new group, create short url, and more — is shown as a plan and requires approval by default, including the 4 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to SMS Alert — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.