Multi-agent demos

Status: Preview | Last reviewed: 2026-09-18

Copilot components use the available Agent Assist cards. Studio checks their card selections, knowledge sources, forms and transcription before marking them built, so an empty or unsupported behavior remains visible as unfinished.

Choose Design with AI → Multi-agent demo when your demonstration needs more than one agent or audience. Describe the whole journey in one conversation. For example:

Help a customer understand a bill, let a supervisor approve an exception, and assist the representative if the customer asks to speak with a person.

The designer can propose:

Agent What it does
Voice Handles customer self-service
Supervisor Chat Lets a human supervisor review requests and return decisions
Agent Assist Copilot Helps the representative during the human-to-human call

Yes, Copilots support the human-to-human portion. They can suggest answers, coach, fill forms and summarize while the representative speaks. A supervisor Chat and a representative Copilot serve different people, so a demo can need both. Choose Copilot on the start screen for a standalone Agent Assist design.

The designer chooses the agents needed for your brief and asks about unresolved business decisions, such as which actions need approval. It uses native authentication, call ending and supervision capabilities. Multiple topics alone do not require multiple agents.

Review and build

Use the tabs beside the conversation:

Review the proposed journey, then choose Build demo. The designer creates ordinary drafts and checks every component and connection. A build can take up to 30 minutes. If interrupted, continue the saved build; completed work and existing agent IDs are reused.

Choose Open demo when the build finishes. You can then open individual components in their normal editors. Editing a component means the demo needs to be checked again before its next preview.

Try the experience

Start the customer call in Preview, then open its supervisor conversation. The supervisor sees the related interaction and can respond to requests. Human approval must come from the supervisor, and must apply to the current request. For a customer Chat component, choose Start customer chat in Preview.

For the representative segment, open the representative preview. Its native Copilot tester supports a voice stand-in for rehearsals. In a real demonstration, connect the Copilot to the human-to-human call using your normal Agent Assist integration. The Copilot itself does not speak to the customer.

The preview shares fictional sample inputs. Your connected phone system still routes the caller and delivers the handoff context. Preview does not create a phone route or automatically bridge the self-service call into the Copilot tester. Check transfer and summary continuity on your configured channel.

Record what happened

Run the scenarios in Validate, including rejected approvals, unanswered requests and calls that end while approval is pending. Enter what you observed and choose Record pass or Record failure.

Saved examples and build checks do not mean a live scenario passed. Journey results remain Not run until you record evidence. Changes to the design or its components invalidate results for the previous version.

Building and opening a demo do not publish its agents. Review and publish each component through its normal release process, including updating connections to the intended published versions.