Use the AI Playground inside AI Agent Studio to simulate customer conversations, test your agent’s behavior, and personalize replies for a specific customer profile.
The AI Playground is the conversation simulator built into every agent edit screen in AI Agent Studio. Use it to sanity-check changes before they reach a real customer — type a question, watch how the agent replies, and see whether your latest brand information, personality, instructions, and skills produce the behavior you want.
Open the agent you want to test in AI Agent Studio.
On desktop, the AI Playground panel renders next to the editor on the right side of the screen.
On mobile and narrow screens, switch from Editor to Playground using the tab at the top of the page.
The Playground header reads AI Playground with a Reset conversation button. Below it, a Testing as card shows who you are chatting as (Guest by default) and a Select customer button.
Type a message in the Playground input as if you were a customer (for example, “Do you have this bag in black?” or “Recommend a shoe for running.”).
Confirm the agent’s reply matches the identity, instructions, and skills you configured.
Send several follow-up messages to walk through a realistic conversation, not just one turn.
Test the common golden paths first (product question, order tracking, FAQ) and then try edge cases (out-of-stock items, unsupported topics, intentionally vague questions). Issues usually show up at the boundaries, not in the happy path.
The Playground uses the currently saved identity, instructions, and skills for the agent. If you change a setting without saving, the Playground will not pick it up until you save.
Skill behavior (Create order, Order tracking, Product recommendation, Knowledge Base lookups, and similar) is exercised end-to-end, so tool calls hit real systems where they’re configured.
Custom skills and Escalation rules apply in the Playground the same way they apply to customers. When the agent hands the conversation to a specific agent, the Playground shows Conversation transferred to followed by that agent’s name.
A custom skill that runs a bitCRM automation does not start the automation from the Playground. The agent still decides to run it and replies as it would to a customer, so you can check when it triggers and what it says, but no automation runs.
The Playground is the right place to catch behavior regressions before going live; it is not a substitute for monitoring real conversations once you launch.