Voicemail: what to say in 30 seconds

The most common decision about voicemail is not to leave one, usually on the reasoning that nobody listens to them.

That reasoning ignores what the alternative actually is. A call with no message does not leave a neutral absence; it leaves a missed call from an unknown number. The person sees it and has to decide what it was, with no information. In practice they assume it was a sales call or a wrong number, and they do not call back.

Worse, repeated calls with no messages produce a specific and damaging pattern: several missed calls from the same unknown number, which reads as either a persistent salesperson or something suspicious. The caller has managed to create an impression while conveying nothing.

So the choice is not between a voicemail and nothing. It is between a voicemail and an unexplained missed call. Even a mediocre message is better than that, because it converts an anonymous nuisance into an identifiable request that the person can act on when convenient.

A useful voicemail contains exactly four pieces of information, and almost every bad one is bad because it substitutes something else for one of them.

Who you are, including the business name. Your number, spoken slowly. The reason for the call, stated concretely. And by when a response is useful.

The reason is the item most often botched. Calling to follow up conveys nothing and gives no basis for prioritising a call back. Calling about the quote you asked for on the bathroom tiling is a reason, and it tells the person what the call concerns, so they can decide whether it matters.

The deadline is the item most often omitted, and it is what turns a message into something actionable. Without it, returning the call is an open-ended task competing with everything else. With a specific reason to respond by a particular time, it becomes something with a place in someone's day.

Four items fit comfortably in well under 30 seconds. Anything else in the message is competing with them.

Voicemail is a linear medium with no ability to skim, and this single property explains most of what makes a message fail.

A listener cannot see how long the message is, cannot skip to the relevant part, and cannot re-read. They are committing to unknown duration, which is why the decision to abandon comes early and why anything past roughly the first fifteen seconds is at real risk of never being heard.

The practical implication is that ordering matters more than in almost any other format. A message that spends its opening on pleasantries, an apology for missing them, and a preamble about how the caller hopes they are well has spent the part that gets heard on nothing, and the number arrives after the point of abandonment.

So: name and business first, reason second, number third and repeated, deadline last. If the message is cut off after ten seconds, the listener still knows who called and why, which is enough to return the call.

And say the number twice, at a pace someone could write down.

On a live call, tone can be corrected: the other person responds, and the caller adjusts. A voicemail has no feedback, so whatever tone it carries is the whole impression.

Two failure modes dominate. The first is sounding rushed, which happens because the caller is aware of the time limit and speeds up. This makes the number unusable, which defeats the message, and it communicates that the call is one of many being got through.

The second is sounding despondent — the flatness that comes from leaving the sixth voicemail of the morning. It is audible, and it invites the inference that the business is struggling.

What works is unhurried and matter-of-fact. Slower than feels natural, particularly for the number. Some people stand up to record a message, or smile while speaking, both of which measurably change how a voice sounds. Neither is a trick; they change what the voice actually does.

One more practical point: pause briefly before speaking. Recordings frequently begin partway into the first word.

Several things routinely appear and reliably reduce the chance of a callback.

Do not pitch. A voicemail is too short to make a case and the attempt uses the space the four essentials needed. It also converts an information message into an advertisement, which is what gets deleted.

Do not ask a question. There is nobody to answer it, and a question makes returning the call feel like an obligation to have prepared something.

Do not reference previous unreturned attempts in a way that carries reproach. Noting that this is the third time you have called adds an accusation, and the person now has to manage their own awkwardness before calling back, which most will avoid by not calling back.

Do not leave anything confidential — an amount owed, a health or financial detail — since a voicemail may be heard by someone else on a shared handset.

And do not promise to keep calling. It is meant as diligence and reads as a warning.

A voicemail is one contact in a sequence rather than a standalone act, and it works better when the sequence is designed with that in mind.

A reasonable pattern is to leave a message on the first attempt so the number is identified from the outset, then not to leave one on every subsequent attempt, since repeated messages saying much the same thing accumulate into pressure. Later in a sequence, a message is worth leaving again when there is something new, or as the final closing contact.

Pairing channels helps. A voicemail followed by a short text or message referring to it gives the person something they can act on without listening, and covers the common case of a voicemail never being played. Keep the text consistent with the message rather than adding new information.

What should be recorded, either way, is that a message was left and what it said — otherwise the next call repeats it.

Automix's Wani is a planned voice follow-up agent, documented at /docs/wani. It is not available to customers and places no calls today; the practice above is for whoever is dialling.