Skip to main content

The Open conversation button

On every view of the bot editor (Agents, Voice, etc.) there’s a fixed toolbar on the right edge of the screen. The first icon, Open conversation, opens a chat panel that lets you talk to the bot directly. Open conversation button in the floating toolbar
In Draft Mode, the same toolbar has two more buttons — Deploy and Reset from production — to publish your changes or discard them.

What it’s for

  • Verify changes in real time — test the effect of an instruction change without leaving the editor or launching a test campaign.
  • Test the flow between agents — walk through agent handoffs to verify the conditions work as expected.
  • Review the LLM’s responses — check that the agent responds correctly to different scenarios before publishing to Production.

Simulate the bot’s variables before testing

Before the conversation starts, you’ll see an Initial Parameters panel: an editable name/value table where you can manually load the variables that would normally come from the campaign file (contact name, debt amount, due date, etc.). Open conversation's Initial Parameters panel, with preloaded variables This lets you simulate different scenarios without needing to launch a real campaign:
  • Add or remove parameters with Add parameter / Remove.
  • Edit the value of any existing variable (for example, test what happens if pago_minimo is 0 instead of a real amount).
  • The bot uses those values exactly as loaded — the initial greeting, the agent handoff conditions, and any {variable} in the Instructions are resolved with this data.
Once you send the first message, the panel collapses into a summary (“Initial parameters (N)”) and the conversation starts normally. Test conversation in progress using the simulated parameters

Which version it tests

When you open the conversation, you test the bot’s version in the active mode — whichever one is selected in the Production/Draft dropdown. If you’re in Draft, you test the draft. If you’re in Production, you test production.
Always make sure you’re in Draft when testing changes you don’t want to publish yet.