Hello my Voice bot always stops speaking and I get the Message Assistent Said end Call Phrase. I am trying now since days but the Problem keeps. https://cdn.discordapp.com/attachments/1353040706150731938/1353040706704248882/IMG_6876.jpg?ex=67e034da&is=67dee35a&hm=31c9194663d8dfbfc7dbb3c93d8f5c128882f0eefe666f546a4caa6bb94241f2&

Hi there! 👋 I understand how frustrating it can be when your voice bot keeps stopping unexpectedly. I don't have access to your specific bot configuration, but I can definitely help explain what that "Assistant said end Call Phrase" message means and provide troubleshooting steps to resolve this issue. ## What's happening? The message "Assistant said end Call Phrase" means that your assistant recognized a phrase or keyword that triggered call termination. According to [Vapi documentation](https://docs.vapi.ai/calls/call-ended-reason), this happens when the assistant detects certain phrases that are configured to end the call automatically. ## Why this happens This typically occurs when your voice bot has

endCallPhrases

configured in the

assistantOverrides

settings. When the assistant speaks one of these phrases, it triggers the call to end. This feature is designed to detect phrases typically used by auto attendants like "you've reached," "press 0 for," or "to speak to a representative." ## Troubleshooting steps: 1. **Check your endCallPhrases configuration**: Review your

assistantOverrides.endCallPhrases

settings to see what phrases are triggering call termination. You might have phrases configured that your assistant is saying during normal conversation. 2. **Adjust endpointing settings**: According to [community discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1331035264751112202), you can try this configuration:

json
   "start_speaking_plan": {
     "waitSeconds": 0.8,
     "smartEndpointingEnabled": true
   }

3. **Check Deepgram settings**: If you're using Deepgram, set its endpointing to 300ms to better capture all words, including single words. 4. **Review your assistant's prompts**: Make sure your assistant isn't programmed to say phrases that might match your end call phrases.

Here a few Call ids 8d9d311c-8e88-4fec-afc0-68549ef75be7 92646cc4-fbff-4628-bfd9-076a69b22d5e 90293729-dfb6-4459-9bb0-8dba533fe251 44b3c1da-5662-4593-861b-68fb65fd1dd7 65019075-c57b-4d40-9f01-05debcace160

did u solve it? my ai stops talking sometimes too

Hey Nikita, The ended reason means the call has been entered by the Assistant because the Assistant has end-call phrases assigned to it (assigned by default). Within the new templates, we are removing them so they won't be assigned by default. Below I am pasting an API curl request. Using this you can remove the end curl faces from your assistant.

```bash
curl -X PATCH "https://api.vapi.ai/assistant/{ASSISTANT_ID}" \
  -H "Authorization: Bearer {API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{
    "endCallPhrases": null
  }'

``` \### Values to Replace: 1\. {ASSISTANT_ID} - Replace with your specific assistant/resistance ID (e.g., "12345678-1234-1234-1234-123456789abc") - This is the unique identifier for your assistant/resistance - You can find this in your VAPI dashboard under the Assistants section 2\. {API_KEY} - Replace with your VAPI API key - This is the authentication token needed to access your VAPI account - You can find or generate this in your VAPI dashboard under Settings > API Keys