voicemail detection issues
its not detecting voicemails instead it shows the log as customer did not answer, my voicemail detection is sat to vapi and default settings. is there anything I can do to make it show voicemail instead?
KHi there,
Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST).
We’ll get back to you as soon as possible during our normal business hours.
If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly.
Warm regards,
Vapi
Customer Support Team
Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST).
We’ll get back to you as soon as possible during our normal business hours.
If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly.
Warm regards,
Vapi
Customer Support Team
VTo improve voicemail detection with the Vapi provider, try making detection more aggressive by lowering the
Test this change to see if voicemails are detected more reliably in your logs.
Source: Vapi documentation on missed voicemail troubleshooting.
startAtSeconds and increasing maxRetries. Update your assistant configuration as follows:Test this change to see if voicemails are detected more reliably in your logs.
Source: Vapi documentation on missed voicemail troubleshooting.
⤵️ Mention @Vapi Support Bot for follow-ups 🐥
Eit still shows customer-did-not-answer rather than "voicemail"...
E@Vapi Support Bot it still shows customer-did-not-answer rather than "voicemail"...
EUrgent
VTo improve voicemail detection and help ensure calls are logged as "voicemail" instead of "customer-did-not-answer," try increasing the
Test this setting—most voicemail systems need 20-30 seconds before the beep. If the issue persists, further troubleshooting may be required.
(Source: Vapi documentation on voicemail detection best practices)
beepMaxAwaitSeconds parameter to allow more time for the voicemail beep. Update your configuration as follows:Test this setting—most voicemail systems need 20-30 seconds before the beep. If the issue persists, further troubleshooting may be required.
(Source: Vapi documentation on voicemail detection best practices)
Ewhere can i find the "beepMaxAwaitSeconds": 25 on Vapi?
EUrgent
E@Vapi Support Bot
VTo set
You can update this setting via the API or in your assistant's configuration file. There is no mention in the documentation of a specific UI toggle for this parameter—it's set in the config JSON.
(Source: Vapi documentation on voicemail detection configuration)
"beepMaxAwaitSeconds" in Vapi, add or update it in your assistant's configuration JSON under the voicemailDetection section. For example:You can update this setting via the API or in your assistant's configuration file. There is no mention in the documentation of a specific UI toggle for this parameter—it's set in the config JSON.
(Source: Vapi documentation on voicemail detection configuration)
Ei tried those updated values it still shows Customer Did Not Answer rather than voicemail
E@Vapi Support Bot
EUrgent
VThank you for confirming you've updated the
This info will help determine if a provider switch (e.g., to Google or OpenAI) or further configuration is needed.
Source:
voicemailDetection settings as recommended. To help diagnose further, could you let me know which telephony provider or carrier's voicemail system you are calling (e.g., mobile carrier, VoIP, etc.)? Some systems may require different detection strategies.This info will help determine if a provider switch (e.g., to Google or OpenAI) or further configuration is needed.
Source:
EI am using twilio
E@Vapi Support Bot
VSince the Vapi provider settings did not resolve voicemail detection with Twilio, try switching to the Google provider for improved accuracy. Update your assistant configuration as follows:
Apply this change and test again—Google's provider is recommended for maximum accuracy with some voicemail systems.
(Source: Vapi documentation on provider-specific voicemail detection)
Apply this change and test again—Google's provider is recommended for maximum accuracy with some voicemail systems.
(Source: Vapi documentation on provider-specific voicemail detection)
EI tried those updated values and it still shows "Customer did not answer"
E@Vapi Support Bot
VThank you for your patience. Since updating both the provider and configuration hasn't resolved the issue, could you please confirm which detection type you are currently using in your
If possible, please share a snippet of your current
Source:
voicemailDetection settings (e.g., "type": "audio" or "type": "transcript")? This detail will help determine the next best troubleshooting step.If possible, please share a snippet of your current
voicemailDetection configuration (with sensitive info removed).Source:
Eok i just tested it on a different vapi account with this configuration
could it be the open ai model thats being used?
could it be the open ai model thats being used?
E@Vapi Support Bot
Eon the configuraiton above it did detect its a voicemail and worked fine, but on the other account it still shows customer did not answer
VThank you for sharing your configuration. To help pinpoint the issue, could you please confirm what value you are using for the
Tip: For best results with the OpenAI provider,
(Reference: Vapi Voicemail Detection Documentation)
Source:
"type" field in your voicemailDetection settings (e.g., "audio" or "transcript")? Tip: For best results with the OpenAI provider,
"type": "transcript" is recommended. For Vapi or Google, "type": "audio" is usually optimal. (Reference: Vapi Voicemail Detection Documentation)
Source:
U@Mike Mitchell I thought I was going crazy myself too. Friday shortly after starting the outbound calls, 100% of my calls were 0 seconds customer did not answer only. I also use Twilio.
EI fixed it
EIt was an easy fix
EBut it took so much time for me to figure it out
U@Mike Mitchell what ended up being the fix for you?
DMessage marked as helpful by @GIDEON! 
A@Mike Mitchell Same, can you share how you solved?
Eset a voice mail message 
that's been the fix
@julian @Dr House
that's been the fix
@julian @Dr House
Eyou have to actually write down a voice mail message
