> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/platform/settings/voice.md).

# Voice

Voice settings apply across all your agents. Configure them at [**Settings > Voice**](https://app.spara.co/settings/voice/configuration).

## Pronunciations

On the [**Settings > Voice**](https://app.spara.co/settings/voice/configuration) tab, you can add custom pronunciations that apply to every Voice agent in your account. Each entry serves two purposes:

* **Controls how the agent speaks the word.** The pronunciation drives text-to-speech, so "SQL" → "sequel" or "kubectl" → "kube control" make the agent say specialty terms correctly.
* **Strengthens how the agent hears the word.** The source term is also added to the speech-to-text key term list, biasing recognition toward that word. This is especially helpful for specialty terms that sound like common English words. For example, mapping "Paychex" → "Paychecks" both makes the agent pronounce the product correctly and helps the model transcribe "Paychex" instead of "Paychecks" when a caller says it.

Add an entry for any product name, person name, acronym, or industry term that voice agents need to say or hear reliably. Pronunciations apply org-wide to every Voice agent. There is no per-agent override today.

<figure><img src="/files/tKfEf2ajYUzJ8uxyFvkJ" alt=""><figcaption><p>The Pronunciations panel on Settings > Voice, showing example entries that apply to every Voice agent.</p></figcaption></figure>

{% hint style="info" %}
Use phonetic spelling: spell the word the way it should sound, and use spaces to separate syllables or letters (for example, "A P I" for the acronym "API").
{% endhint %}


---

# 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.spara.com/platform/settings/voice.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.