Why does Vapi mess up saying numbers
I'm using the Elliot voice model, and it can't say things like 1 0 0 1 or soething, it'll say oui or something. is there a way to fix this?
KHi there,
Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST).
We’ll get back to you as soon as possible during our normal business hours.
If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly.
Warm regards,
Vapi
Customer Support Team
Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST).
We’ll get back to you as soon as possible during our normal business hours.
If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly.
Warm regards,
Vapi
Customer Support Team
Uit is 10:51am PT...
KDisable formatPlan in your assistant config by setting "voice.chunkPlan.formatPlan.enabled": false..
Uok
Ujust for context, it is saying phone numbers
Uits just like 302 493 1001 but the last 4 characters are often pronounced wrong. like it could say one oui oiu one
Uso is that still the proper thing?
U@Kings_big
in fact, i can privately send you the recording for the call so you can hear what is happening. the callId is here: 4e71aa95-1136-46eb-84ec-f85449e35778
in fact, i can privately send you the recording for the call so you can hear what is happening. the callId is here: 4e71aa95-1136-46eb-84ec-f85449e35778Ubut i upload it privately so you may be unable to hear the recording
ELooking into it
Uthanks @Kings_big , any updates?
, any updates?KHey can you send a call_id that I can take a look at?
UI already sent it: 4e71aa95-1136-46eb-84ec-f85449e35778
KCan you try 11labs or different voice provider?
EYou'll need to work on your prompting to ensure that the LLM outputs the digits as you are expecting, and then the TTS models pronounce the same. I will suggest you try few calls with below prompting instructions which instructs the LLM to transform or generate numbers output as English letter words so they get pronounced correctly.
Concise Instructions (for Digit-by-Digit Pronunciation)
Concise Instructions (for Digit-by-Digit Pronunciation)
- To force digit-by-digit pronunciation, always write numbers as space-separated digits:
e.g., 1 0 0 1 instead of 1001 - Avoid using dashes or periods unless needed for style (test output first).
- Check output for edge cases; for codes or IDs longer than 4 digits, test for chunking or truncation.
- Examples:
Input: 1 0 0 1 → Output: "one zero zero one"
Input: 2 5 7 9 → Output: "two five seven nine"
Input: 2025 → Output: "two zero two five" (if input as 2 0 2 5)
Input: 1 2 3-4 → Output: "one two three dash four"
Input: 0 0 7 → Output: "zero zero seven"
