Skip to content
Operations

Voicemail drops

Reusable voicemail recordings, scoped to a workspace, an agent or a campaign.

A voicemail drop in Autocloz is a named recording tied to one of three scopes: the whole workspace, one agent, or one campaign. When more than one drop could apply, the campaign's drop wins, then the agent's, then the workspace default. Drops, scopes and that precedence rule are live today; automatic playback into a call is not built yet.

What you get
  • ·Named drops that point at a clip in your audio library
  • ·Three scopes: workspace default, one agent, one campaign
  • ·Fixed precedence: campaign, then agent, then workspace
  • ·Creating a drop is limited to owners and admins
  • ·Every create, edit and delete lands in the audit log
  • ·Not built yet: automatic playback into a live call
Voicemail drops · 3 saved
Generic intro · v3
Workspace default
0:18vm_intro_v3.mp3
Jamie · personal
Agent-attached
0:24vm_jamie.mp3
Q3 promo voice
Campaign-attached
0:32vm_q3_promo.mp3
The problem

The same voicemail, recorded by hand, call after call

A rep who reaches an answering machine either hangs up or leaves the message again from memory. Each rep's version drifts, nobody can say which wording a campaign was meant to use, and changing the script means asking the whole team to change a habit. A voicemail drop moves that message into one managed record, with a fixed rule for which version belongs to which rep and campaign.

  • Every rep leaves a slightly different message
  • No record of which wording a campaign should use
  • A script change depends on every rep remembering it
  • No control over which recording prospects hear
3
scope levels
workspace · agent · campaign
1
precedence rule
campaign, then agent, then workspace
Audited
every create, edit and delete
with the person who made it
How it works

The detail.

Most-specific scope wins

The resolution rule is fixed: a drop attached to the campaign comes first, then a drop attached to the agent, then the workspace default. The agent-level match only counts drops that are not also tied to a campaign, and every lookup is limited to your own workspace, so another workspace's recording can never be picked. That lets ops keep one general message while a single rep or a single campaign carries its own.

Guard rails on who can create a drop

Only workspace owners and admins can create a voicemail drop or register a clip by web address, because both are treated as telephony spend. The API also refuses a drop whose audio file, agent or campaign belongs to a different workspace, and the refusal says which of the three was wrong. Viewing the list of drops does not need admin rights.

What is live today, and what is not

The management side is live: named drops, the three scopes, the precedence rule and the audit trail. Playback is not. No dial path in Autocloz currently plays a drop's recording into a call, so an answering machine that picks up does not yet hear your message. Power and Parallel dialer campaigns do offer a Drop voicemail choice for an answering machine, but today that choice only files the call as a voicemail outcome.

The recording lives in the library, not in the drop

A drop stores a reference to an audio file rather than a copy of the recording. Deleting that file from the audio library deletes every drop built on it, so check the Voicemail tab before removing a clip. A drop's name, agent and campaign can be changed later through the API, but its audio cannot, so a new recording means a new drop.

FAQ

Specific to this feature.

Does a drop play automatically when a call reaches voicemail?

+

Not yet. Drops, scopes and the precedence rule are live, but no dial path currently plays the recording into a call. The Drop voicemail choice on Power and Parallel dialer campaigns only records a voicemail outcome; it does not leave a message.

Which drop applies if a campaign, an agent and the workspace all have one?

+

The most specific one: the campaign's drop first, then the agent's, then the workspace default. A general drop can therefore cover the whole team while one rep or one campaign keeps a version of its own.

Are do-not-call numbers still protected?

+

Yes, at the point of dialling. The Power and Parallel dialer skips any queued number on the do-not-call list before placing the call, and sequence call steps check the list before they dial.

Where does the recording come from?

+

From the audio library. In the app you register a clip by pasting the web address where it is hosted, and the drop form lists those clips with their length. There is no in-browser recorder, so record and export the file elsewhere first.

In depth

The full story.

Setting up a drop in Autocloz uses two tabs of the Call console. On the Audio tab, an owner or admin registers the recording with a display name and the web address where the file is hosted. On the Voicemail tab, they give the drop a name of up to 120 characters and choose that clip from a list that shows each recording's length where one was entered. The in-app form saves the drop as the workspace default; attaching it to one agent or one campaign is currently done through the API.

Scope matters once a team has more than one message in play. A workspace default applies whenever no agent or campaign drop matches. An agent-level drop suits a rep whose own voice is part of the pitch. A campaign-level drop suits an offer with its own wording, such as an event invitation, and it outranks both of the others for that campaign. Each change to a drop is written to the audit log as a created, updated or deleted event, with the person who made it.

Autocloz does not send ringless voicemail, which places a message in a mailbox without the phone ringing, and it has no in-browser recorder. It also does not yet play a drop into a call automatically. What it does provide is one managed, audited list of the messages your team would otherwise leave by hand, and a tested rule for which message belongs to which rep and campaign.

Pairs well with