Skip to content

External Voice Bot

In this section, we will explore the External Voice Bot feature of Buzzeasy. External Voice Bots enable you to bring your own voice participant (bot) solution to interact directly with customers within the Buzzeasy system.

How it works

The workflow reaches the External Voice Bot node. The system sends a SIP INVITE to the configured external endpoint. Once the external bot answers, it is conferenced into the call with the customer. The external bot and the customer communicate directly via voice in real time.

When the interaction is complete, the external system has two options to leave the call:

  1. SIP disconnect (BYE) The bot ends the call using standard SIP signaling (sending a BYE request). In this case, the call leg is terminated immediately, and the workflow continues based on the configured post-node behavior.

  2. API-based exit (MCP / JSON-RPC) The bot calls a dedicated API (MCP server using JSON-RPC) to signal that it wants to exit the interaction. This method allows the bot to:

  • Gracefully leave the call
  • Pass back updated workflow data (key-value pairs)
  • Provide a transcript of the interaction

After the API call is processed, the system removes the bot from the call and resumes the workflow with the provided data.

This dual-exit mechanism gives you flexibility: use simple SIP signaling for straightforward scenarios, or the API-based approach when you need to return structured data and context back into the workflow.

Adding External Voice Bot to your Workflow

In order to setup new SIP trunks please contact us.

Navigate to the workflow editor in the Buzzeasy portal. Add a new External Bot node to your workflow. Inside the node, select the trunk selection group which targets the SIP endpoint of your bot then provide a phone number (this can be anything that helps your system to identify which bot has been requested).

Remember, you can add multiple Custom Bot nodes in a single workflow, and each node can be configured to use a different External Bot. This allows you to create complex workflows that use multiple bots to handle different parts of a conversation.