VoiceDrop Ringless Voicemails
Sequences · Early access

The drip campaign runs for weeks. It stops the second they answer.

Drop a voicemail. Wait a day. Text the ones who went quiet. Stop the moment someone calls you back. Build it once on a canvas and VoiceDrop walks every contact through it on their own.

The drip campaign runs for weeks.

Sequences is in early access

Drip campaigns are built in Sequences, which is rolling out to a limited group of VoiceDrop customers. You request access from your dashboard, and the builder carries an Early access marker while it is in your account.

How it works

How a drip campaign with voicemail works

Three things, then it runs on its own. None of it needs a developer.

  1. 1
    Step 1

    Drag the steps onto a canvas

    Pick from seven steps and join them together: a voicemail, a wait, a text, and a branch for whatever happens next.

  2. 2
    Step 2

    Launch it with a contact list

    People enter the flow when you launch it with a list. Everybody walks it on their own clock, from wherever they joined.

  3. 3
    Step 3

    It stops when they answer

    A Wait for event step holds each person until they reply, call you back, or ask to stop. Whoever stays quiet carries on down the other branch and gets the text.

Voicemail and text together

A text message drip campaign with your voice in front

Your voice lands first, the text only if it has to

Most drip campaigns open with a text or an email. This one opens with a recorded voicemail that drops straight into the voicemail box without the phone ringing, and texts only the people who did not respond to it.

  • Send Voicemail drops a recorded message without the phone ringing
  • Send SMS goes out from your texting number
  • Each of those branches on Delivered and Not delivered
  • Wait for event branches on It happened and Ran out of time
A VoiceDrop drip campaign on the canvas: a start step, an A/B split into two voicemail scripts, a wait for a callback, then a text message on the branch where nobody called.
The steps

Seven steps, in plain English

These are the product's own words for what each step does, not a marketing rewrite of them.

Send Voicemail

Drops a recorded voicemail straight into their voicemail box. Their phone does not ring. You pick the voice and write the script when you set the step up.

Send SMS

Sends a text message from your texting number. You write the message when you set the step up.

Wait

Holds the person here for as long as you choose, then moves them on to the next step. Nothing is sent while they wait.

Wait for event

Hold here until the person replies, calls you back, or asks to stop. If nothing happens in the time you set, they carry on down the other branch.

If / condition

Checks one thing about the person, for example whether your message was delivered or whether they called you back, then sends them down the Yes branch or the No branch.

A/B split

Split people at random between two or more versions, so you can see which one works better. You choose what share each version gets.

Never contact again

Add this person to your do-not-contact list. They stop getting voicemails and texts from this sequence.

In practice

Building a real estate drip campaign

One list, two scripts, and the callback decides

Upload the expired listings, split them in half, and record two versions of the same voicemail. Everybody who calls back leaves the flow. Everybody who does not gets a text a day later, and you can see which of the two scripts brought more people in.

  • Wrap any field name in double braces, for example {{First Name}} or {{City}}
  • The panel lists the fields used in each message, so a typo cannot go out unnoticed
  • An A/B split weights the branches, so the test runs on one list
The VoiceDrop step settings panel, showing a voicemail script with a First Name merge field and the list of fields used in that message.
What you get

An SMS drip campaign that opens with a voicemail

  • Seven steps: voicemail, text, wait, wait for a reply, condition, A/B split and never contact again
  • Branches for Delivered, Not delivered, It happened, Ran out of time, Yes and No
  • A/B two scripts against one list and compare the callbacks
  • Merge fields in both voicemail scripts and text messages
  • The chase stops the moment somebody calls you back
  • Voicemails and texts leave from the same local number

It will not call anyone at 3am

Sending hours run on each person's own local time, worked out from their phone number, so someone in California is contacted on California time and someone in Hawaii on Hawaii time. A 9am start means 9am wherever they are.

The sending rate has no off state. Every drip campaign is saved with a rate on it, capped by your account's limit, so a flow cannot be published that sends faster than your account allows.

FAQ

Drip campaign questions

A drip campaign is a series of messages that go out over days or weeks rather than all at once, where each step decides what happens next based on what the person did. In VoiceDrop a drip campaign is built in Sequences: you drag steps onto a canvas, join them up, and every contact walks the flow on their own.

An email drip campaign sends emails. This one opens with a ringless voicemail in your own voice, which lands in the voicemail box without the phone ringing, and sends a text only to the people who stayed quiet. Voicemails and texts leave from the same local number.

You launch the drip campaign with a contact list. That is the only way in today: there is no API, webhook, Zapier or CRM trigger that starts one for you.

Yes. Send SMS is one of the seven steps and goes out from your texting number, so a text can follow a voicemail, or replace it on the branch where the voicemail did not land.

Yes. The A/B split step divides people at random between two or more versions and you choose what share each version gets, so two voicemail scripts can run against the same audience.

The Wait for event step holds each person until they reply, call back, or ask to stop. Someone who calls back leaves down the It happened branch, so nothing else in the flow is sent to them. Everybody else runs out of time and carries on down the other branch.

Yes. Every sequence carries a status of Draft, Published, Paused or Archived. Pausing stops the engine sending for that sequence, and the button to start it again is labelled Resume. Archiving tidies it out of your main list without deleting anything, and you can put it back from the Archived tab.

Build the follow-up once and let it run

Sequences is in early access. Request access from your dashboard, and start with $20 in free credits - about 200 messages.