How to edit a Five9 IVR script in your browser

Before you start

You need two things: access to export IVR scripts from your Five9 admin console, and a browser. There is nothing to install — no Java runtime, no desktop app, no admin rights on your machine. ivrloom never connects to Five9 and never asks for your Five9 credentials, so there is no integration to set up and no permission for anyone to grant.

If you don't have an export handy, you don't need one yet — the app ships with a sample IVR, and the live demo runs without an account.

The round trip, step by step

1. 01

   Export the bundle from Five9

   In the Five9 admin console, use IVR Scripts to export a .zip. That file is the whole unit of work — every script in it, plus the prompt audio. ivrloom never asks for Five9 credentials and has no API integration, so this export is the only handoff.

2. 02

   Drop it into a project

   Create a project and drag the .zip onto the dropzone. It is unzipped and parsed in your browser — in a Web Worker, so a large bundle with dozens of scripts and audio files doesn't freeze the tab. A single .five9ivr or .xml script works too if you only need one flow.

3. 03

   Edit — by hand, in bulk, or by asking

   Click any node to edit its properties. Press ⌘K to search every node and run commands, or ⌘⇧F for find & replace across all flows at once. Undo and redo work the way you expect. The AI panel can propose larger refactors, but it only ever proposes — nothing is applied until you approve the diff.

4. 04

   Check your work before it's real

   The Issues panel flags unreachable nodes, dead ends, and missing prompts. The simulator places a call against the flow: queue DTMF digits, step node by node, and read the trace. Save a run as a scenario and it re-runs after later edits, so a change that breaks a path you already tested tells you immediately.

5. 05

   Review the diff, then download

   Review changes shows a PR-style diff of exactly what you altered, node by node. Approve it and download the modified .zip. Node types ivrloom doesn't model are preserved byte-for-byte, so nothing is silently rewritten on the way out.

6. 06

   Re-import in Five9

   Import the downloaded .zip in the Five9 admin console the same way you exported it. Nothing in your live IVR changed until this moment — the entire edit happened on a copy.

Making the same change everywhere

This is the part that takes an afternoon in the Five9 IVR Script Designer, because it edits one flow at a time. Renaming a prompt, repointing a skill, or updating a business-hours check across thirty flows means opening thirty flows.

In ivrloom the bundle is one object, so a change can cross it. Find & replace (⌘⇧F) works across every script at once. For anything that needs judgement rather than a literal match, describe it to the AI panel — it reads the flows with real tools and comes back with a diff. It cannot apply anything itself; you review the change list and approve it, exactly as you would a manual edit. See the side-by-side comparison for the full list of differences.

Working with other people

Offline editing is single-player by design and needs nothing from us. If you'd rather not pass .zip files around, Cloud Save puts a project on our servers so you can share it with viewers or editors, keep a history of saved versions, and open a pull request against one — a diff with comments that someone else approves and merges. It's opt-in per project; pricing covers which plans include shared workspaces and seats.

Common questions

Do I need a Five9 export to try ivrloom?

No. There's a sample IVR built in — click "Try a sample IVR" in a new project, or open the live demo with no signup at all. Bring your own bundle when you're ready.

What file types can I open?

A .zip bundle exported from Five9 (the normal case — this carries every script plus prompt audio), or a single .five9ivr / .xml script on its own.

How long does a large bundle take to open?

Parsing happens locally, so it depends on your machine rather than our servers — but it runs off the main thread, so the tab stays responsive while it works.

Can I stop mid-edit and come back?

Yes. Work in progress is kept in your browser's local storage, so closing the tab doesn't lose it. Cloud Save is opt-in and stores the project's IR JSON on our servers so you can pick it up on another machine, share it, or open a pull request against it.

What if I make a mistake?

Undo and redo cover the whole session. Beyond that, nothing you do in ivrloom can affect Five9 — you're editing an exported copy, and your live IVR is untouched until you choose to re-import.

Does my IVR leave my browser?

Not by default. Two features opt in explicitly: AI assistance (your prompt plus the relevant slice of the flow) and Cloud Save (the project's IR JSON). The Security & Privacy page has the specifics.

More in the full FAQ, or email [email protected] — a human reads every message.