Infrastructure · October 6, 2026 · intSignal Team

Voicemail Transcription: Useful, Until Someone Relies On It

Share this article

Voicemail-to-text turns a message you have to listen to into one you can scan. For anyone handling volume, that is a real saving — you triage a screen of messages in the time it takes to play two.

It is also wrong often enough to matter, in specific and predictable ways, and most deployments never establish how wrong.

Where it fails predictably

Numbers. The highest-consequence category. Phone numbers, order numbers, amounts and dates are exactly what callers leave messages about, and exactly what transcription handles least reliably — because a digit has little surrounding context to correct it. "Five one three" and "five one free" sound similar; only one is a number.

Names. Especially names outside the common set for the language model. A caller leaving their name is the most important part of the message and frequently the least accurately rendered.

Poor audio. Mobile callers in cars, on speaker, in wind, with background noise. Accuracy drops sharply and — importantly — the transcript does not indicate that it has.

Accents and non-native speech. Performance varies considerably, which is a fairness issue as much as a quality one: some of your customers consistently get a worse service.

Negation and short responses. "I can't make Thursday" and "I can make Thursday" differ by one contraction, and the meaning inverts.

The end of a message. People trail off, and the last few words — often the callback number — are where accuracy is worst.

The failure mode that costs money

The transcript renders a phone number with one digit wrong. Staff call it, reach nobody or the wrong person, and move on. The original caller is never called back.

From the business's point of view, nothing failed. The message was received, read and actioned. The customer's experience is that they left a message and nobody rang back.

This is invisible in any metric you are likely to have, which is what makes it worth designing against.

Deploying it sensibly

Always keep the audio accessible. The transcript is an index, not a replacement. One click to play the original, right next to the text. If your delivery method drops the audio — a transcript-only email — fix that first.

Flag low confidence, if the platform exposes it. Many engines produce a confidence score, and some surface it per word. Rendering uncertain words distinctively tells the reader where to be careful.

Train the one habit that matters: always listen before dialling a number from a transcript. Five seconds, and it eliminates the expensive failure mode entirely.

Change your outgoing greeting. Transcription accuracy improves markedly when callers speak clearly and say numbers slowly. Ask them to:

"Please leave your name, number — slowly, twice — and a brief message."

Repeating the number is the single highest-return change available, and it costs nothing. The second rendering gives staff a cross-check.

Route transcripts carefully. If voicemails may contain sensitive information, the transcript is a copy of that information in a second system. In a medical or financial context, that is a storage obligation and the destination must be inside your controlled environment.

Check your own accuracy

Do not accept a vendor's published rate. Establish yours:

Take 30 recent voicemails covering your real mix — mobile callers, noisy environments, your actual customer demographics. Compare transcript against audio and record:

  • Did it capture the caller's name correctly?
  • Did it capture the callback number correctly?
  • Is the substance right, including negations?
  • Would someone acting on the transcript alone do the right thing?

That last question is the one that matters. A transcript with minor word errors that still conveys the message is fine. One that reverses a meaning or corrupts a digit is not.

If callback number accuracy is below about 90%, treat transcripts strictly as an index and enforce the listen-before-dialling habit.

Where it is genuinely valuable

Despite the caveats, the feature earns its place:

  • Triage. Scanning ten messages to find the urgent one, without playing ten messages
  • Searchability. Finding the message from a particular customer weeks later
  • Accessibility. For staff who are deaf or hard of hearing, this is not a convenience
  • Noisy or quiet environments where playing audio is impractical
  • Record-keeping, with the audio retained alongside

The deployment that works treats it as a fast index into audio that remains the authority — rather than as a replacement that happens to be mostly right.

One configuration worth checking

Retention of transcripts and audio is frequently set independently, with transcripts kept much longer because they are small.

Decide both deliberately. A voicemail archive is a collection of customers describing their problems in their own words, and in regulated contexts it is more than that. "Indefinitely, because it's only text" is a decision made by default rather than on purpose.

Share this article