Treat a saved draft and a published configuration as separate checkpoints. A draft gives you a place to prepare the conversation. Publication is the point to review what callers should experience.
Review before publishing
Check the configuration as a whole:
- The name identifies the correct agent and subscription.
- The greeting and instructions describe the intended job.
- Business knowledge is current and relevant.
- Any selected tools match the actions described in the instructions.
- Phone routing and the expected fallback are understood.
- The person responsible for follow-up knows what the agent may promise.
Use Agent instructions for a reusable brief and Phone setup and forwarding for routing preparation.
Save and check the result
Select Save draft in the agent editor and read the result shown by the console. If it reports a validation issue, resolve that issue before continuing. Reopen or review the saved settings to check that they match your intended configuration.
Do not use the mere absence of an error as proof that a change is published. Check the agent’s displayed state and any publication confirmation.
Publish deliberately
Select Publish when the configuration is ready. Read any validation messages and the resulting status. If the outcome is unclear, inspect the current state before trying again.
New configuration is intended for new calls; an edit is not a way to rewrite a conversation already in progress. Account readiness and phone routing are separate parts of reaching callers.
Inspect and compare saved versions
Open Agents → your agent → Configuration → Version history. The list identifies saved, published and previously published versions, with Current draft or Current published markers where applicable. Use Previous page, Next page or Refresh history when needed.
- Select the retained version you want to inspect.
- Choose Compare with to compare it with another retained version, or Latest saved draft or current published.
- Review Changed fields. Comparison version is the baseline; Selected version is the version you opened. Use View all fields for the complete retained values.
Comparison uses saved versions, not unsaved text currently in your editor. Opening or closing history does not save, publish or replace your editor changes.
A fictional revision A says “The team must confirm the requested visit.” Revision B says “The visit is booked.” Comparing them exposes the changed instruction; it does not establish that any real booking occurred. Check the welcome message, voice, maximum call duration, file collections and MCP tools as well as instructions.
Restore into a new draft
Select the version, choose Restore as draft and read the confirmation. Restoring creates a new saved draft containing the selected retained configuration. It leaves the original versions and current published configuration unchanged. It restores the configuration, not call records or an external business action.
If you have unsaved editor changes, the confirmation warns that they will be replaced. Cancel to keep them, or copy the text you need before deliberately restoring. After a confirmed restore, review the editor and version history, reopen the configuration to check persistence, then Publish separately if callers should use it. You do not need an extra Save merely to persist the restore.
| Message or condition | Next step |
|---|---|
| No retained versions / unavailable version | Inspect another retained version; absence is not an empty configuration. |
| Unavailable collection, connection or tool | Choose a compatible version or correct the current draft. Restore does not reconnect a service. |
| Historical selections not recorded precisely enough | Do not infer the old tool or collection selection. Review the currently supported choices. |
| Configuration changed in another session | Preserve unsaved text, use Refresh saved configuration, inspect the new state and compare again. |
| Restoration was not confirmed | The editor is unchanged. Check history and the saved configuration before another restore. |
Custom MCP servers explains tool versions and disconnected selections. Agent instructions explains how the instruction assistant saves revisions into this same draft history.
Keep a small change record
For each meaningful update, record what changed and the expected result in your own team notes. For example:
Change: Clarified that a preferred visit date is a request, not a booking.
Expected result: The agent says the team must confirm availability.
Review: Normal request, changed date and request for immediate confirmation.
After a change
Review available call information for the intended behaviour. If the agent gives an incorrect answer, identify whether the cause is an instruction, outdated knowledge or an action outcome. Correct that source and review the affected scenario again.
For an unclear state or a failed save, use Troubleshooting.