Every template below is short, and that is the point. The most common mistake in WhatsApp outreach is pasting a cold email into a chat window: it arrives as a wall of text on a personal device and gets a block rather than a reply. Two or three lines, one question, no signature block.
Four rules apply to all of them. Identify yourself in the first six words, nobody recognises the number, so anything else is a scam by default. One question per message. No attachments or links in a first message. And never send outside local business hours; WhatsApp at 9pm is an intrusion in a way email is not.
First touch
Signal-based (best performing).
“Hi {{first_name}}, Ravi from Outboundry. Saw you are hiring two SDRs, usually means the email setup question lands on someone’s desk soon. Is that yours?”
Referred or mutual context.
“Hi {{first_name}}, Ravi here from Outboundry. {{mutual}} mentioned you are rebuilding outbound at {{company}}. Would a short conversation be useful, or is it too early?”
After a LinkedIn invite was accepted.
“Hi {{first_name}}, Ravi, we just connected on LinkedIn. I work on outbound infrastructure for teams around your size. Is deliverability something you are looking at this quarter?”
Cold, no signal. Do not. If you have nothing specific, the message is a broadcast and the channel punishes it. Use email, where the cost of a weak touch is a fraction of a cent instead of a block.
Follow-ups
First follow-up, two to three days later.
“Hi {{first_name}}, following up on the above in case it got buried. Worth ten minutes, or should I leave it?”
Second and last.
“Understood, {{first_name}}, I will stop here. If the SDR hiring goes ahead and the setup question comes up, my number is in this thread.”
Two follow-ups is the limit on this channel. A third is where blocks come from, and unlike email there is no version of persistence that reads as diligence.
Reviving a stalled thread
Timing objection.
“Hi {{first_name}}, you mentioned Q1 was the wrong moment. New quarter, has that changed, or should I check back later in the year?”
Went quiet after interest.
“Hi {{first_name}}, we got as far as pricing in March and then it went quiet, which usually means priorities moved. Should I close this off, or is it worth another look?”
Both work because they give an explicit exit. A revival message with no way to say no reads as pressure.
Meeting reminders, where WhatsApp earns its keep
This is the least glamorous use and the one with the clearest return. A calendar invite is a notification nobody sees; a WhatsApp reminder is read within minutes, and it measurably cuts no-shows.
Day before.
“Hi {{first_name}}, we are on for tomorrow at {{time}} {{timezone}}. Link: {{meeting_link}}. Still good?”
Fifteen minutes before.
“Starting in 15, {{first_name}}, {{meeting_link}}. See you shortly.”
No-show recovery, five minutes after.
“No problem if something came up, {{first_name}}. Same time Thursday, or would next week be easier?”
The no-show message is the highest-value template on this page. Sent within five minutes it reschedules a meaningful share of no-shows; sent the next day by email it mostly does not.
Voice-note scripts
After an unanswered call. “Hi {{first_name}}, Ravi from Outboundry, I just tried calling. Noticed you are hiring three SDRs this quarter, which usually brings up the infrastructure question. Worth ten minutes, or wrong quarter?”
Reviving a stalled thread. “Hi {{first_name}}, Ravi again. You said timing was the issue in March, so I am not chasing, just checking whether the new budget year changed that. If not, I will leave it.”
Both are under 30 seconds when read at normal pace. More on when voice notes land and when they do not.
Localising, briefly
In Brazil write in Portuguese, in Hispanic LATAM in Spanish; a translated first line with an English body reads as effort rather than laziness. In the Gulf, open with a proper greeting and keep the register formal even though the channel is casual. In India, English and directness are both fine. Full regional notes.
Next: what gets a number banned, or the 21-day ramp to run before sending any of this at volume.
Frequently asked questions
How long should a B2B WhatsApp message be?
Two or three lines with one question. A message the length of a cold email reads as a wall on a phone and is a common cause of blocks.
How many WhatsApp follow-ups should I send?
Two at most, then stop and say you are stopping. Unlike email, there is no version of persistence on WhatsApp that reads as diligence.
Should I send a cold WhatsApp message with no specific reason?
No. Without a signal or shared context the message is a broadcast and the channel punishes it with blocks. Use email for low-signal touches, where a weak touch costs a fraction of a cent.
Do WhatsApp meeting reminders reduce no-shows?
Yes, and it is the most reliable use of the channel. A reminder the day before and 15 minutes before gets read within minutes, and a recovery message sent five minutes after a no-show reschedules a meaningful share of them.
Do I need approved templates like the WhatsApp Business API requires?
Not with a QR-linked setup, which connects an existing number the way WhatsApp Web does. You write freely, and in exchange you take on the responsibility for ramps, caps and block-rate monitoring yourself.