Skip to main content
When you change an agent that is already working with leads, the change does not reach them right away. It goes into a draft: a private copy of the agent that you and your team can edit and test. Your leads keep talking to the published version until you publish the draft.

How a draft starts

Your first change to a live agent opens its draft automatically. You don’t need to create it. Every later change, yours or a teammate’s, lands in that same draft.
  • One draft per agent. The whole team shares it. Two people can edit at the same time, and both sets of changes end up in the same draft.
  • The draft covers the whole agent: its tasks, stages, fields, instructions and prompts, tools, cadence, reminders, meeting types, knowledge and catalog selections, the files the agent can send, how new conversations reach a task, and its calls: who answers during business hours and after hours, your team’s number, the rings before the AI answers, and transfers by topic.
  • Agents still being set up save directly. If none of the agent’s tasks is live yet, there is nothing to protect: your changes apply right away, with no draft. The draft appears once at least one task is live.

Read the pill

The pill at the top of the agent’s chat shows where the agent stands.
The agent header with the pill reading Paused · Unpublished changes and the version history button next to it. Shown in the Spanish interface.
The agent header with an open draft: Unpublished changes and the See changes button next to it. Shown in the Spanish interface.

After each change

Every change that goes into the draft shows a notice: Saved to draft, not live yet. Choose See changes in the notice to open the review of the changes. Nothing is published until you confirm it there. See Publish the draft.
The notice Saved to draft, not live yet, with a Publish button.
In the agent list on the left, an agent with unpublished changes shows a Draft badge next to its name, so you can see which agents have changes waiting without opening them. The badge stays until you publish or discard the draft.
An agent in the agent list with the Draft badge next to its name.

Test the draft in the Playground

Open Test this agent. While a draft is open, the version selector in the Playground header reads Draft, and the Playground runs the draft, not the published version. Hover it to see the reminder: your leads still use the published version. The draft works on every test channel:
  • Chat in Nexor answers with the draft.
  • WhatsApp, iMessage, SMS and Email send real messages from the agent’s own number or address. Your replies come back to the draft, not to the published agent.
  • Call places a call from the agent’s number with the draft’s instructions.
If no draft is open, the selector shows the version your leads are using, for example v3 (Current). Choosing an older version from the same selector loads it into the draft so you can test it. See Go back to a previous version.
The Playground version selector reading Draft with its menu open: Draft selected, v2 (Current) and v1. Test inbound call appears below the channel options. Shown in the Spanish interface.

Test an inbound call

To check how the draft answers when a lead calls in:
  1. In the Playground, choose Test inbound call, below the channel options. It only appears while you test a draft.
  2. Enter the phone you will call from and choose Get the number.
  3. Call the number shown, which is the agent’s real number, from that phone within 15 minutes. The draft answers, and the conversation opens in the Playground.
The inbound call test form asking which phone you will call from, with Get the number and Cancel. Shown in the Spanish interface.
The agent needs a number with AI answering turned on. If that number forwards calls to a phone, turn call forwarding off before testing.

The draft’s voice

Calls on a draft always use the draft’s own voice, never the published one. The real calls of the published agent keep their voice until you publish. When you change the draft, its voice has to be prepared again before the next call test. You don’t need to do anything:
  1. In the Playground, choose Call or Test inbound call. Nexor starts preparing the draft’s voice while you enter your phone.
  2. The call starts as soon as the voice is ready. It can take a few minutes.
  3. To stop waiting, choose Cancel. The waiting call is dropped, and the voice keeps preparing so your next call starts sooner.
Once prepared, the voice is reused for every call test until you change the draft again. If a test chat switches to a call, for example when the agent offers to call you, the call waits for the voice the same way. The chat shows a line while the voice is being prepared, when the agent is calling, or when the call is cancelled and why: The same reasons appear when a voice error blocks activating a task (Fix this before activating) or publishing who answers incoming calls. When the fix is in a task, Open task opens it. In the incoming calls notice, Main agent or Sub-agents opens the setting to fix. A temporary error retries on its own, so there is nothing to fix. If the agent’s tools need to be republished, calls on the draft are turned off and the Playground says so. Republish the tools to test calls again.

Publish the draft

  1. In the agent header, choose See changes. Opening the review publishes nothing.
  2. Review Your changes. The review groups them under Agent and under each task, names the sections as they appear in Instructions, and shows task and knowledge folder names. Long instruction edits show only the passages that changed, and additions show as added text. Changes to how new leads reach a task appear under When a lead reaches out first. Internal IDs and priority numbers are not shown.
  3. Check the groups you want to publish. See Choose what to publish.
  4. Choose Publish. The parts you published use the new version for their next messages, and the publish becomes the next version in the history.
