> 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/configure-conversation-clean-speech.md).
# Configure Conversation – Clean Speech
Normalize Text for Speech Synthesis
The Normalize Text for Speech Synthesis feature converts certain parts of the text (such as numbers, currencies, or dates) into their spoken form. This ensures more consistent speech synthesis, since TTS models can sometimes misinterpret text if it isn’t normalized.
For example, before generating the audio, the phrase:
> “Call my number 2137112342 on Jul 5th, 2024 for the $24.12 payment”
will be transformed into:
> “Call my number two one three seven one one two three four two on July fifth, twenty twenty four for the twenty four dollars twelve cents payment”
It’s important to note that this feature adds a small latency (approximately 100 ms) to the overall process.
***
#### Language Configuration
Currently, speech normalization is supported in the following languages:
* English
* Spanish
* French
* German
For other languages, this feature will not make any modifications to the text. If you select a non-multilingual language, the normalization will use that language’s rules (for example, “1” will be normalized to “one” if English is used). If you select the multilingual option, the system will automatically detect the appropriate language based on the generated text and normalize it accordingly.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.dapta.ai/ai-voice-agents/how-to-set-up-your-ai-voice-agent/voice-agent-settings-guide/configure-conversation-clean-speech.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.