Skip to main content
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.
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.

Review the supported fields

The following fields belong to conversation_config.tts. Check the selected model’s supports_pronunciation_dictionaries and supports_phoneme_tags capabilities in Get available AI model. Support for one does not imply support for the other.

Prepare a pronunciation review

1

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.
2

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.
3

Reference only known resources

If you have an accessible dictionary identifier, review its intended version before adding a locator to a server draft. Do not invent dictionary IDs or assume a public creation endpoint exists.
4

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.

Frequently asked questions

No. Check the selected TTS model’s capabilities. A compatible saved voice is also required; a tag in text does not add model support.
No. A locator references a resource. This guide does not claim an available dictionary-upload or creation workflow.