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.

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.

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.

Test an inbound call
To check how the draft answers when a lead calls in:- In the Playground, choose Test inbound call, below the channel options. It only appears while you test a draft.
- Enter the phone you will call from and choose Get the number.
- 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 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:- In the Playground, choose Call or Test inbound call. Nexor starts preparing the draft’s voice while you enter your phone.
- The call starts as soon as the voice is ready. It can take a few minutes.
- To stop waiting, choose Cancel. The waiting call is dropped, and the voice keeps preparing so your next call starts sooner.
Publish the draft
- In the agent header, choose See changes. Opening the review publishes nothing.
- 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.
- Check the groups you want to publish. See Choose what to publish.
- Choose Publish. The parts you published use the new version for their next messages, and the publish becomes the next version in the history.

Choose what to publish
Every group under Your changes has a checkbox, including Agent. What starts checked depends on where you open the review:- 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.
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:Discard changes
To throw away some changes and keep the rest:- Choose See changes and check the groups you want to discard.
- Choose Discard. In Discard the selected changes?, choose Discard to confirm, or Cancel to keep them.
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.


Go back to a previous version
- Open the version history and choose Restore on the version you want. You can also pick it in the Playground’s Version selector.
- If a draft is already open, confirm Replace draft. Its unpublished changes are lost.
- The version is loaded into the draft. Nothing changes for your leads yet.
- Test it in the Playground, then publish it. That publish creates a new version with the old content.
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.
Move a task to another agent
Moving a task to another agent changes the live agents right away. It never goes into a draft.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 includesaved_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.