How to Write a WhatsApp Broadcast People Welcome
How to write a WhatsApp broadcast: start with a reason the recipient would recognise, choose the audience, check the count and test it on your own phone.
To write a WhatsApp broadcast, start from a reason the recipient would recognise, send it only to the people for whom it is true, and make one point with one ask in a message that sounds like a person. Then test it on your own phone before anyone else sees it.
A good broadcast is short, specific and easy to answer. A bad one is a complete announcement addressed to everyone. The difference is almost never copywriting skill. It is the thinking done before the first word.
How to write a WhatsApp broadcast: start with the reason
Before you draft, finish this sentence from the recipient's side: "They sent me this because I ______." The ending has to be something specific and true.
| Honest ending | Verdict |
|---|---|
| "am on their list" | Do not send it |
| "asked about the blue one last month and it is back" | A message worth sending |
| "registered for the event and it starts tomorrow" | A message worth sending |
| "bought something this offer genuinely fits" | A message worth sending |
That one test does more for your read rates, your opt out rates and your standing on the platform than any technique. It also pushes you towards smaller, sharper groups. If you cannot complete the sentence, the problem is not the wording.
Choose the audience, then check the count
Send to the people for whom this message is true, not to everyone who might conceivably be interested. A narrow group gets more replies per message and fewer opt outs per send. It also protects against the asymmetric downside described in why people mute WhatsApp business messages.
Then look at the number of recipients you are about to message and compare it with the group you meant. The worst broadcast error is not a typo. It is a filter that silently did not apply, so a message meant for last month's buyers reached everyone. Check the count before you press send, every time, and if it surprises you, stop.
Exclude the people who have not read anything in a long time, and anyone who has asked to stop. Consent behind the list is covered in how to get WhatsApp opt in.
Write for the phone
The message is read on a small screen, in a notification preview, in the same list as a friend's message. Write for that.
- Identify yourself in the first line. The recipient may not have your number saved.
- Keep it short enough to read without scrolling.
- Make one point and one ask.
- Use at most one link, and only when the reply cannot do the job.
- Personalise only with information you are certain is correct.
- Sound like the person who will answer the replies. If the message starts a conversation, that person has to continue it in the same voice.
The first line carries the most weight, because it may be all that is seen before the recipient decides. Make sure it still makes sense when it is the only thing visible.
Handle missing details before they happen
Personalisation is a risk as much as a feature. A message that opens with an empty name, or the wrong one, announces itself as automated in the first word.
| Detail | Question to settle before sending |
|---|---|
| Name | What does the message say if the name is missing? |
| Anything about an order or a request | Is it certain to be correct for everyone in this group? |
| A link | Is it really needed, or can a reply do the job? |
| The sender | Does the first line say who we are? |
If you are not certain a field is reliable, leave it out. A plainer message that is right beats a personal one that is wrong.
Send it to yourself first
Send the broadcast to your own number and read it on your own phone. Check that the placeholders filled, the link works, the formatting survived and the first line makes sense in a notification preview. It takes two minutes. It is the only reliable way to catch the mistake you would otherwise hear about from a customer.
Send at their time, not yours
A message is read when it arrives, which means it interrupts whatever the recipient is doing. Schedule it for hours they are likely to welcome, in their time zone, on days that make sense for the content. Late night and early morning carry an extra cost on a channel this personal.
If your group spans several places, schedule by the recipient's clock, not yours. The sending tool may or may not support that, so check before you rely on it.
Be ready for the replies
A broadcast is an invitation to answer, and the replies will arrive together. Before you send, confirm that someone is available to answer, and that the replies will land in a place the team can see. If the answer is no, hold the broadcast. This is the handover described in WhatsApp broadcast versus conversation, and the practicalities of the inbox are in how to run a WhatsApp inbox.
Decide the number you will judge it by
Name, before sending, the number that will tell you whether the broadcast worked. It should not be the read rate. Read means opened. A campaign that was read and started nothing was noise with good delivery. Choose replies, and count the opt outs it cost alongside them.
A short broadcast checklist
- I can finish "they sent me this because I ______" with something specific.
- The message matches what these people agreed to receive.
- It has one point and one ask.
- The segment contains only the people for whom this message is true.
- I have looked at the recipient count and it matches the group I meant.
- The first line says who we are.
- Every personalised field is reliable, and I know what happens when one is empty.
- I sent it to my own phone and read it there first.
- It is scheduled for an hour the recipients will welcome.
- Someone is available to answer the replies.
Run it every time, including the urgent ones. Especially the urgent ones.
The shape of a good message
You do not need a clever sample to write a good broadcast. You need a reliable shape, and every part of it comes from the principles above.
| Part | What it does | Question to check it |
|---|---|---|
| Who we are | Tells a recipient who may not have your number saved who is writing | Would a stranger know? |
| Why you | States the reason in the recipient's terms | Does it finish "they sent me this because I ______"? |
| The one point | Gives the news or the fact | Is there only one? |
| The one ask | Invites a short reply | Can it be answered in a line? |
Read it aloud as the person who will answer the replies. If that person would not say it that way, rewrite it, because they will have to continue in the same voice.
Choosing a group that the message is true for
Picking the audience is where most broadcasts are won or lost. Work through it in order.
- Write the reason first, in one sentence.
- Describe the people for whom that sentence is true, using facts you actually hold.
- Build the group from those facts, and nothing wider.
- Remove anyone who has asked to stop and anyone who has not read anything for a long time.
- Check the count against what you expected.
If the count is far larger than the group you pictured, a filter has probably not applied, and the right move is to stop and find out why. Narrow groups feel small. They are the ones that reply, and they protect you from the penalty described in why people mute WhatsApp business messages.
Common slips in the draft
- Opening with a greeting that tells the reader nothing, when the first line should carry who you are.
- Putting the reason at the bottom, where it will not be read.
- Adding a second ask because the first felt too small.
- Adding a link when a reply would have done.
- Using a field you are not sure is filled for every recipient.
- Writing in a voice nobody on the team would use in conversation.
Each slip is fixed by cutting. A shorter message with one clear reason almost always beats a longer one that tries to cover every case.
Frequently asked questions
How long should a broadcast be?
Short enough to read without scrolling. One point and one ask is the shape that works on a phone.
Should I include a link?
At most one, and only when a reply cannot do the job. A link asks the recipient to leave the conversation, while a reply keeps them in it.
How often can I send?
Often enough to be useful and rarely enough that each one is still noticed. If you cannot give each send a reason the recipient would recognise, it is too often.
Can I use the same wording for everyone?
You can, if the message is true for everyone in the group. If it is not, the problem is the group, not the wording.
The full method, with the checklists, is in The WhatsApp Playbook, a free 31-page playbook.