I do solutions engineering and automation consulting work, and over the last year a chunk of that has been WhatsApp outreach campaigns for clients — onboarding sequences, re-engagement pushes, event reminders. Somewhere past the 10,000-message mark, a few patterns became impossible to ignore. Sharing them here since most "WhatsApp marketing" content online is either too API-heavy or too vague to be useful.
1. Personalization isn't optional, it's a deliverability mechanism
Identical mass-blasted text reads as spam to recipients and behaves like spam to WhatsApp's systems — number restrictions follow predictable patterns tied to repetitive, unpersonalized sends. Even swapping in {{name}} and one contextual detail (last purchase, last interaction date) measurably changes how a message lands. This isn't a nice-to-have, it's the difference between a campaign that works and one that gets a number flagged.
2. The official API is the wrong tool for one-off campaigns
The WhatsApp Business API is built for sustained, automated, high-volume messaging — chatbots, transactional notifications, multi-agent support. For a single re-engagement campaign to a few hundred or even a few thousand existing contacts, BSP onboarding and template approval add days of setup for something that should take an afternoon. I still reach for the API (I've used Brevo as a BSP) when the use case is genuinely automated and recurring — just not for everything.
3. Excel is still the best campaign database for small lists
Every "no-code automation" pitch eventually wants you to migrate your list into some new platform. For lists under a few thousand contacts, a clean spreadsheet with name, phone, and 2-3 custom fields is faster to maintain and easier to hand off to a non-technical team member than any dashboard. The tooling should adapt to the spreadsheet, not the other way around — which is why I ended up using WappHub, a Chrome extension that uploads the sheet directly and maps columns to message placeholders.
4. Delivery tracking changes how you write follow-ups
Without visibility into who actually received a message, every follow-up campaign is a guess. Once you can see delivered vs. not-delivered vs. read, the follow-up strategy gets a lot sharper — you stop re-messaging people who already saw it and ignored it, and instead focus effort on contacts where delivery actually failed.
5. Media attachments outperform text-only by a wide margin
For anything product or event related, a single relevant image attached to the message consistently outperformed text-only sends in response rate — anecdotally, by a significant margin. WhatsApp is a visual-first channel for most users; treating it like an email list undersells the medium.
The actual workflow
For context, the stack that produced these numbers was simple on purpose:
Client's existing contact list (Excel)
↓
Clean + dedupe + add custom fields
↓
WappHub Chrome extension (template + media + send)
↓
Delivery tracking → segment non-delivered for retry
↓
Manual reply handling for responses
No backend, no webhook, no API key. For campaigns under a few thousand contacts, that's been more reliable in practice than anything more "automated."
If you're running similar campaigns and want to skip the API setup for one-off sends, the extension I used is at wapphub.com — free trial available.
Top comments (0)