repeating numbers
# support
u
I can't get vapi to say numbers back to the customer in a repeatable sensible way. In the prompt I am using this :- "Say 'I have your number as ' and say the number contained in {{callerNumber}} replacing '+44' with '0' and it is important that you say the digits SLOWLY and ONE AT A TIME and pronouncing the number 0 as zeeroe so the caller can individually identify them properly - NEVER RUSH SAYING THE NUMBERS. ", sometimes it's great but more often is saya it so fast it in a blur or the number six is just a grunt. any help appreciated - thx
v
Hi Christine! πŸ‘‹ I understand you're having trouble with Vapi's pronunciation of numbers - sometimes it works well but often speaks too quickly or doesn't pronounce digits clearly. While I can't explain why the number six specifically comes out as a grunt, I can definitely help with configuring Vapi to pronounce numbers more consistently and clearly. Here are several approaches you can try to improve number pronunciation: ### 1. Adjust the Voice Formatting Plan You can modify the
numberToDigitsCutoff
setting in your assistant's voice configuration:
Copy code
json
{
    voice: {
        chunkPlan: {
            formatPlan: {
                numberToDigitsCutoff: 100000 // Set this higher than your largest expected number
            }
        }
    }
}
This setting determines when numbers should be spoken as individual digits versus words [according to Vapi documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342349738032500736). ### 2. Enable SSML Parsing SSML (Speech Synthesis Markup Language) gives you more control over pronunciation: 1. Visit the [Update Assistant API](https://docs.vapi.ai/api-reference/assistants/update-assistant) 2. Select your current voice provider (e.g., 11labs) 3. Enable the SSML parsing option (
enableSsmlParsing: true
) 4. Save the changes With SSML enabled, you can use tags to control speech rate and pronunciation [as mentioned in Vapi's documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1338644573207007304). ### 3. Try Different Voice Providers Different TTS providers may handle number pronunciation differently. Vapi supports several providers including PlayHT, ElevenLabs, Azure, OpenAI, and others. You might want to experiment with different providers to find one that handles number pronunciation better [according to Vapi's multilingual documentation](https://docs.vapi.ai/customization/multilingual). ### 4. Use Phonetic Spelling
For consistently mispronounced words or numbers, try using phonetic spelling. For example, instead of "0", you might try spelling it as "zeroe" directly in your prompt [as suggested in Vapi's troubleshooting information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1332426179285880863). ### 5. Adjust Speech Rate Settings Look for parameters like
rate
,
speed
, or
tempo
in your voice synthesis settings and set them to a lower value to slow down speech [according to Vapi's support documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336023375721791549). Would you like me to provide more details on any of these approaches or help with implementing a specific solution? Sources: - [Vapi documentation on numberToDigitsCutoff](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342349738032500736) - [Vapi documentation on SSML parsing](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1338644573207007304) - [Vapi documentation on multilingual support](https://docs.vapi.ai/customization/multilingual) - [Vapi documentation on phonetic spelling](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1332426179285880863) - [Vapi documentation on speech rate settings](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336023375721791549)
r
Which model are you using for the assistant, transcriber, and voice?
k
Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!
2 Views