> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Voicemail

> Prepare a voicemail-detection definition and optional message without assuming outbound calls, detection, or message delivery.

The voicemail definition describes what the agent should do if voicemail is detected. Prepare wording that remains appropriate when someone other than the intended recipient hears it.

<Note>
  This is configuration authoring. It does not establish working voicemail detection, outbound calling, or delivery of a recorded message. An optional message in the draft is not evidence that a call was placed.
</Note>

## Prepare the definition

<Steps>
  <Step title="Decide whether a message is appropriate">
    Keep any message brief and avoid private account details. Do not promise a callback, completed action, or follow-up that your process cannot provide.
  </Step>

  <Step title="Open Voicemail Detection">
    On the agent's **Tools > System tools** panel, enable **Voicemail Detection** and open its settings. Review the **Voicemail message (optional)** field.
  </Step>

  <Step title="Set the intended response">
    Leave the field blank to store `null`, expressing the intent to end without a message when voicemail is detected. Enter text to request a message before ending. These are intended behaviors, not verified live outcomes.
  </Step>

  <Step title="Save and inspect">
    **Save** updates the working copy. Preserve the definition at `conversation_config.agent.prompt.built_in_tools.voicemail_detection` in a complete [server draft](/agents-platform/deploy/versioning), then read it back.
  </Step>
</Steps>

## Parameters and message review

`params.system_tool_type` must be `voicemail_detection`. The only additional tool-specific field is `voicemail_message`, an optional string whose default is `null`.

A preparation example is: “This is the delivery support assistant. Please use the support contact listed in your order confirmation.” Adapt the wording to your actual organization and support process before use.

The editor accepts text containing [dynamic-variable references](/agents-platform/configure/personalization/dynamic-variables). Review them using fictitious placeholder values. A reference does not prove that the variable will be available or substituted during a call.

Prepare examples for a human greeting, a recorded greeting, silence, and an ambiguous automated message. The configuration does not include a verified detection-accuracy guarantee or a threshold you can tune here.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does saving the message schedule an outbound call?" id="faq-voicemail-outbound">
    No. It stores text in an agent configuration. Calling and scheduling are separate capabilities with their own availability limits.
  </Accordion>

  <Accordion title="Is an empty message a request to leave silence?" id="faq-voicemail-empty">
    The dashboard converts an empty field to null. The authored intent is to end without playing a message when voicemail is detected; runtime behavior still requires verification.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.