To close the review without publishing or discarding anything, choose the X.
The review opened from a task, under Your changes: Agent checked with a voice change, the open task checked with a line saying its description changed in production and that publishing replaces that change, a second task unchecked with This task stays in your draft, and a third task checked and locked because the open task uses it. Discard and Publish at the bottom.

Choose what to publish

Every group under Your changes has a checkbox, including Agent. What starts checked depends on where you open the review: Change the checkboxes, then choose Publish or Discard. Both act only on the checked groups. With nothing checked, both are turned off.
  • Unchecked groups stay in your draft. An unchecked task shows This task stays in your draft. An unchecked Agent shows The agent’s changes stay in your draft. The draft stays open, and the pill keeps showing Unpublished changes until you publish or discard them.
  • Other tasks keep their production edits. Changes someone made in production to a task you don’t publish are kept. Publishing one task never overwrites another.
  • You publish whole groups. You can’t pick single changes inside a group.
Every publish creates a new version, also when it covers only part of the draft.

Tasks that go together

Some groups can’t be published apart. The review checks and locks them, and says why under the name.
  • Required tasks. If a checked task, or a change under Agent, uses a task that exists only in the draft, that task is checked and locked: “task” uses this task, so you publish it too. or The agent uses this task, so you publish it too.
  • The agent’s instructions. When you change the agent’s instructions, the change also goes into every task that carries them. Those tasks and Agent go together. Checking one of them checks the others, and unchecking Agent unchecks those tasks. Each of those tasks shows It carries the agent’s instructions, so it goes with the agent. Their other edits go with them.

Conflicts

A conflict means a setting changed in production after the draft was created, and the draft changes it too. You don’t choose between them. Publishing uses your version. The task with the conflict says so in a line, for example: The description changed in production on October 30. Publishing replaces that change with your version. Choose See what changed to compare the production value with yours. To keep the production version, uncheck the task so it stays in your draft, or discard its changes. Conflicts show only for the groups you check. What the review can tell you: Publishing does not activate paused tasks. Tasks you created in the draft are published paused. Turn them on when they are ready.

Discard changes

To throw away some changes and keep the rest:
  1. Choose See changes and check the groups you want to discard.
  2. Choose Discard. In Discard the selected changes?, choose Discard to confirm, or Cancel to keep them.
The checked groups go back to how they are in production. A task you created in the draft is removed, and a task you deleted in the draft comes back. Unchecked groups keep their changes. If nothing is left in the draft, the draft closes. Leads are not affected. You can’t discard a group that a group you keep depends on. The group that depends on it says so: This task uses changes you selected to discard. Select it too, or keep those changes. or The agent uses changes you selected to discard. Select it too, or keep those changes. Tasks that carry the agent’s instructions are discarded only together with Agent. To discard the whole draft at once, open the version history next to the pill. On Draft in progress, choose Discard, then Discard agent draft. The agent stays on the published version. Parts you already published stay published when you discard what is left in the draft.

Version history

Every publish creates a new version: v1, v2, v3 and so on. Open the history with the clock button next to the pill. Each row shows the version, the date and who published it. A check marks the version your leads are using now.
The version history open below the pill: a draft in progress with Discard, and version 1.0 marked as current. Shown in the Spanish interface.
Choose a row to open the full list, with the draft in progress and every published version. Discarded drafts are hidden; choose Show discarded to see them.
The Versions panel with a draft in progress marked Not published and version 1 marked Current. Shown in the Spanish interface.
Open a version to see its timeline: who created the draft, who edited which section and in which task, who tested it in the Playground, who reviewed it and who published it. If it was published over changes made to the live agent in the meantime, the timeline says so. Choose View changes to compare line by line: removed text in red, added text in green, unchanged lines collapsed. In the draft and published versions, each change shows the setting’s name and the names of related tasks or knowledge folders. Changes to incoming leads appear under Channels. If a task or folder is no longer available, a generic label appears instead of its identifier.
A published version opened with its changes shown line by line: the removed instruction in red and the new one in green. Shown in the Spanish interface.

Go back to a previous version

  1. Open the version history and choose Restore on the version you want. You can also pick it in the Playground’s Version selector.
  2. If a draft is already open, confirm Replace draft. Its unpublished changes are lost.
  3. The version is loaded into the draft. Nothing changes for your leads yet.
  4. Test it in the Playground, then publish it. That publish creates a new version with the old content.
Versions published before the full history was kept can’t be restored. In that case, make the changes again by hand in the draft.

What is not part of the draft

