### Answer
A few community-sourced workarounds have come up around this exact issue:
One approach is adding a global node/prompt instructions that check for common voicemail-indicating phrases so the agent can trigger end call when it detects them. One user's list of trigger keywords included: "please press 1", "after the tone", "please enter verification code", "Google Virtual Calling Assistant", "Is Not Available", "Google Voice", "leave a msg after the tone" [(1) ](
) .
Another suggestion was reducing interruption sensitivity so the agent can cut off and correctly identify voicemail greetings before continuing its script, though this comes with the tradeoff of potentially talking over real users .
For a similar case where an agent wasn't reliably detecting voicemail during a warm transfer, the recommendation was to train silence/beep detection and add a voicemail-specific prompt, and if detection still fails, to contact support@retellai.com directly with specific call examples for investigation — since voicemail greetings can sound conversational enough to confuse detection logic [(2) ](
) .
On the official side, Retell AI's dashboard lets you enable voicemail detection on your agent's settings, choose the behavior (hang up or leave a message) , and configure a detection duration timeout — starting around 30 seconds is recommended, adjusted based on when voicemail typically triggers in your calls [(3) ](
) .
If you want, I can point you toward the feature-requests channel process one user followed when raising this same concern, or you can reach out to support@retellai.com with specific failed call IDs (as suggested in the community threads) for