Writing WhatsApp messages that get opened and read

Writing well for WhatsApp starts with an honest picture of how the message is read. It arrives on a phone, among messages from family and friends, and is looked at for a second or two while the person is doing something else. It is read in a narrow column, so a paragraph that looks compact on a computer becomes a wall of text on the device.

That context rules out most of the conventions businesses import from other formats. An email can afford a preamble because the reader has opened it deliberately and expects some structure. A leaflet can afford a headline and supporting copy because the eye takes in the layout at once. A chat message has neither affordance: it is read linearly, from the first words, by someone who has not committed to reading it at all.

So the first line does almost all the work. If it does not give the reader a reason to continue, the rest is not read, however good it is.

It also means the message is competing on a different axis than usual. It is not competing with other marketing; it sits next to a message from someone's mother. Anything that reads as corporate communication is conspicuous in that setting, and not favourably.

The most reliable improvement available is also the simplest: make each message about one thing.

A message covering three topics forces the reader to identify which parts concern them, and the usual response to that work is to skim, extract nothing, and move on. A message about one thing can be understood in the second the reader gives it.

This is harder than it sounds, because there is always a temptation to add. The business is already sending a message, so it may as well mention the other thing, and the offer, and the reminder about opening hours. Each addition seems free and each reduces the chance that any part is acted on.

Under per-message billing there is a real cost to splitting, so the discipline is not to send three messages instead of one. It is to decide what the message is for and leave out the rest. If two things genuinely both need saying, they are usually two messages to two different audiences at two different times — which is a segmentation decision rather than a writing one.

The category rules reinforce this. A confirmation with an offer attached is not a well-packed message; it is a marketing message under a utility label. Keeping one idea per message keeps categories clean as a side effect.

Line length matters more than word choice on a phone. A message broken into short lines, with breaks between distinct pieces of information, is scannable. The same words in one block are not, even if every sentence is simple.

The practical form is a line or two of context, then the specific detail on its own line, then what to do next. A reader looking for one fact — the time, the amount, the date — should be able to find it without reading the surrounding sentences. This matters most for exactly the messages people return to: confirmations and reminders are re-opened specifically to extract a detail, and one buried mid-paragraph makes the reader work for it.

Sentence length follows the same logic. A long sentence with several clauses requires holding structure in mind, which a reader glancing at a phone will not do. Two short sentences convey the same content at no cost.

What does not help is stripping vocabulary. Plain words are good, but replacing accurate terms with vaguer simpler ones makes messages longer and less clear, because the reader has to infer what was meant. Precision shortens messages; simplification for its own sake often lengthens them.

A message that opens with what the business wants — book now, check this out, don't miss this — has asked before establishing why the reader should care. On a channel read in a second, that ordering is usually fatal.

The useful inversion is to lead with the thing that is true and relevant to that person, and put the request after it. "Your usual size is back in stock" earns the request that follows. "Visit our store this weekend" does not, because nothing has been established.

This is also where segmentation and writing meet. A message can only open with something specifically relevant if the sender knows something specific about the recipient. A business sending one message to everyone is forced into generic openings, which is why undifferentiated sends read as advertising regardless of how they are phrased. The writing problem and the audience problem are the same problem.

Urgency deserves particular care. A genuine deadline or a real stock constraint is useful information and worth stating. A manufactured one is a claim about goods for sale, which is the territory the Commerce Policy governs, and readers who discover a fabricated deadline discount everything afterwards. Urgency is a fact to report when it exists, not a technique to apply.

Emojis work in moderation and fail in volume. One, marking the subject of the message or replacing a bullet, reads naturally in a chat. Several per line reads as noise, makes the message harder to scan, and for a message with any seriousness — a payment, a medical appointment — undermines it.

There is also a template constraint worth knowing: the number of emojis permitted in a template body is capped rather than unlimited, and authentication templates prohibit them entirely.

Formatting is available and best used sparingly. Bold for the one detail that matters — the time, the amount — helps a scanning reader. Bold applied to half the message helps nobody, because emphasis is relative and everything emphasised is nothing emphasised.

Tone should match how the business actually speaks to customers. A business whose staff are warm and informal in person should not become stiff and corporate in writing, and one dealing with serious matters should not be artificially chirpy. The mismatch is noticeable, and it reads as insincerity rather than as professionalism.

The register to avoid on this channel specifically is the promotional voice: capitals, exclamation marks, and the vocabulary of advertising. It is conspicuous next to messages from actual people, and it invites the block that a plainly written version of the same message would not.

Most improvement comes from cutting rather than rewriting. Two passes are usually enough.

First, remove everything the reader does not need. Pleasantries that convey nothing, restatements of the obvious, sentences explaining what the message is about instead of being about it. Ask of each sentence what the reader loses if it is gone; if nothing, it goes.

Second, check that the essential facts are findable without reading the whole thing. Read only the first line and ask whether it gives a reason to continue. Then scan for the specific detail — the amount, the time, the reference — and see whether it stands out or has to be hunted for.

Then read it on a phone. This is not optional advice, because line breaks, length and emphasis all behave differently on the device where the message will actually be read, and a message that looks tight on a computer often does not.

For templates, check with realistic values rather than tidy samples. A long name, an item description that runs on, a date in an unexpected format — templates that read well with sample data frequently break on real recipients.

And read the replies. Recurring confusion about a particular message is the most direct evidence available that its wording is not working, and it is more reliable than any amount of reviewing the copy in isolation.