Skip to main content

Application Inputs

Voice-enabled applications often need to react to events beyond user speech. For instance:

  • A user pauses for too long, requiring a prompt to keep the conversation going
  • An external notification or system event which must be conveyed during a voice conversation

To handle these scenarios, the application can send an AddInput message to the Flow system. This allows non-verbal or system-driven inputs to be injected into the conversation dynamically.

{
  "message": "AddInput",
  "input": "<string>",                // Required: The input text to be incorporated
  "interrupt_response": "<boolean>",  // Optional: If true, interrupts the current response (default: false)
  "immediate": "<boolean>"            // Optional: If true, processes the input immediately after the current turn ends (default: false)
}

Application Input variables

  • input - The information that the LLM must incorporate in the response
  • interrupt_response - Setting this to true interrupts the current ongoing turn to vocalise the new information
  • immediate - Setting this to true ensure that the LLM treats this information as priority but does not interrupt current turn. Setting this to false lets Flow decide when to incorporate the information

API reference