Skip to main content
When an outbound call goes unanswered by a person, Compensable’s agent detects that it’s reached an answering machine and leaves a message, rather than treating the call as connected or hanging up silently. The message it leaves is one you’ve written and approved ahead of time. The agent doesn’t improvise what to say into a voicemail box. Voicemail is managed from the Voicemails page in the Command Center, across three tabs: your message library, delivery sequences, and delivery history.

​
Authoring a voicemail message

1

Open the message library

On the Voicemails page, go to the message library tab and choose New, or select an existing message to edit.
2

Write the script

Give it a name and a script. Use the variable chips (lead name, firm name, callback number) to personalize it per lead. Choose a mode: a scripted template that’s synthesized as written, a library audio URL that plays a pre-recorded file, or a dynamic prompt where the AI personalizes the script per lead, falling back to this script if it can’t.
3

Set the voice and delivery

Pick a voice from your organization’s cloned voices, and set pacing, urgency, and warmth to control how the message sounds.
4

Clear the compliance check

Every script is checked against a compliance lint before you can save it. It confirms, for example, that the script identifies who’s calling and includes a callback number. Blocking failures have to be resolved before the message can be saved.
5

Preview and save

Synthesize a preview to hear the message with your chosen voice, then save it. Saving creates a new version of the message.
Editing the message library requires admin access. Other roles can view scripts, sequences, and delivery history but can’t change them.

​
Pinning a message

A voicemail message is pinned, not referenced live. When you build a delivery sequence or a cadence step that drops voicemail, you choose a specific message from the library at that point, and that’s the version that plays until you deliberately change it. This keeps a compliance-reviewed script from changing out from under a running campaign or cadence.
  • In a delivery sequence (the Sequences tab), a voicemail step pins a message alongside other channels, such as SMS, WhatsApp, email, or a second voicemail attempt, each with its own delay after the previous step, then applies to an outbound campaign as a set.
  • In a cadence, if enabled for your workspace, a voicemail step in the ladder editor pins a message the same way. See Cadences.

​
Delivery history

The Delivery history tab shows every voicemail drop your campaigns have attempted, with its outcome: deposited (the message was left), human answered (a person picked up instead), no answer, blocked, or failed. You can filter by campaign, lead, status, and date range, and export the current filtered view as CSV for your own records. A drop that’s blocked is blocked for the same reasons any other outbound touch is blocked: consent, opt-out, DNC, or quiet hours. The block reason is recorded alongside the attempt.
Voicemail drops go through the same consent and suppression checks as a live call, re-checked immediately before the message is left. See Compliance overview.