> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Pronunciation

> Prepare difficult terms and review pronunciation dictionary and phoneme settings against the selected speech model.

Names, acronyms, and product codes often need a pronunciation review. Keep a short list of terms and their intended spoken forms before changing speech settings.

<Note>
  Threetone exposes pronunciation-related authoring fields, but this guide does not provide a verified dictionary-creation workflow or live pronunciation execution. Voice publication remains unavailable.
</Note>

## Review the supported fields

The following fields belong to `conversation_config.tts`.

| Field | Authoring meaning |
| - | - |
| `pronunciation_dictionary_locators` | List of dictionary references. Each reference requires `pronunciation_dictionary_id` and may include `version_id`. |
| `enable_phoneme_tags` | Requests phoneme-tag support for a compatible model; defaults to `false`. |
| `model_id` | Determines which pronunciation capabilities and options are accepted. |

Check the selected model's `supports_pronunciation_dictionaries` and `supports_phoneme_tags` capabilities in [Get available AI model](/api-reference/agents-platform/get-available-ai-model). Support for one does not imply support for the other.

## Prepare a pronunciation review

<Steps>
  <Step title="Collect ambiguous terms">
    Include organization names, abbreviated titles, alphanumeric identifiers, and words with different regional pronunciations. Record their intended meaning as well as how they should sound.
  </Step>

  <Step title="Use complete example sentences">
    Put each term in a sentence the agent is likely to say. Include a plain-language fallback, such as spelling a short code when a listener asks for clarification.
  </Step>

  <Step title="Reference only known resources">
    If you have an accessible dictionary identifier, review its intended version before adding a locator to a [server draft](/agents-platform/deploy/versioning). Do not invent dictionary IDs or assume a public creation endpoint exists.
  </Step>

  <Step title="Keep listening verification pending">
    Read the saved draft back to confirm the references and model. Verify the actual pronunciation through a supported speech path when it becomes available; configuration alone cannot confirm the sound.
  </Step>
</Steps>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can I use phoneme tags with every voice?" id="faq-pronunciation-phonemes">
    No. Check the selected TTS model's capabilities. A compatible saved voice is also required; a tag in text does not add model support.
  </Accordion>

  <Accordion title="Does a dictionary locator upload a dictionary?" id="faq-pronunciation-locator">
    No. A locator references a resource. This guide does not claim an available dictionary-upload or creation workflow.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.