Voice AI not following the prompt
# support
s
I am setting up a new voice ai the problem that I am facing is it cannot read system prompt calling is going Balck after the introduction
v
Hi there! 👋 I understand you're having trouble with your voice AI not reading the system prompt and calls going black after the introduction. I don't have specific details about your particular setup, but I can definitely help troubleshoot this common issue based on information I've found. Here are several potential causes and solutions for your issue: ## System Prompt Configuration Issues 1. **Check Your System Prompt Format**: Make sure you're using the correct format. The
systemPrompt
property might be deprecated - instead, use the
messages
array with a
role
of
system
[according to Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1337126843790397591). Example of the correct format:
Copy code
json
   "model": {
     "provider": "openai",
     "model": "gpt-4o-mini",
     "messages": [
       {
         "role": "system",
         "content": "your prompt here"
       }
     ]
   }
2. **Empty First Message**: Ensure your first message for the AI Assistant isn't empty, as this could prevent the AI from speaking initially [based on user reports](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1339467226381684789). ## Call Going Black Issues 1. **Service Degradation**: There might be service issues with Deepgram or other services affecting your voicebot's functionality [according to support discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1296852804631265392). 2. **Silence Timeout**: Calls may be ending due to silence timeout settings [as reported by users](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1296852804631265392). 3. **Voice AI "Deafness"**: The AI might not be hearing user input, causing the call to end [based on reported bugs](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1340235729204285510). ## Troubleshooting Steps
1. **Check API Keys**: Double-check your API keys and access permissions to ensure they're correct and haven't expired [according to troubleshooting guides](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334024569861963788). 2. **Adjust Configuration Settings**: - Set
waitSeconds
to 0.8 in your
startSpeakingPlan
- Set
transcriber.endpointing
to 300 - Try enabling
smartEndpointingEnabled
[based on user solutions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1338497725917827196) 3. **Try Different Models**: If you're using Groq, try switching to OpenAI models [as suggested in support threads](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1303981615344779325). Some users reported better results with GPT-4o instead of GPT-4o mini [according to discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1340523490662416494). 4. **Adjust Temperature**: Set the model temperature to 0-0.3 to resolve issues with the AI behaving oddly [as recommended by users](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341892594044633099). 5. **Request Call ID**: If the issue persists, getting the call ID can help in tracking down the specific problem [according to support recommendations](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341487523897147422). Would you be able to share which of these troubleshooting steps you've already tried, or if you need more specific guidance on any particular solution? Sources: - [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1337126843790397591) - [User reports](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1339467226381684789) - [Support discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1296852804631265392)
k
Hey! To help track down this issue, could you share: - The call ID - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!