Skip to main content

​
What is the Engine tab?

The Engine Tab controls the core performance settings of your voice AI agent. Fine-tune transcription accuracy, interruption behavior, response timing, and user presence detection for optimal conversation quality.
Engine Tab in Agent Studio showing a Response Latency card with Response Rate Custom, Endpointing 150 ms and Linear delay 250 ms, a Transcription & Interruptions card with the interruption word count set to 2, a User Online Detection card with English and Hindi message tabs, and Final Call Message and Call Management cards

Engine Tab with the Response Latency, Transcription & Interruptions, User Online Detection, Final Call Message and Call Management cards

​
Configuration options

​
Transcription & interruptions

Control how speech is captured and processed during conversations.
Transcription & Interruptions card with the Number of words to wait for before interrupting slider set to 2, beside the Response Latency card

Transcription & Interruptions card

Interruption threshold

Number of words to wait for before interrupting — how many words the user must say before the agent treats it as an interruption and stops speaking.
Stopwords like “Stop”, “Wait”, “Hold On” will always pause the agent immediately, regardless of the interruption threshold.

​
Response latency

Configure how quickly your agent responds to user input.
Response Latency card with Response Rate set to Custom, Endpointing at 150 ms and Linear delay at 250 ms, next to the Transcription & Interruptions card

Response Latency card with the Custom response rate sliders

The Endpointing slider only appears for transcribers that use it: Deepgram (except Flux models), ElevenLabs, Gladia, OpenAI and Gemini. Other transcribers, including Deepgram Flux, detect the end of a turn on their own, so the slider is hidden and a note under Response Latency explains why. Linear Delay still applies to every transcriber.
Lower latency isn’t always better! Setting values too low may cause the agent to interrupt users mid-sentence. Start with defaults and adjust based on testing.
For natural conversations, use Endpointing around 200-300ms and Linear Delay around 400-500ms.

​
User online detection

Detect when users go silent and automatically re-engage them.
User Online Detection card with the toggle enabled, English and Hindi tabs above a message box reading Hello, are you still there?, and an Invoke message after slider set to 8 seconds

User Online Detection card with the re-engagement message and timer

1

Enable Detection

Toggle User Online Detection to check if the user is still on the call.
2

Set the Message

Customize the prompt (e.g., “Hello, are you still there?”) per language using the language tabs.
3

Configure Timing

Set Invoke message after (seconds) to control when the check triggers.
Set the timer between 8-15 seconds to give users enough time to respond without seeming impatient.

​
Final call message & call management

Configure the last message your agent says before disconnecting, and how and when calls should end.
Final Call Message card with English and Hindi tabs, a closing message reading The call will now disconnect. Goodbye! and an Allow interruption toggle, beside a Call Management card with Hangup on User Silence enabled at 13 seconds and Total Call Timeout at 820 seconds

Final Call Message and Call Management cards

Final Call Message — select a language, write a warm closing (e.g., “Thank you for your time. Goodbye!”), and repeat for each language your agent speaks. Allow interruption lets the caller speak over the agent’s goodbye. When the agent decides the conversation is over and starts to say goodbye, a caller who cuts in with a last question (“wait, one more thing”) stops the goodbye, the hangup is canceled, and the conversation carries on. The agent can still end the call later. Off by default, so the goodbye plays through and the call ends.
Final Call Message card with the Allow interruption toggle switched on below the closing message, beside the Call Management card

Allow interruption switched on under Final Call Message

Allow interruption applies when the agent ends the call through Hangup using a prompt. Hangup on user silence, total call timeout, call transfers and voicemail hangups are never interruptible. A caller can reopen the conversation at most twice per call; after that the goodbye plays through.
Set reasonable timeouts to manage costs and prevent stuck calls. Very long calls can indicate issues or abandoned calls.

​
Best practices

Start with defaults

Use default settings initially and adjust based on real call feedback

Test extensively

Make test calls to experience the timing and interruption handling

Consider use case

Customer support may need longer pauses; sales may prefer faster responses

Monitor analytics

Review call recordings to identify timing issues

​
Next steps

Calling tab

Configure telephony and call features

Languages tab

Set up voice and transcription providers

Intelligence tab

Configure language model settings

Call history

Review call logs and recordings