I am making an ai receptionist that can speak 4 languages that is Ukrainian, Russian, english and spanish. It is gettibg spanish and English alright. But having hard time in detecting the Ukrainian and russian. When spoken to in either she repeats " i can help you in russian, Ukrainian English spanish" and then just stops. Sometiems she detects sometimes dont. Also the agent is sounding very robotic even though I am using 11labs voice and multilingual models for STT.

Hi 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

Urgent

Thank you for sharing the details. To help diagnose the Ukrainian and Russian detection issue, could you specify which speech-to-text (STT) provider and model you are currently using for language detection (e.g., Deepgram Nova 2/3, Google Multilingual, Gladia, etc.)? This will help determine if your configuration supports reliable auto-detection for those languages and suggest the best next steps. Sources: - [Multilingual Configuration Guide](https://docs.vapi.ai/customization/multilingual) - [Debugging Voice Agents](https://docs.vapi.ai/debugging) - [Multilingual Support Agent Example](https://docs.vapi.ai/assistants/examples/multilingual-agent)

I can help you providing solutions to solving this..

Stt elevenlabs claire model. For language Detection google multilingual

I have worked on multilingual not once how urgent do you need the problem solved

Message marked as helpful by @GIDEON! 🎉

With 4 languages, it will be more effective to set up a squad with 4 separate assistants. You can configure all 4 assistants to have the same system prompt but with one language different, then at the top level have a routing assistant with keypad entry enabled to appropriately route to the assistant per language (press 1 for English, 2 for Spanish, etc...)

Use Azure Voice instead and initiate the instructions right into your prompt. If perhaps you are still finding it a problem.. Send me a direct message, I would be able to assist you on that..

We apologize for the delay in responses lately. We are in process of making some changes to our workflow in how we handle support requests. The good news is that we are starting to get back on track of having a 48 hour response time and we would like to start cleaning up anything old. With that being said, just wanted to check in with you to see if you have made any progress or changes to your project since support has last reached out.