Start a test
1
Save your configuration
Save every tab you changed. Tests use the saved agent; they do not send unsaved editor content.
2
Open Test agent
Use the header button. The panel identifies the environment as Sandbox.
3
Write as a customer
Send a specific message, wait for the reply and continue. Also test incomplete information and requests for human support.
4
Inspect tools
Expand the simulated tool indicator to see names and arguments. The blocked-effect badge means the real action was blocked during the test.
5
Reset for another scenario
Use Reset to start without the previous conversation’s context. Save agent changes before testing again.
Read the panel
Test scenarios
Record the message, expected result and observed result. Repeat these scenarios after changing instructions, model or tools.
Test scope
The sandbox does not send customer messages through WhatsApp. A simulated tool does not confirm a CRM update, a real conversation transfer or an API response. The HTTP tool’s test request is different: it contacts the endpoint. Read Tools before using it.Common problems
Frequently asked questions
Does this test contact a customer?
Does this test contact a customer?
It does not send WhatsApp messages to customers. The panel uses a sandbox chat and displays simulated tools.
Can I test unsaved changes?
Can I test unsaved changes?
Save the tabs you changed first. The test uses the agent identifier and does not send the editor draft.
Does a successful test mean WhatsApp is ready?
Does a successful test mean WhatsApp is ready?
You still need a connected channel and a rule assigning conversations to the agent. See Channel settings.
How do I avoid carrying over previous replies?
How do I avoid carrying over previous replies?
Use Reset before the next scenario. This prevents previous conversation context from affecting the new test.