Skip to main content
Every agent has a Test menu in the editor header. Use it to talk to your draft in the browser, have the agent call your phone, or chat with it in text. Tests run your own draft, so you can try changes before anyone publishes them, and nobody else’s tests or calls change.

Before you start

  • You need the Call permission to start a test. Owners, admins and members all have it by default. See Roles and permissions.
  • Save your changes first. While the editor has unsaved changes, Test is disabled and its tooltip says “Please save changes before testing”.
  • For a phone call test, the agent needs a phone number. See Phone numbers.

Start a test

1

Open the Test menu

In the editor header, click Test.
The flow builder header with the Test menu open: Browser call, Phone call, Chat, Values from dev and Test valuesThe flow builder header with the Test menu open: Browser call, Phone call, Chat, Values from dev and Test values
2

Choose how to test

  • Browser call: talk to the agent through your computer’s microphone.
  • Phone call: enter Your phone number and the agent calls you.
  • Chat: the same agent in text, with the same prompts, tools and values.
3

Fill in dynamic variables, if asked

If the agent uses dynamic variables, a dialog asks for a value for each one before the call starts. Every variable needs a value.
The Phone call dialog with a UAE number in Your phone number and a value filled in for each dynamic variableThe Phone call dialog with a UAE number in Your phone number and a value filled in for each dynamic variable
4

End the test

Click End call, or end the chat from the chat panel.
Start or end a browser test call with Cmd+Shift+Enter on Mac or Ctrl+Shift+Enter on Windows. Start a test chat, or bring the open one back, with Cmd+Option+Enter on Mac or Ctrl+Alt+Enter on Windows.
If your browser blocks the microphone, the app says so. Allow the microphone for the site in your browser, and for your browser in your computer’s settings, then try again.

Chat with your agent

The chat opens in the panel beside the editor, so you can keep working while you chat. Type a message and press Enter to send it; Shift+Enter starts a new line. Each of the agent’s replies shows how long it took (“Replied in {seconds} s”), from the moment you sent your message to the reply.
  • Copy conversation copies the whole chat as text, one line per message (“You: …”, “Agent: …”).
  • Restart chat ends this chat and starts a fresh one with the same agent.
  • Logs shows the test’s logs, as for a call.
The Chat panel during a test chat: the agent's greeting, two questions and answers each marked Replied in 1.4 s and 1.1 s, and Copy conversation and Restart chat above themThe Chat panel during a test chat: the agent's greeting, two questions and answers each marked Replied in 1.4 s and 1.1 s, and Copy conversation and Restart chat above them

Choose which values your test reads

When an agent uses environment variables, each test reads the values of one environment.
  • With deployments on, the Test menu has Values from {env} (for example Values from dev). Pick another environment there to test against its values. “Only your tests change”: nothing is saved, and no colleague or real call is affected.
  • With deployments off, tests read the prod values.
The Test menu with Values from dev open, offering dev, staging and prodThe Test menu with Values from dev open, offering dev, staging and prod
If you are viewing a version that runs in more than one environment, the menu shows Choose whose values to test with. Pick one; until you do, test calls can’t start. You can also start a test from Releases: open an environment’s menu and click Test with this environment. See Environments and releases.

Use test values

Test values in the Test menu let you replace an environment’s values for your own tests of this draft. “Your tests of this draft use these instead of {env}‘s values. Nobody else’s tests change, and no environment does.”
1

Open Test values

Click Test > Test values.
2

Add a key and a value

Click Add a key, type the key, then its value. Each key shows whether it is “Not in {env} yet”, “Differs from {env}” or “Same as {env}”.
The Test values dialog with the key LOYALTY_API_URL marked Not in dev yet, its test value, and Save test valuesThe Test values dialog with the key LOYALTY_API_URL marked Not in dev yet, its test value, and Save test values
3

Save

Click Save test values. Your next test uses them.
Test values are also how you add a new environment variable without access to Releases: add the key here with a value, use it as {{KEY}} in a prompt or tool, and test. When your changes are merged, the person merging chooses which test values to add to the environment. See Merge requests. To stop using one, clear it. “Cleared. Your next test uses {env}‘s values.”

Follow a test while it runs

In the flow builder, the Live call logs panel shows what happens during the call: the conversation, step changes, tool runs and system events. Open it from the ⋯ menu in the editor header. Search the logs, filter by type (Error, Warning, Information, Debug) or Category, or export them.
Live call logs during a test call, filtered by node to Verify the order, with Follow canvas switched on and the Locate node button in the filter barLive call logs during a test call, filtered by node to Verify the order, with Follow canvas switched on and the Locate node button in the filter bar
While a call runs, the step it is in is highlighted on the canvas, and the log list scrolls so the latest line for that step stays in view. Your choice of Follow canvas and Open groups is kept in this browser, for every flow you open.
  • Every test call is saved with the agent’s other calls. Open Calls in the editor header to find it, then open it in call details. From there, Debug mode steps through the call on its flow, with its recording, visits and logs.

Test someone else’s merge request

Owners and admins can test a member’s merge request before merging it. Click Test on the request. A banner says “Test calls and chats run {name}‘s merge request, not your draft.” and its test values are used. Click Back to my draft to return to your own draft. See Merge requests.

Good to know

  • A test runs the agent’s draft as you saved it. Save before you test.
  • Test calls never see another member’s test values, and real calls never see test values at all.
  • Test calls are left out of A/B test comparisons.
  • Phone numbers aren’t part of a version. Changing which number the agent uses doesn’t need a publish.

Test values and undefined variables

Preview values in the editor and spot variables with no value.

Drafts and versions

Your private draft, publishing and version history.

Environments and releases

dev, staging and prod, and what each one runs.

Call details

Transcript, recording and debug mode for any call.