Skip to main content

What is Silence Tolerance?

During a conversation, users may pause for various reasons:
  • Thinking about their response
  • Distracted by something
  • Unsure how to proceed
  • Technical issues with the call
Silence Tolerance settings control how long the agent waits before taking action.

Key Timers


How It Works


The Silence Tolerance property on each step controls silence tolerance behavior:

When to Use Each Setting

Hurried (Default)

Best for:
  • Simple questions with quick answers
  • Confirmations and acknowledgments
  • Fast-paced conversations
Example: “Is Tuesday at 2pm okay?”

Patient

Best for:
  • Questions requiring some thought
  • When users might need to check something
  • Multi-part answers
Example: “What challenges are you facing with your current process?”

Extremely Patient

Best for:
  • When users need to look something up
  • Fault finding or troubleshooting scenarios
  • When users might need to consult others
Example: “Can you check the serial number on the back of the device?”

Infinite

Best for:
  • Situations where users may need extended time
  • When you don’t want to interrupt at all
  • Calls where users explicitly need to step away
Note: Infinite silence tolerance is still limited by the maximum call duration. See Settings for call duration configuration.

Silence Prompts

When the response delay expires, the agent prompts the user to re-engage:
The re-engagement prompt fires once per quiet period. If it is cancelled before the caller ever hears it — because the assistant was interrupted, or the call was busy doing something else — it is re-armed and spoken as soon as it can be, rather than being counted as already said. Silence tolerance is applied per step, so each step waits for as long as its own setting says.

Interaction with Other Settings

Silence tolerance works alongside other dynamics:

Best Practices

  1. Configure per step — Set silence tolerance on each step based on the expected response
  2. Match complexity to tolerance — Complex questions need higher tolerance
  3. Consider your audience — Elderly users may need more time
  4. Test realistic scenarios — Try with actual users, not just ideal cases

Next Steps