Botmaker 3.0 lets you test your bot before putting it into production, review in Executions how it behaved in each conversation, and, when everything is ready, Publish the changes. When you test, you don't just see the final response: you see the orchestrator's reasoning step by step, which agent it routed each query to, and what stage of the process it's at.

You can:

• Test the complete bot from the orchestrator, in a simulated conversation.
• See the orchestrator's reasoning and which agent it routed each query to.
• Reset the context during the test to start from scratch.
• Review the conversation history in Executions, with its reasoning.
• Publish the changes and consult previous versions in History.

Key concepts

Test: open the tester to simulate a conversation with the orchestrator. Testing the orchestrator is equivalent to testing the complete bot.

Reasoning (events): the detail of the steps the orchestrator follows, visible inside the tester.

View details: an option inside the tester that shows which agent it routed to and what stage it's at.

Executions: the orchestrator's conversation history, with the reasoning of each one.

History: a record of published versions, to consult previous changes.

Publish: make the changes you made available in production.

How to test your bot

Step 1: Open the tester from the orchestrator

Go to the orchestrator and use the Test button, top right. Testing the orchestrator tests the whole bot. You can't test an agent separately; what you can test in isolation is a logic (within Tools/skills).

Step 2: Start the interaction

Start chatting as a user would. As you type, the orchestrator processes the messages and resolves the query by routing to the corresponding agents.

Step 3: Review the reasoning

In the tester you'll see the breakdown of the orchestrator's reasoning. With View details you see which agent it routed to and what stage of the process (Funnel state) it's at.

Note: during the test you can type @reset to clear the context and start over.

How to review Executions

Step 1: Open Executions

From the orchestrator or the agent, go to Executions: the conversation history and what happened in each one. When you open one, you'll see the reasoning the orchestrator followed, just like in the tester.

Note: the reasoning is shown in the tester and in Executions, not in the conversation the end user sees. Access to Executions is restricted to the project's authorized profiles.

Use the History and choose what to publish

By clicking "History" within each agent, you can view the project's previous versions. Once inside, you'll be able to view them in read-only mode (without needing to publish them) and choose which one to apply in development (to keep working) and which to apply in production. Keep in mind that if you click "apply in production," it replicates the "publish" behavior and becomes the agent that handles conversations.

Remember to visit our Help Center for further information.