Hey! I'm trying to use the new way of detecting voicemail but it's not working for me when using a transcient assistant: This is part of my setting. "voicemailMessage": "Hello! this is many please call me back", "startSpeakingPlan": { "waitSeconds": 0.5, "smartEndpointingEnabled": "livekit", "transcriptionEndpointingPlan": { "onPunctuationSeconds": 0.5 } }, "maxDurationSeconds": 900, "voicemailDetection": { "provider": "google", "voicemailExpectedDurationSeconds": 20 }, Does this applies to transcient assistants? Could this be happening because I'm using my own twilio account and importing the nbrs to you? Here's some callIDs: 9d1d2f86-ff74-440e-81b1-2e9b63bbc47c f1080cbb-80c8-49f6-83bd-44b5eb24c0ab 4d278af9-42a7-4140-8aa7-6c7780344e9f

Hi there! I've looked into your voicemail detection issue with transient assistants. Based on the documentation I found, while there's no explicit mention that voicemail detection settings don't apply to transient assistants, I notice you're using "google" as the provider in your configuration. Most of the documentation refers to using "twilio" as the provider for voicemail detection [settings](https://docs.vapi.ai/phone-calling/voice-mail-detection). Regarding your second question, yes, using your own Twilio account could potentially be causing issues. There are several known problems when integrating custom Twilio accounts: 1. **Error Responses**: Users have reported receiving HTTP 404 responses when sending AMD (Answering Machine Detection) requests to Twilio [in some cases](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334077307966590986). 2. **Detection Issues**: Calls routed to voicemail sometimes lead to the AI interacting with the voicemail system rather than detecting it correctly. 3. **Configuration Challenges**: The timeout settings are critical - you might want to adjust your configuration to include these parameters:

json
"voicemailDetection": {
  "provider": "twilio",
  "voicemailDetectionTypes": [
    "machine_start", 
    "machine_end_beep", 
    "machine_end_silence", 
    "unknown", 
    "machine_end_other"
  ],
  "enabled": true,
  "machineDetectionTimeout": 30,
  "machineDetectionSpeechThreshold": 2400,
  "machineDetectionSpeechEndThreshold": 1200,
  "machineDetectionSilenceTimeout": 5000
}

You might also want to try using both Twilio's voicemail detection and Vapi's built-in voicemail tool together for improved reliability: ```json { "voicemailDetection": { "provider": "twilio", "enabled": true, "voicemailDetectionTypes": [ "machine_start", "machine_end_beep", "unknown" ], "machineDetectionTimeout": 15 }, "model": { "tools": [{ "type": "voicemail" }]

I tried exactly that setting as well and I got a twilio-failed-to-connect error instead of the voicemail. Here was most of the asssistant's config:

Hello Manu, Could you please switch to Gemini voicemail detection and give that a shot?

there's no Gemini option, it's either google or vapi or twilio.

Please try the Google option

That's what I had as shown on my first message: "voicemailDetection": { "provider": "google", "voicemailExpectedDurationSeconds": 20 },

Let me take a closer look at the logs