Voicemail Tool
Learn how to use the assistant-controlled voicemail tool for flexible voicemail handling
Overview
The voicemail tool gives your assistant direct control over what happens when it reaches a voicemail system. Unlike automatic voicemail detection, which operates independently of your assistant, this tool lets your assistant decide when it’s hit voicemail and then either leave a configured message or silently end the call — depending on how you’ve set it up.
Key benefits:
- Maximum flexibility — assistant decides when to invoke the tool, and you decide what happens when it does
- Customizable — use template variables to personalize voicemails per call
- Cost-effective — only triggers when needed
- Simple integration — works like other built-in tools
How it works
When you add the voicemail tool to your assistant:
- Your assistant listens for voicemail indicators (greetings mentioning “unavailable”, “leave a message”, etc.)
- Upon detecting voicemail, the assistant calls the tool
- Depending on how you’ve configured the tool, it either delivers your configured message or skips speaking entirely
- The call ends automatically
This approach differs from automatic voicemail detection, which detects voicemail at the system level. The voicemail tool puts detection and response entirely in the assistant’s hands, so reliability depends heavily on your system prompt — see Detection prompting below for the indicators your prompt should explicitly call out.
Voicemail behavior modes
When you configure the voicemail tool, you choose what the caller hears once voicemail is detected:
How the modes map to the underlying fields
Two fields work together to drive these modes: the tool’s messages array (which can hold a request-start message with optional template variables) and the assistant-level voicemailMessage property. The dashboard radio buttons orchestrate these for you, but if you’re configuring via the API, set the fields directly:
Configuration
Add the voicemail tool to your assistant and configure your system prompt to invoke it when voicemail is detected.
Dashboard
API
- Go to Tools in the left nav and click Create Tool.
- Select Voicemail as the tool type.
- Give the tool a name and description. The description tells the LLM when to invoke the tool — keep it consistent with the voicemail-detection instruction you’ll add to your system prompt in step 7. Example: “Leave a voicemail message when you detect you’ve reached a voicemail system or auto-attendant.”
- Under Voicemail Script, choose a behavior mode: Use assistant voicemail message, Use custom script, or Skip speaking a voicemail. See Voicemail behavior modes for details.
- Save the tool.
- Attach the tool to your assistant: open the assistant, go to Tools, and add the voicemail tool you just created.
- Add a voicemail-detection instruction to your assistant’s system prompt. Without this, the LLM won’t know when to call the tool. See Detection prompting for indicators to include.

Message configuration
Assistant voicemail message
To reuse the same voicemail across an assistant without configuring the tool separately, leave the tool’s messages empty and set voicemailMessage on the assistant:
Custom script mode
For custom-script mode, define the voicemail message inline:
You can set a hardcoded message, or use template variables like {{company}}, {{message}}, and {{phone}} that are substituted at call time. See Variables for how to pass values.
Skip mode (silent end-call)
To silently terminate the call on voicemail, leave the tool’s messages array empty and clear voicemailMessage on the assistant:
Use this mode for outbound outreach where the value is a live conversation and a missed voicemail is fine — silent termination keeps the call short and avoids the cost of running it to the max-duration cap.
Pre-recorded audio messages
For consistent quality and pronunciation, use pre-recorded audio files by providing the URL in the content field:
Pre-recorded audio messages are ideal for brand-specific messaging or when you
need precise pronunciation of phone numbers, website URLs, or company names.
Supported formats: .wav and .mp3 files.
Best practices
Detection prompting
Be specific about voicemail indicators in your system prompt:
- “unavailable”
- “leave a message”
- “voicemail”
- “at the tone”
- “beep”
For auto-attendants and IVR menus, add cues like:
- “press 1 for…”
- “for a list of departments”
- “if you know your party’s extension”
Message structure
Keep voicemail messages:
- Brief — under 30 seconds
- Clear — state name, company, and purpose
- Actionable — include callback number or next steps
- Professional — match your brand voice
Error handling
Consider edge cases:
- Long voicemail greetings
- Voicemail box full scenarios
- Systems requiring keypad input
- Auto-attendants that loop their menu
Voicemail tool vs. automatic detection
Avoid combining the voicemail tool with automatic detection, as this could result in false positives and other complications.
Choose the voicemail tool when you need maximum flexibility and cost efficiency. Choose automatic detection when you need guaranteed system-level detection without relying on assistant prompting.
Common use cases
- Sales outreach — personalized follow-up messages
- Appointment reminders — leave detailed appointment information
- Customer service — callback scheduling with ticket numbers
- Lead qualification — leave targeted messages based on lead data
- Outbound prospecting (no message) — cleanly terminate calls that hit voicemail when your strategy depends on live conversation
Next steps
- Learn about other default tools
- See how to create custom tools for your specific needs