Conversation flow

Configure how your assistant handles timeouts, interruptions, and turn-taking during conversations.

Overview

Conversation flow settings determine how your assistant handles periods of user silence, interruptions during speech, and turn-taking behavior. These settings help create more natural conversations and can be customized based on your use case.

Timeouts

Timeout handling determines how long your assistant will wait during periods of user silence before prompting for a response.

Configuration

Timeout settings can be configured in the agent’s Advanced tab under Turn Timeout.

The timeout duration is specified in seconds and determines how long the assistant will wait in silence before prompting the user. Turn timeouts must be between 1 and 30 seconds.

Example timeout settings

Timeout settings

Choose an appropriate timeout duration based on your use case. Shorter timeouts create more responsive conversations but may interrupt users who need more time to respond, leading to a less natural conversation.

Best practices for timeouts

  • Set shorter timeouts (5-10 seconds) for casual conversations where quick back-and-forth is expected
  • Use longer timeouts (10-30 seconds) when users may need more time to think or formulate complex responses
  • Consider your user context - customer service may benefit from shorter timeouts while technical support may need longer ones

Interruptions

Interruption handling determines whether users can interrupt your assistant while it’s speaking.

Configuration

Interruption settings can be configured in the agent’s Advanced tab under Client Events.

To enable interruptions, make sure interruption is a selected client event.

Interruptions enabled

Interruption allowed

Interruptions disabled

Interruption ignored

Disable interruptions when the complete delivery of information is crucial, such as legal disclaimers or safety instructions.

Best practices for interruptions

  • Enable interruptions for natural conversational flows where back-and-forth dialogue is expected
  • Disable interruptions when message completion is critical (e.g., terms and conditions, safety information)
  • Consider your use case context - customer service may benefit from interruptions while information delivery may not

Turn eagerness

Turn eagerness controls how quickly your assistant responds to user input during conversation. This setting determines how eager the assistant is to take turns and start speaking based on detected speech patterns.

How it works

The assistant now includes two key improvements for more natural turn-taking:

  1. Faster response generation - The assistant starts speaking after receiving enough words and a comma from the language model, rather than waiting for complete sentences. This reduces latency and creates more responsive conversations, especially when the assistant has longer responses.

  2. Configurable turn eagerness - Control how quickly the assistant interprets pauses or speech patterns as opportunities to respond.

Configuration

Turn eagerness can be configured in the dashboard Agent settings or via the API. Three modes are available:

  • Eager - The assistant responds quickly to user input, jumping in at the earliest opportunity. Best for fast-paced conversations where immediate responses are valued.
  • Normal - Balanced turn-taking that works well for most conversational scenarios. The assistant waits for natural conversation breaks before responding.
  • Patient - The assistant waits longer before taking its turn, giving users more time to complete their thoughts. Ideal for collecting detailed information or when users need time to formulate responses.

Turn eagerness is especially powerful when combined with workflows. You can dynamically adjust the assistant’s responsiveness based on context—making it jump in faster during casual conversation, or wait longer when collecting sensitive information like phone numbers or email addresses.

Best practices for turn eagerness

  • Use Eager mode for customer service scenarios where quick responses improve user experience
  • Use Patient mode when collecting structured information like phone numbers, addresses, or email addresses
  • Use Normal mode as a default for general conversational flows
  • Combine with workflows to dynamically adjust turn eagerness based on conversation context
  • Test different settings with your specific use case to find the optimal balance
  • Shorter timeouts (5-10 seconds) for responsive interactions - Enable interruptions to allow customers to interject with questions - Eager turn eagerness for quick, responsive conversations
  • Moderate timeouts (10-15 seconds) to allow users time to gather information - Enable interruptions for natural conversation flow - Patient turn eagerness when collecting phone numbers, addresses, or email addresses
  • Longer timeouts (10-30 seconds) to allow time to think and formulate responses - Enable interruptions to allow students to interject with questions - Patient turn eagerness to give students adequate time to respond