> For the complete documentation index, see [llms.txt](https://docs.guideflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guideflow.com/help/ai/ai-voiceover/voiceover-pronunciation.md).

# Voiceover pronunciation

Guide the AI to pronounce specific words correctly—especially useful for technical terms, brand names, or unique pronunciations. This feature currently supports English only.

**How to specify pronunciation:**

Wrap any word in a phoneme tag using either IPA or CMU Arpabet notation:

```
Welcome to <phoneme alphabet="ipa" ph="ɡaɪdˈfloʊ">Guideflow</phoneme>
```

or

```
Welcome to <phoneme alphabet="cmu-arpabet" ph="G AY1 D F L OW2">Guideflow</phoneme>
```

**Quick tips:**

* Apply pronunciation to individual words only (for full names, tag each word separately).
* Include stress markers (1 for primary, 2 for secondary, 0 for unstressed) in CMU Arpabet.
* Most common use cases: product names, technical acronyms, or industry-specific terms.

**Finding pronunciations:**

* IPA: Use online IPA dictionaries or converters.
* CMU Arpabet: Reference the CMU Pronouncing Dictionary.

This ensures your AI narrator pronounces critical terms exactly as your users expect to hear them.


---

# 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.guideflow.com/help/ai/ai-voiceover/voiceover-pronunciation.md?ask=<question>&goal=<user_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.
