The Assistant Sandbox is a testing environment for your voice assistant’s
system prompt. You can tweak the prompt as you go and trigger web calls to try
it, and none of this changes your production assistant. It’s the fastest way to
fine-tune how your assistant behaves during a call.
Credits are deducted for sandbox calls. Sandbox calls are real calls, and
they use credits from your wallet the same way production calls do.
To open the sandbox, enter your Public Key, Private Key and Workspace credentials, then click the Validate button.
Sandbox authentication — enter your Public Key, Private Key, and Workspace ID to validate access.
Field
Description
Public Key
Your public API key
Private Key
Your private/secret API key
Workspace
The workspace identifier you want to work with
Once you’re authenticated, the sandbox loads your workspace data and every assistant configured in it.
2
Select an Assistant
A dropdown then lists every assistant in your workspace. Select the one you want to test.
Assistant selection — choose from all assistants configured in your workspace.
3
Review the Prompt & Configure
Once you select an assistant, the screen splits into two sections:
Sandbox main interface — system prompt on the left, payload and metadata on the right.
Left section: System Prompt & Variables
The assistant’s system prompt appears in an editable area, split into sections such as Context, Objective and Personality
Below the prompt is the list of allowed variables. The system generates these from the data you provide (e.g., customer name, order details, discount info)
You can only use these system-generated variables in your prompt
Right section: Configuration
Payload: a JSON text box where you paste the call payload data (e.g., customer info, cart details)
Metadata: a JSON text box where you paste any additional metadata for the call
Change Assistant: a button in the top-right that switches to a different assistant
4
Make a Call
Fill in the Payload and Metadata fields with your JSON data.
Optionally, edit the system prompt to test different conversation
behaviors.
Click the Test Assistant button to trigger a web call.
You’re connected to the assistant and can speak with it in real time.
5
Iterate & Refine
After each call, review how the assistant responded:
Modify the system prompt based on your findings
Adjust the Payload or Metadata as needed
Click Test Assistant again to test your changes right away
Repeat this cycle until the assistant behaves as expected.
6
Switch Assistants
To test a different assistant, click the Change Assistant button in the top-right corner. The assistant dropdown reappears so you can select another assistant from your workspace.
Prompt changes are not saved. Edits you make to the system prompt in the
sandbox are temporary and are not stored in the database. To keep a change,
update the assistant’s prompt through the dashboard or API.
Use only system-generated variables. The sandbox generates the allowed
variables from the data you provide. Custom or arbitrary variables are not
resolved during the call.
No events or actions in sandbox. Sandbox calls do not trigger webhook
events (such as call.ended, call.completed, end-of-call, action, etc.)
or actions (such as create-order, send-whatsapp). The sandbox is only for
testing prompt behavior and conversation flow.
Start with your production prompt. Select the assistant and test how it behaves now, before you make changes.
Change one thing at a time. Edit one part of the prompt per call, so you can tell which edit changed the assistant’s behavior.
Test edge cases. Vary your payload data (e.g., different product types, price ranges, customer profiles) to check that the prompt handles a range of scenarios.
Note your changes. Sandbox edits aren’t saved, so copy your final working prompt and apply it to your assistant configuration by hand.
Monitor your credits. Each sandbox call deducts credits, so plan your testing sessions with that in mind.
