Test the MAS

By the end of this page you will have driven your system end to end in the builder, and know how to fix a message that reaches the wrong specialist.

Prerequisites

• A system saved at least once (Builder tour).
• Two or more connected agents with skills (Connect agents).
• Admin or Developer role.

The preview panel

The right pane is a live chat against your saved configuration, headed Agent Preview. Its controls are:

• Clear chat — starts a fresh session. Use it between test cases so earlier turns don’t influence routing.
• Expand / Minimize — full-screen the conversation.
• Stop — appears while a reply is streaming.

Hide or show the whole pane with the preview toggle in the header.

Run a test

Ask something clearly in one specialist’s domain

Start with an easy case — a question only one member could answer. The reply is labelled with the agent that produced it, so you can confirm the routing at a glance.

Now ask about another domain

Ask something that belongs to a different member. This is the interesting case: the conversation should hand off, and — if Show transition message is on — you’ll see the transition line before the new agent answers.

Test a follow-up

If an agent asks you a question, answer it briefly — “yes”, or an order number. The turn should stay with the agent that asked, rather than being re-routed. That’s follow-up affinity at work.

Test the miss

Ask something no member covers. You should get your default action: either your custom message, or an attempt from the fallback agent.

Clear the chat and repeat

Click Clear chat before the next scenario, so each test starts from a clean session.

What else you’ll see

Because each turn is answered by a real agent, everything that agent does shows up in the preview:

• Tool activity — the tools it called while answering.
• Approval requests — if a member’s tool needs human approval, the approval card appears here and you can approve or reject it to let the run continue.
• Streaming replies — text arrives as it’s generated.

Tuning loop

When a message reaches the wrong specialist, work in this order:

1. Fix the skill. Sharpen the winning agent’s skill description, or add the failing phrasing to the right skill’s example queries. This solves most cases — see Connect agents.
2. Add a rule. If it’s a priority or tie-break that spans agents, add a line to the Router Prompt.
3. Pin the phrasing. Only if it’s still ambiguous, add a few-shot override on the agent that should win it.

Save after each change and re-run the failing message from a cleared chat.

Testing roles and data governance

Role impersonation lives in the AI Agent editor, not here. To verify that role-gated skills and row/column governance behave correctly, open the member agent itself and use Test as Role in its preview — see Test the agent.

A system preview always runs with your own roles, so any governance rules that apply to you apply here too.

Common issues

• “Save the router to enable preview.” — The system has never been saved. Click Save.
• The reply comes from the wrong agent — Work the tuning loop above, starting with the skill.
• Nothing happens when I send a message — The system has no members, or the member that was chosen has only a draft version and so can’t run. Publish the agent, then retry.
• A change had no effect — It wasn’t saved, or the message you’re testing skips classification (a greeting, or a single-member system).
• The conversation won’t move to the other agent — The current agent’s last reply ended in a question. Clear the chat and ask the second domain first.

Next

• Publish — turn the tested configuration into a version.