Skip to content

Communication

Nodes in the Communication section are used to hand a bot conversation over to an external operator or support service.

1. Chat Soon

Chat hands the current conversation over to an operator through the selected chat integration and ends the current bot flow.

Settings

Field Meaning
Provider Chat provider: Unitalk=0 or SmsBat=1
ChatIntegrationId Chat integration ID for the selected provider
Title Node title on the canvas

Connections

  • Input: one standard connector.
  • Outputs: none.
  • Chat is a terminal node, so no following node can be connected after it.
  • OnChatClosed is a separate entry point for a new flow after the operator chat is closed, not a connection from Chat.

How it works

When executed, the node attempts to open an operator chat through the selected integration.

The handoff is considered successful only after the external chat has been confirmed as opened.

Chat does not create its own variables and does not return a Screen or JSON.

Example

Condition "operator required"
  -> Chat

After the operator chat is closed, a separate flow can be started:

OnChatClosed
  -> Screen "Operator chat has ended"

Important details

  • Chat is a terminal node and has no outgoing connection.
  • If the integration is missing, disabled, uses the wrong provider, or cannot open the external chat, execution ends with an error.
  • Chat is not used in a synchronous AI tool because the terminal node does not return JSON.
  • The functionality is not yet available as a fully ready production handoff, so the node is marked as Soon.