romanian numbers
# support
g
When I ask the agent for a price inside attached knowledge share it does one of the following 1. It reads it in english instead of romanian; language is set to ro-RO as per print screen. Instruction is provided to only talk in romanian. the whole prompt is in romanian. 2. It reads it as 1 - 8 - 0 -0 - 0 -0 instead of one thousand eight hundred, although inside the knowledge base I wrote the price using letters 3. The value of the price is different than the one provided in knowledge base call id e70f6660-d3ac-45ce-aa96-5b3be37bcbbc starting at minute 01:46 @User https://cdn.discordapp.com/attachments/1329136078921138199/1329136079999336448/image.png?ex=67893def&is=6787ec6f&hm=eb263f90c0e57ac1b9de8a7887383181b4cf7137d3ac09401f1184ebb94512b7&
v
@Gabriela Macovei I'm sorry to hear about the issues you've encountered with the language and number formatting in the voice response. To address this, I would need to review the specific settings and data within the call ID you've provided. However, as a support bot, I don't have direct access to call logs or the ability to listen to calls. For the issues you've described, here are some general steps that can be taken to troubleshoot and resolve them: 1. **Language Issue**: Ensure that the language settings are correctly configured to Romanian (ro-RO) for both the text-to-speech and speech-to-text services. Double-check the configuration in the system to make sure that the language preference is being honored throughout the entire interaction. 2. **Number Formatting**: Verify that the text-to-speech engine is configured to interpret numbers as full digits rather than individual numbers. This might involve adjusting the settings or providing additional context in the knowledge base to guide the text-to-speech engine. 3. **Incorrect Price**: Make sure that the knowledge base is up-to-date and that the correct price is being referenced during the interaction. If the price is dynamically generated or retrieved from an external source, confirm that the correct value is being pulled. If these steps do not resolve the issues, or if you need further assistance with the specific call ID mentioned, please ask support for more info on this. They will have the necessary tools and access to investigate the matter in detail and provide a solution.
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
g
can you provide instructions to do these checks ? I don`t think they are available in VAPI UI for azure transcriber
another example here: 318e57fc-3329-444a-af0c-225bdc37599c @User
I asked same question 4 times, it gets different values. none of them are from the knowledge base 318e57fc-3329-444a-af0c-225bdc37599c
s
@Gabriela Macovei As discussed over the calls, did you try implementing the voice formatting plan and LLM instructions to generate numbers in Romanian language?
2 Views