Call settings control how an agent behaves in the audio stream — when it stops talking, how long it waits before responding, what it does when the line goes quiet. Defaults work well for most agents; reach for these when an agent talks over people, pauses awkwardly, or responds too eagerly.
All settings live on the agent’s Call Settings tab.
Interruptions and turn-taking
Silence handling
When the caller goes quiet, the agent checks in rather than sitting in dead air:
- Voice activity detection (VAD) — on by default, with a sensitivity slider. Higher sensitivity detects quieter speech but picks up more background noise.
- Silence message — what the agent says after a sustained silence. Use a static message (e.g. “Hey, are you still there?”) or have one generated from the conversation context so it fits naturally.
- If the caller still doesn’t respond after the check-in, the agent ends the call (the conversation record shows the silence timeout as the end reason).
Voice and audio
- Noise cancellation — on by default; filters background noise from the caller’s side before the agent hears it.
- Background audio — play ambient sound behind the agent’s voice to make the call feel like it comes from a real place. Options: none, city ambience, forest ambience, office ambience, crowded room — with a volume slider. Subtle office ambience makes long pauses feel less artificial.
Response timing
Presets (fast / medium / slow / custom) that trade snappiness against the risk of talking over the caller. Fast suits short transactional calls; slow suits conversations where callers think out loud.
Supporting LLM
For agents where every millisecond of response delay matters, you can enable a second, smaller LLM that generates a brief acknowledgement (“Sure, let me check that…”) while the main model composes the full answer. You choose its provider and model, set its temperature and token cap, and give it a filler instruction describing the kinds of acknowledgements it should produce. The result is an agent that never leaves a long thinking gap.
Change one setting at a time and re-test in the web-call playground. Interruption and endpointing settings interact — adjusting both at once makes it hard to tell which change helped.
