Skip to content

English draft · translated from the Russian original

A voice message needs a trailer

In 2020 I was interested in voice-message transcription. In 2026 I wanted a preview to help me decide whether to press Play at all.

19 October 20261 min readMarkdown ↗

interfaces language observations

An ear becomes a small cinema, with a red curtain, a projectionist on a ladder and film turning into a sound wave.

Text has a useful property: you can choose not to read it. Skim it, catch a few words, decide whether to stop. A voice message offers much less. Until you press Play, it is almost an opaque object.

In 2026 I found myself wanting a voice-message summariser. My reason was specific: it was not that I did not want to listen to Artemy’s message. I did not yet know whether I wanted to. I needed a preview.¹

Six years earlier, I had been thinking about voice-message transcription in VK. Voice messages suit the sender: you can talk on the move without requiring an immediate answer, as a call would. The recipient has a different set of circumstances: headphones, other people nearby, time and the ability to listen. Transcription helps the two sides meet.²

A useful feature can still land in the wrong workflow. Suppose someone records a message, gets a transcript, edits it and sends the text. Congratulations: you have invented dictation.³

A preview answers a different question. Show me what the recording is about before I commit several minutes to it. I may then decide that I would very much like to hear the voice.

My note about previewing voice messages, 2026. ↩
My discussion of voice messages and transcription, 2020. This is a historical account of a use case, not a comparison of current messengers. ↩
The continuation: when transcription becomes dictation. ↩

Markdown

A voice message needs a trailer

With your agent

Read-only MCP ↗

Request for this material

Verify “A voice message needs a trailer”: https://shipulin.md/en/blog/voice-message-preview/ Use the read-only shipulin MCP overview tool with lang="en". Match the exact URL path "/en/blog/voice-message-preview/", then call read_content with that entry's id and the same language. Separate the observation about voice-message previews from a general UX recommendation. Which contexts or counterexamples could limit it? State what the published material supports and what still needs verification. For numbers, check the period and basis. If linked sources have not been read, say so; do not present their contents as verified.

---
title: "A voice message needs a trailer"
description: "In 2020 I was interested in voice-message transcription. In 2026 I wanted a preview to help me decide whether to press Play at all."
date: 2026-10-19
lang: en
translationKey: "voice-message-preview"
translationStatus: machine
tags: ["interfaces", "language", "observations"]
related: ["ai-on-a-tap", "bot-voyage"]
sourceUrls: ["https://t.me/Shipao/809", "https://t.me/Shipao/810", "https://t.me/Shipao/2503"]
canonical: "https://shipulin.md/en/blog/voice-message-preview/"
---

Text has a useful property: you can choose not to read it. Skim it, catch a few words, decide whether to stop. A voice message offers much less. Until you press Play, it is almost an opaque object.

In 2026 I found myself wanting a voice-message summariser. My reason was specific: it was not that I did not want to listen to Artemy's message. I did not yet know whether I wanted to. I needed a preview.[^preview]

Six years earlier, I had been thinking about voice-message transcription in VK. Voice messages suit the sender: you can talk on the move without requiring an immediate answer, as a call would. The recipient has a different set of circumstances: headphones, other people nearby, time and the ability to listen. Transcription helps the two sides meet.[^voice]

A useful feature can still land in the wrong workflow. Suppose someone records a message, gets a transcript, edits it and sends the text. Congratulations: you have invented dictation.[^dictation]

A preview answers a different question. Show me what the recording is about before I commit several minutes to it. I may then decide that I would very much like to hear the voice.

[^preview]: [My note about previewing voice messages, 2026](https://t.me/Shipao/2503).
[^voice]: [My discussion of voice messages and transcription, 2020](https://t.me/Shipao/809). This is a historical account of a use case, not a comparison of current messengers.
[^dictation]: [The continuation: when transcription becomes dictation](https://t.me/Shipao/810).

Plain text, ready for your notes or agent.