These changes apply right away, even when a draft is open:
  • Turning a task on or off (Set live / Pause).
  • Moving a task to another agent. See Move a task to another agent.
  • Phone numbers, WhatsApp and iMessage lines, and other channel connections.
  • CRM connections and CRM flows.
  • Webhooks.
  • Deleting the agent.
Call settings are part of the draft. Publishing does not wait for them: they apply after it, and calls pick up the new settings within a minute or two. See When your changes reach calls. Numbers stay with the published agent. A task that exists only in the draft can’t get a WhatsApp number until you publish the draft. When the API or Nexor AI assigns a WhatsApp number to a task of the draft, the number goes to that task’s published version.

Move a task to another agent

Moving a task to another agent changes the live agents right away. It never goes into a draft. Nothing moves when the move is refused. Unbinding the task’s number means that number stops answering, also for the other tasks of its current agent that answer through it. Check that before you unbind it.

With Nexor AI

When you ask Nexor AI to change a live agent, the change goes into the same draft as your own edits, and Nexor AI tells you so. It also offers a link to test the draft in the Playground.
  • Publishing: after a change it saved to the draft, Nexor AI says the change is not live yet and offers, in one line, to publish it, with a short summary of what would change for your leads. It publishes only when you answer yes in your next message.
  • Renaming an agent: the new name applies to the live agent right away and also to its open draft, so publishing the draft keeps the new name.
  • Moving a task: Nexor AI moves the task on its own, apart from other changes, and the move applies right away. If a draft is in the way, it offers to publish or discard that draft first. If the task and the destination agent each have a WhatsApp number, it tells you which number would stop answering and unbinds it only after you say yes.
  • Versions: ask it to list the agent’s versions, compare them, discard the draft, or go back to a previous version. Going back follows the same steps: it loads the version into the draft, you test it, and Nexor AI asks before publishing.
  • If someone changed the draft or the live agent while you were talking, Nexor AI explains what changed and asks again.

With the API

Changes made with an API key or an MCP key apply to the live agent right away. Responses to these writes include saved_in_agent_draft. It is false when the change was applied to the live agent (every customer API key and MCP key). It is true only when NexorGPT saved the change to the agent’s draft; that change reaches calls when the draft is published. A task created with an API key or an MCP key while the agent has a draft open goes straight to the live agent. It shows in the agent’s task list next to the draft’s tasks, in its live state, and keeps working with leads. In the app you can turn it on or off, but to edit it, publish or discard the draft first. Publishing keeps the task as it is. Moving a task to another agent with master_workflow_id in Update an Agent applies right away too. It answers 409 with task_in_open_draft while either agent has a draft with unpublished changes, and with whatsapp_provider_assignment_lineage_change_requires_unassign when the task and the destination agent each have a WhatsApp number. Both responses name what is in the way.

Frequently asked questions

Will my leads see my changes while I test?

No. Leads keep using the published version until you publish. Tests in the Playground use the draft, on every channel.

Can two people edit at once?

Yes. The agent has one draft for the whole team, and every change lands in it. The version timeline shows who changed what.

How do I go back to a previous version?

Open the version history, choose Restore on that version, test the draft and publish it. See Go back to a previous version.

I published by mistake. What now?

Restore the version that was current before and publish it. Your leads switch back as soon as you publish.

Can I publish only one task?

Yes. Open the task and choose See changes. That task is checked, with Agent if it has changes and any task it requires. Uncheck Agent to leave the agent’s changes in the draft, unless the task carries the agent’s instructions. The other tasks stay in the draft. See Choose what to publish.

Can I discard only some changes?

Yes. In See changes, check what you want to throw away and choose Discard. Those parts go back to how they are in production, and the rest stays in the draft. See Discard changes.

Production changed a setting that my draft also changes. What happens?

Publishing replaces the production change with your version, and the task says so before you publish. To keep the production version, uncheck that task or discard its changes. See Conflicts.

Does publishing turn my agent on?

No. Publishing only changes the configuration. To start a paused task, use Set live.

Why can’t I move a task to another agent?

The agent the task leaves or the one it moves to has a draft with unpublished changes, or the task and the destination agent each have a WhatsApp number. Publish or discard the draft, or unbind the task’s number, then move the task. See Move a task to another agent.

Why didn’t my change open a draft?

Either the agent has no live task yet, so changes apply directly, or the change is one of the settings that are not part of the draft, such as turning a task on, moving a task to another agent or connecting a number, or it was made with an API key or an MCP key, which change the live agent.

Why do calls still sound like the old version?

Some voice agents take a few minutes to switch. The pill shows Propagating… until they do. A call already in progress keeps the version it started with.

Next

Test your agent

Talk to the draft as a lead on any channel before you publish.

Agent settings

Every setting you can change in an agent and its tasks.
Last modified on November 3, 2026