Hi, anyone else had this issue where they can't press test call? It just says "Assistant ID not allowed" or "Assistant Key ID not allowed" with a red error message in the bottom right. Whenever I press test call, we're using the voice agent successfully inside a wrap by the VAPI SDK, and we've got a variety of tools. But I don't know why what's going wrong or how to fix it. The VAPI chatbot is awful; it lacks so much knowledge, and chats disappear if you close it by accident. It's really hard to get any support from VAPI, and I have no idea why they make the chats disappear, especially if they're putting their custom support on autopilot.

This error usually means your assistant ID is missing or not set up correctly. To fix it, make sure you assign a valid assistant to your phone number in the Vapi Dashboard, or include the

assistantId

in your API call. For example:

javascript
const response = await vapi.calls.create({
  workflow: { id: "your-workflow-id" },
  assistantId: "your-assistant-id", // Make sure this is set
  to: "+1234567890"
});

Double-check your assistant ID and try again—this should resolve the "Assistant ID not allowed" error. (See the [Discord discussion for more details](https://discord.com/channels/1211482211119796234/1336652401733668864)) Source: - [Discord discussion about Assistant not valid error](https://discord.com/channels/1211482211119796234/1336652401733668864)

its vapi sdk rather than a phone number though?

Hi JP | Exited Founder, If you're encountering issues with the "Talk to Assistant" feature in the Vapi dashboard, you can start by checking the following areas: 1. **Dashboard Testing**: Use the "Talk to Assistant" or "Call" buttons directly in the [Vapi Dashboard](https://dashboard.vapi.ai/) to eliminate phone network variables and provide a real-time transcript view with immediate results. 2. **Error Messages**: Navigate to

Observe > Call Logs

in your dashboard to review any error messages that might appear during the test. 3. **Call Status**: Check the

Ended Reason

under the call logs for any specific issues. Possible reasons can range from misconfigurations to external service errors. More details can be found in this [guide on call ended reasons](https://docs.vapi.ai/calls/call-ended-reason). 4. **Service Status**: Ensure that Vapi and related AI service providers are operational by visiting their respective status pages: - [Vapi Status Page](https://status.vapi.ai/) - [OpenAI Status](https://status.openai.com/) - [Anthropic Status](https://status.anthropic.com/) - [ElevenLabs Status](https://status.elevenlabs.io/) - [Deepgram Status](https://status.deepgram.com/) If you continue to experience issues or need further assistance, reviewing your call logs for specific error patterns or steps might help identify the root cause. You can find more detailed steps on debugging in the [debugging voice agents guide](https://docs.vapi.ai/debugging).