Skip to main content
The Test Chat pane on the right of the builder runs a real conversation with the agent as currently configured — before a customer does.

​
What it runs

The Test Chat uses the version open in the builder, not the published one. That is what makes it useful: you are testing the edit, not the live agent. Each reply shows the model that produced it underneath, so you can see when the secondary model took over.

​
Test as a contact

WhatsApp agents. Optional.
Enter a phone number (e.g. 919876543210) in the box above the chat, and the agent loads that contact’s CRM record — so the agent and your functions see the real name, lead stage and attributes instead of an empty contact. Nothing is sent and nothing is saved. No message goes to that number, and the conversation is not written to the Inbox.
Test with a contact that has a filled-in record and one that does not. A brand-new contact has empty strings, not missing fields, and prompts that assume a name produce “Hi ,” for them.

​
What to test

The main thing the agent exists for, start to finish. Does it reach the outcome without being led there by you?
For each function, say the thing a customer would say and confirm the right function fires. A function that never fires in testing will never fire in production either.
Ask for an order status without giving an order id. The agent should ask for it, not invent one or call the function with a guess.
Ask something the agent is not meant to handle. It should decline and route, not improvise.
An angry message, a one-word reply, a message in another language, an attempt to talk it into a discount. You are checking that the boundaries in your prompt hold.
If Audio Transcription or Image Context is on, test that the agent handles those inputs. If they are off, check what it says when someone sends one anyway.

​
Testing the individual pieces

The Test Chat exercises the agent as a whole. Each function also has its own test path, which is faster for checking one thing:

​
Before publishing

1

Run the happy path once more on the final version

2

Test Send every media and template function

3

Check the follow-up settings

Especially the stop condition — an unattended message that ignores “not interested” is the one customers complain about.
4

Save, then publish

Publish ships the last saved version. Save first.

Versions and publishing

Test on a version, publish when it is right

Monitoring

Watching it once it is live