Agent Versions: Draft and Publish

Editing an agent no longer changes the agent that is answering calls right now. Your changes are saved automatically as a draft, and they only go live when you publish them. That means you can rewrite a prompt, swap a voice, or rewire a tool without a half-finished change ever reaching a real caller.

How it works

Every agent has two things at any moment:

• The live version — what real callers reach. Shown with a Live badge.
• Your draft — everything you have edited since the last publish. Shown with a Draft badge.

As you type, Dialora auto-saves your draft in the background. The header shows the save status, so you always know whether your work is stored. Older published versions are kept as Archived, so nothing you shipped is lost.

Step 1: Edit your agent

Go to Agents, open the agent, and change anything you like — Basic Settings, Advanced Settings, Widget, or Tools. There is no Save button to hunt for: edits are written to your draft automatically.

Step 2: Review what you changed

Click Publish. Before anything goes live, Dialora shows you a side-by-side summary of every difference between the live version and your draft — prompt changes, voice changes, tool changes, and configuration changes.

If this is a brand new agent, Dialora tells you it will be the first published version.

Step 3: Name and publish the version

Give the version a short name (required, up to 80 characters) and an optional description of what changed — for example, “Added after-hours transfer” or “Shorter greeting”. These labels are what you’ll scan later in the history, so make them meaningful.

Click Publish. Your live agent updates in one step.

Version history and comparison

Open History from the agent view to see every version of the agent, newest first, each with its version number, name, description, and status badge.

From there you can:

• Read the description of any past version to see why it was published
• Pick any two versions and Compare them side by side
• Choose which version is the base and which is the target, so the direction of the diff is exactly what you expect

Comparison is field-by-field, so you can see precisely which setting moved rather than guessing from a date.

Good practice

• Publish in meaningful chunks. One publish per intent (“new booking flow”) beats ten publishes of single-word prompt tweaks.
• Test before you publish. Use the Playground to talk to your draft first — see Test Your Agent.
• Write real version names. “v3” tells you nothing in three weeks; “Added Spanish + voicemail message” does.
• Check the diff every time. The publish summary is the last chance to catch an accidental edit.