Why we built ivrloom

The problem

For a lot of contact-center teams, changing an IVR means opening the Five9 IVR Script Designer — a desktop Java application that's slow to launch, can't make the same edit across multiple flows, and has an undo that you don't fully trust. A one-line prompt change can turn into an afternoon of clicking through windows, and a crash mid-edit can cost you the work. The tooling makes a routine change feel risky.

Our approach

ivrloom treats your IVR the way modern engineering treats code. You export a .zip from Five9, open it in a fast browser-based canvas, and edit visually — with reliable undo, search across every flow, and bulk changes that touch all of them at once. When you're done, every change is presented as a side-by-side, PR-style diff that you approve before you download the modified .zip to re-import.

Three principles shape every decision:

• Your IVR stays yours. The bundle is parsed and edited entirely in your browser. There's no backend endpoint that accepts your .zip, and AI and Cloud Save are strictly opt-in. Here's exactly what's sent, where, and why.
• AI proposes, you approve. The assistant reads your flow with real tools and stages edits as a reviewable diff — it can never apply a change you didn't tick. Turn it off entirely and ivrloom is still a full manual editor.
• Round-trip safety is non-negotiable. Node types we don't recognize are preserved byte-for-byte, so what you re-import into Five9 is exactly what you intended to change — and nothing else.

Where we're headed

Today ivrloom is focused on doing one thing well: making Five9 IVR edits fast, safe, and reviewable. Next on the roadmap is an optional connected tier that can push approved changes back to Five9 for you — offline-first stays the default, always — alongside deeper compliance and support for additional contact-center platforms through the same universal representation that powers the editor. We ship deliberately and write about the decisions on our blog.

Talk to us

We're building this in close contact with the admins who use it. If you run a Five9 IVR and something here resonates — or you think we've got it wrong — we want to hear it: [email protected].