Update Emergency and Closure prompts on your IVR in seconds — from a browser, an email, or even a phone call. Per-PIN isolation, full audit trail, every channel governed by the same trust list.
Enter your authorized email and PIN. We'll send a one-time code.
Operators shouldn't need a developer to change what callers hear. MSGManager gives every team direct, governed control over the prompts that matter most.
Enable or disable the Emergency or Closure message with one click. Next call hears the change.
Edit the spoken prompt in plain language. Preview the TTS audio before publishing to callers.
See what's currently playing, when it last changed, and which operator made the change.
Same state, four channels — web app, email, IVR DTMF menu, and REST API. Pick what fits the moment.
Four clean steps, every one of them governed and audited. No vendor lock-in, no developer ticket, no spreadsheet of admin emails.
Sign in with your authorized email and team PIN. A 6-digit code is sent to your inbox. Two-factor by construction.
Your dashboard shows the current Emergency and Closure state for your PIN — toggles, text, last-updated-by.
Flip a toggle or rewrite the message. Preview the TTS audio. Publish with one click.
Your contact center pulls the new value on the next call. Every action is logged to the audit trail.
Every minute counts when something changes for your callers. MSGManager turns what used to be a vendor support ticket into a self-service action.
Update the prompt the second a storm hits, a system goes down, or a public-safety event affects service.
Flip on the closure message at end-of-day, flip it off when offices reopen — without paging an engineer.
Tell callers exactly what's down, when it'll be back, and what to do — without retraining the IVR.
Schedule pre-recorded closure text the night before. Audit shows who scheduled what and when.
Update legal or regulatory disclosure language at the start of a call without re-publishing your flow.
Pre-stage holiday greetings and closure schedules. Toggle them on without a 6-week change-management cycle.
Every operator action — from the web app, an email, the IVR menu, or a direct API call — writes to a single immutable audit log. Sign in to your PIN and the most recent activity is the first thing you see.
MSGManager is a control plane, not a replacement. Your IVR keeps doing what it already does — it just gets fresh prompts every time a call lands.
Add a single HTTP Request activity at the top of your call flow.
Point it at https://api.msgmanager.com/v1/state/<PIN>
and bind the response to two flow variables — one for the toggle state, one for the message text.
The flow's decision activity branches on the toggle. The PlayMessage activity speaks the text. That's the whole integration. No SDK, no plugin, no flow re-architecture.
Wire MSGManager into anything — ticketing systems, ops dashboards, Slack bots, scheduled tasks. Bearer-token auth, per-PIN scoping, JSON in / JSON out.
Every action available in the UI is a single HTTP call. The same Bearer token that gates the web app can drive a PagerDuty webhook, a cron job, or your team's internal ops platform.
Calls are idempotent where it matters (toggle state), atomic where it counts (text updates), and audited universally. The data worker validates every request against the per-PIN trust list before any state changes.
curl https://api.msgmanager.com/v1/state/2876 \ -H "Authorization: Bearer $TOKEN" // → 200 OK { "pin": "2876", "team": "TSB", "emergency": { "on": true, "text": "Due to a water service...", "updated_by": "operator@your-team.com", "updated_at": "2026-05-15T22:30:00Z" }, "closure": { "on": false, "text": "Our offices are currently closed..." } }
curl -X POST https://api.msgmanager.com/v1/toggle/2876/emergency \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/json" \ -d '{"state": "on"}' // → 200 OK { "pin": "2876", "action": "toggle", "scope": "emergency", "before": "off", "after": "on", "audit_id": "a8f3c2e1-..." }
curl -X PUT https://api.msgmanager.com/v1/message/2876/emergency \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/json" \ -d '{"text": "Due to high call volume..."}' // → 200 OK { "pin": "2876", "action": "update", "scope": "emergency", "chars": 42, "audit_id": "b9d4f2a8-..." }
curl https://api.msgmanager.com/v1/audit/2876?limit=3 \ -H "Authorization: Bearer $TOKEN" // → 200 OK { "items": [ { "ts": "2026-05-15T22:30:00Z", "actor": "operator@your-team.com", "source": "web", "action": "update", "scope": "emergency" }, { /* ... */ } ] }
Every action passes through three independent gates before any state changes. Every change is captured in an immutable audit log. Every operator is scoped to exactly the PINs they own.
Email + PIN + 6-digit OTP delivered to the authorized inbox. Knowledge plus proof-of-control on every session.
Operators see and touch only the PINs they're authorized for. Cross-tenant access is blocked at the API layer, not by convention.
Every action — from any channel — recorded with who, what, when, before, after. Compliance-ready out of the box.
Pages, Workers, KV, Turnstile, DDoS protection — globally distributed, zero vendor sprawl, no single-region failure.
Cloudflare Turnstile on the login, per-IP and per-email rate limiting on every endpoint. Scripted attacks fail fast.
No assumptions about your industry, compliance posture, or naming. Drops cleanly into any contact center, any team.
A 30-minute walkthrough is all it takes to see your IVR's emergency and closure prompts under MSGManager governance. No code change to your contact center required.
Request a walkthroughWe sent a 6-digit code to your email. It expires in 5 minutes.