Publish your AI-agent
Publishing a AI-agent involves deploying AI-agent changes to the live environment. Only a Super Admin can publish a AI-agent for the first time. Each AI-agent environment will have a unique AI-agent ID. It's important to understand that database records will not automatically transfer to the live environment upon publication. They must be configured separately in both the development and live environments.
Only certain user roles can approve the AI-agent. To know about user roles in detail, click here.
To publish your AI-agent, it's mandatory to configure Fallback.
Publish chatbot to go live
To publish a AI-agent to live mode follow these steps:
-
Ensure the AI-agent is in Sandbox/Development mode. Go to Automation > Workflow builder > Publish.

-
In the following screen, fill in the following fields.
-
Click Configure more channels to configure further more channels to the AI-agent in the upcoming stage.
-
In Approvers, you will see the list of AI-agent approvers added by the Super admin. This cannot be modified. All the approvers will be notified when you raise a publish request.
-
In Comment, add a message to the approver citing the changes made in the AI-agent.
- Click Publish. The changes will move to Staging.
- Change your AI-agent environment to Staging, make changes (if any) and follow steps 1,2,3. The publish approval request will be sent to the Approver. AI-agents with only Development and Live modes need not do this. When you publish the changes, AI-agent sends the approval request to approvers.
To learn about different AI-agent environments (modes), click here.
Approve publish request
-
Users with Approver access(as provided by Super Admin) will receive an email with the content like the image below. Any one of them can approve, to approve click Review Request.

-
You will be redirected to the Bot approvals page. Click View request.
-
In the following screen, add a message to the approval requestor and click Publish.
What you are approving
A request raised through Publish selected items lists its scope on the request screen, split by kind and with a count on each row — Requested flows, Requested multi agents, Requested agents. Only the kinds actually in the request appear, so a request that lists Requested agents and nothing else publishes those agents and no flows.
A request that lists no scope at all is a full publish: everything in the AI-agent goes live.
Sub-agents are published with their parent agent, so approving a request may publish more agents than the Requested agents row names.
Publish selected items
Publishing selected items lets you release only the parts of your AI-agent that are ready, so you can observe results while continuing to refine everything else. You can pick individual flows, multi agents and single agents — anything you leave unselected stays on the version that is already live.
To publish selected items, follow these steps:
-
Go to Automation > Publish changes > Publish selected items.

-
In the pop-up, choose what to publish. The pop-up tells you what it covers: Choose which flows, multi agents and agents to publish. Everything else is published in full.
Field What it does Flows The flows that changed since the last publish. On a v3 AI-agent this picker is labelled Multi agent instead. Single agent The conversational agents that changed since the last publish. Shown only on AI-agents that have agents enabled. Approvers The approvers who will approve the publish. Read-only. Comment A message to the approvers describing what you changed. Required. Each picker is scoped to changes only, and its heading carries the count — for example, Flows (4 with changes). If nothing of that kind changed, the picker is disabled and reads No flows changed since the last publish. If you opened the pop-up from a flow you were editing, that flow is already selected for you.
noteLeaving a picker empty publishes none of that kind — an empty Single agent picker does not mean "publish all agents". You do need at least one item selected overall; otherwise the pop-up shows Select at least one item to publish.
infoOnly the items you select are published. Everything else — variables, APIs, databases and tools — is published in full, and references to items you did not select are removed. Sub-agents are published along with their parent agent, so a single-agent selection can carry more than the list shows.
-
Click Publish. The changes will move to Staging. Change your AI-agent environment to Staging, make changes (if any) and follow steps 1, 2, 3. The publish approval request will be sent to the Approver. AI-agents with only Development and Live modes need not do this. When you publish the changes, AI-agent sends the approval request to approvers. Click here to know about approving the publish request.
If the pop-up shows Couldn't load your changes, your list of changes failed to load — this is not the same as nothing having changed. Click Retry rather than falling back to a full publish.
- When you publish your AI-agent in the Sandbox, all the parts like flows, intents, entities, and AI-agent skins will also move to Staging and later to Production.
- You cannot pick and choose which parts go to Staging; everything you set up in Sandbox will go there when you publish.
- If you create something new in Staging that wasn't in Sandbox, you can publish it once. The next time you publish from Sandbox, anything you added exclusively in Staging will be lost and won't be in Production.
To learn about different AI-agent environments (modes), click here.
Cancel publish request
If you wish to make changes to the current flow/AI-agent, or if you've raised a publish request by mistake or prematurely before finalizing the end result, you can cancel the publish request by:
- Go to Publish changes > select Publish bot or Publish selected items (depending on the choice you made to raise the publish request).

- Click Cancel Request in the following screen.
Revert published changes
Revert option is a handy tool for fixing bugs in the live version. It lets you roll back to any previous version of your AI-agent. The Revert feature is available only in the live/production environment. Only Admins can have access to this option.
To revert changes:
-
Go to a AI-agent, ensure the AI-agent is in Live/Production mode and go to Automation > Build > Revert.

-
Select the version to which the AI-agent should be reverted.

-
Click Revert.
Decline publish requests
-
Users with Approver access(as provided by Super Admin) will receive an email with the content like the image below. Any one of them can decline, to decline click Review Request.

-
You will be redirected to the Bot approvals page. Click View request.
-
In the following screen, add a message to the approval requestor and click Decline.