Check campaign delivery in Segmento, then send SMS and OTP with approval
Connect Msg91 and your agent can read what your messaging is actually doing: which campaigns are running in Segmento, which event types are configured, and which user events failed. When a message needs to go out, it sends SMS through a Flow template or issues an OTP as a previewed, approved step. Authentication is by API key.
8 tools: 3 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Msg91 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.
This connection exposes write actions such as create user events, resend otp, send otp, send sms via flow (v5), and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 Msg91 — 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.