The Conversational Flow Layer in Tavus gives you precise control over the natural dynamics of conversation. This layer allows you to customize how your replica handles turn-taking and interruptions to create conversational experiences that match your specific use case.Documentation Index
Fetch the complete documentation index at: https://docs.tavus.io/llms.txt
Use this file to discover all available pages before exploring further.
Understanding Conversational Flow
Conversational flow encompasses the subtle dynamics that make conversations feel natural:- Turn-taking: How the replica decides when to speak and when to listen
- Interruptibility: How easily the replica can be interrupted by the user
All conversational flow parameters are optional. When not explicitly configured, the layer remains inactive. However, if you configure any single parameter, the system will apply sensible defaults to all other parameters to ensure consistent behavior.
The replica’s greeting is always non-interruptible, regardless of
replica_interruptibility. These settings only take effect after the greeting completes.Configuring the Conversational Flow Layer
If you’re migrating from sparrow-0 (formerly called
smart_turn_detection on the STT Layer) then check out the migration guide here.layers.conversational_flow object. Below are the parameters available:
1. turn_detection_model
Specifies the model used for detecting conversational turns.
-
Options:
sparrow-1(default): Advanced turn detection model - faster, more accurate, and more natural (recommended)sparrow-0: Legacy turn detection model (API-only, not actively supported)timebased: Simple time-based turn detection (API-only, not actively supported)
-
Default:
sparrow-1
2. turn_taking_patience
Controls how eagerly the replica claims conversational turns. This affects both response latency and the likelihood of interrupting during natural pauses.
- Options:
low: Eager and quick to respond. May interrupt natural pauses. Best for rapid-fire exchanges or customer service scenarios where speed is prioritized.medium(default): Balanced behavior. Waits for appropriate conversational cues before responding.high: Patient and waits for clear turn completion. Ideal for thoughtful conversations, interviews, or therapeutic contexts.
low: Fast-paced customer support, quick information lookups, casual chatmedium: General purpose conversations, sales calls, presentationshigh: Medical consultations, legal advice, counseling sessions
3. replica_interruptibility
Controls how sensitive the replica is to user speech while the replica is talking. Determines whether the replica stops to listen or keeps speaking when interrupted.
- Options:
low: Less interruptible. The replica keeps talking through minor interruptions.medium(default): Balanced sensitivity. Responds to clear interruption attempts.high: Highly sensitive. Stops easily when the user begins speaking, maximizing user control.
low: Educational content delivery, storytelling, guided onboardingmedium: Standard conversations, interviews, consultationshigh: User-driven conversations, troubleshooting, interactive support
4. voice_isolation
Voice isolation separates speech from background noise in the participant’s microphone audio. It is enabled by default for improved audio quality and can be disabled if needed.
- Options:
near(default): Separates speech from background noise for scenarios where the user is less than 1 meter away from the microphone.off: No voice isolation model is used. The raw audio is sent down the conversational pipeline.
5. wake_phrase
A specific phrase the persona listens for before responding. When set, the persona remains silent until it hears the wake phrase, similar to how voice assistants like Siri or Alexa work.
- Type:
string - Default:
None(disabled)
- The persona stays silent and does not respond until it hears the specified wake phrase.
- The persona still “hears” everything that is said. All user utterances are recorded in the transcript so the persona has full context when it does respond.
- Once the wake phrase is detected, the persona responds using the full conversation history, including anything said before the wake phrase was triggered.
6. idle_engagement
Controls whether the replica proactively re-engages the user after a stretch of silence, and how eagerly.
- Options:
off(default): The replica never breaks silence — it only speaks in response to user input.patient: The replica re-engages after longer silences. Suited to tutors, coaches, or contemplative use cases where users may need time to think.eager: The replica re-engages after shorter silences. Suited to SDR or sales-style conversations where keeping momentum matters.
off: General conversational use cases where the user always drives the next turnpatient: Tutoring, coaching, therapy, interviewseager: Outbound sales, SDR, qualification calls
idle_engagement is independent of turn_taking_patience. Turn-taking patience controls how quickly the replica responds after the user finishes speaking; idle_engagement controls whether the replica proactively breaks an extended silence.Default Behavior
When the conversational flow layer is not configured, all parameters default toNone and the layer remains inactive. However, if you configure any single parameter, the system automatically applies the following defaults to ensure consistent behavior:
turn_detection_model:sparrow-1turn_taking_patience:mediumreplica_interruptibility:mediumvoice_isolation:nearwake_phrase:Noneidle_engagement:off
Example Configurations
The following example configurations demonstrate how to tune conversational timing and interruption behavior for different use cases. Useturn_taking_patience to bias how quickly the replica responds after a user finishes speaking. Set it high when the replica should avoid interrupting, and low when fast responses are preferred. Use replica_interruptibility to control how easily the replica recalculates its response when interrupted; lower values are recommended for most experiences, with higher values reserved for cases where frequent, abrupt interruptions are desirable. Sparrow-1 dynamically handles turn-taking in all cases, with these settings acting as guiding biases rather than hard rules.
Example 1: Customer Support Agent
Fast, responsive, and easily interruptible for customer-driven conversations:Example 2: Medical Consultation
Patient, thoughtful, with engaged listening for sensitive conversations:Example 3: Educational Instructor
Delivers complete information with minimal interruption, and gently re-engages the user after long pauses for thought:Example 4: Minimal Configuration
Configure just one parameter—others will use defaults:turn_detection_model:sparrow-1replica_interruptibility:mediumvoice_isolation:near
Best Practices
Match Flow to Use Case
Choose conversational flow settings that align with your application’s purpose:- Speed-critical applications: Use
lowturn-taking patience andhighinterruptibility - Thoughtful conversations: Use
highturn-taking patience - Important information delivery: Use
lowinterruptibility - User-controlled interactions: Use
highinterruptibility
Consider Cultural Context
Conversational norms vary across cultures. Some cultures prefer:- More overlap and interruption (consider lower commitment, higher interruptibility)
- Clear turn-taking with pauses (consider higher patience, lower interruptibility)
Test with Real Users
Conversational flow preferences can be subjective. Test your configuration with representative users to ensure it feels natural for your audience.Refer to the Create Persona API for the complete API specification and additional persona configuration options.

