Urgent! Shared account behaves differently, voices...
# support
j
Hey Vapi team 👋 We're running into some serious issues with our shared Vapi account and could use your help. I use the account from Indonesia — everything works fine on my side. But my co-founder (NL-based) can’t test or publish any agents. He keeps getting errors like: "11Labs voice not found" "Room has been deleted" On top of that, some agent settings look different on his dashboard compared to mine — even though we’re using the same account. We tried: Removing & re-adding ElevenLabs credentials Refreshing the voice library Clearing cache and re-logging Duplicating the agent Still nothing. It’s really slowing us down — it has impact on clients too, so this doesn’t look good from his side. Any ideas what might be causing this? Really appreciate a fix or workaround 🙏 Thanks in advance!
v
Hey there! đź‘‹ Sorry to hear you're experiencing these issues with your shared Vapi account. I understand I can't provide a definitive solution without examining your account directly, but I can help with some troubleshooting steps based on similar issues others have faced. ## For the "11Labs voice not found" error: This could be related to several factors: 1. **API Key Configuration**: Verify that the 11Labs API key is correctly entered in your [VAPI Provider Key section](https://dashboard.vapi.ai/keys) and that the voice is properly added to the [VAPI dashboard](https://dashboard.vapi.ai/library/voice). 2. **Voice Synchronization**: Try selecting 11labs as your voice provider and clicking on "Sync with 11labs" from the [Voice Library](https://dashboard.vapi.ai/voice-library). 3. **Conflicting API Keys**: If you're using a voice managed by Vapi's account, using your own 11Labs key might cause issues. Conversely, if you're using a private voice owned by you, you'll need to use your own key and import the voice to Vapi. 4. **Model Compatibility**: The "11labs flash_model" might be causing the error. A potential solution is to change the model to "turbo". ## For the "Room has been deleted" error: This could be due to: 1. **Service Degradation**: According to support threads, Deepgram service degradation has been known to cause this error. 2. **End-Call Phrases**: The actual reason for call termination may be
assistant-said-end-call-phrase
. Removing those phrases from your assistant might resolve the issue. 3. **Configuration Issues**: Ensure that VAPI is correctly configured to send and receive the correct data. ## Regarding geographical differences: The discrepancies between Indonesia and Netherlands users might be related to: 1. **Server Location**: Vapi servers are hosted in the US regions by default for all users. This might affect how the service behaves in different locations.
2. **Network Optimization**: The network path between servers and clients might need optimization, especially when accessing from different global locations. 3. **Configuration Synchronization**: There might be configuration issues specific to your organization's VAPI setup that are causing different behaviors in different locations. If these steps don't resolve your issues, I'd recommend contacting Vapi support with your organization ID and detailed description of the problems. Would you like more specific information about any of these troubleshooting steps? Sources: - [Troubleshooting "11Labs voice not found" error in Vapi](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334024569861963788) - [Troubleshooting "Room has been deleted" error in Vapi](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1296852804631265392) - [Impact of geographic location on shared Vapi account functionality in Vapi](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1332423973715316868) - [Agent settings discrepancies in Vapi shared accounts](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334024569861963788)
k
This error occurs when the specified voice ID isn't recognized by ElevenLabs. This maybe the possible cause; Subscription level, voice availability and API key issues..
s
Hey! To help track down this issue, could you share: - The call ID This would really help us figure out what went wrong!
2 Views