This page covers voice-specific TTS tuning. If you are only working with webchat, you can skip this page.
Key points
- Enhanced pronunciation accuracy: Correctly pronounce domain-specific terms and unique phrases using IPA.
- Streamlined workflow: Manage rules directly in Agent Studio.
- Flexibility: Adjust pauses and pronunciation for various needs.
How it works
Pronunciations use the International Phonetic Alphabet (IPA) to define pronunciation rules. You can also use SSML (Speech Synthesis Markup Language) such as<break>, <prosody>, and <emphasis> in the replacement string.
You may define pronunciation rules using regular expressions and replacements, including support for regex capture groups.
Multilingual pronunciation rules
For multilingual agents, pronunciation rules are organized by language. Each language has its own set of rules, displayed as separate collapsible cards. Rules within a language card only apply to responses in that language. To add a rule for a specific language:- Expand the language card.
- Add the regex pattern and replacement.
- The rule automatically scopes to that language.
Rule evaluation order
- A rule that formats a phone number with pauses or separators
- A rule that converts digits into words
Using capture groups in replacements
If your regular expression uses capture groups (for example,(\d{3})), you can refer to these in the replacement string using \1, \2, etc. This allows you to reformat matched text dynamically.
Example: Formatting a phone number with pauses
To transform a number like(651) 359-2923 into:
“six five one [pause] three five nine [pause] two nine two three”Use the following pronunciation rule:
- Regex:
$begin:math:text$?(\\d{3})$end:math:text$?[ -]?(\d{3})[ -]?(\d{4}) - Replacement:
\1 <break time="0.5s" /> \2 <break time="0.5s" /> \3 - Case sensitive:
FALSE
Example: IPA correction
- Regex:
/\bLouvre\b/ - Replacement:
/ˈluːvrə/ - Case sensitive:
FALSE
