> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/ai-voice-agents/how-to-set-up-your-ai-voice-agent/voice-agent-settings-guide/speech-settings-responsiveness.md).

# Speech Settings - Responsiveness ⚡️

Control how instantly your AI responds after a user finishes speaking. This setting fine-tunes the AI’s reaction time, shaping the rhythm of conversation.

<figure><img src="/files/l8y1Uzt4KUVj7oKDWSLF" alt=""><figcaption></figcaption></figure>

• Lower values (closer to 0) insert intentional pauses.

• Higher values (closer to 1) generate quicker, snappier replies—ideal for fast-paced tasks like support or routing.

*Minimum: 0 (Slow, deliberate)*

*Maximum: 1 (Fast, immediate)*

*Recommended: 0.5–0.8 for natural, fluid responsiveness*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dapta.ai/ai-voice-agents/how-to-set-up-your-ai-voice-agent/voice-agent-settings-guide/speech-settings-responsiveness.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.