1/7
Having someone's phone number isn't the same as permission to send them WhatsApp marketing. That's a separate opt-in. Here are 5 ways to collect it properly 🧵
6/7
In conversation
When someone in store asks about upcoming deals, invite them to opt in. Keep it separate from the question they came with, and capture the yes on a device so there's a record.
7/7
Whichever you pick, one rule holds: an existing number isn't an opt-in. Name who's messaging, why, and on which channel, and make leaving as easy as joining.
Full guide + wording examples: messageflow.com/blog/whatsap…
1/7
A lot of brands treat WhatsApp like an SMS blast with a green icon.
It runs on a different mechanic though: a 24h window built to reward relevance over volume. Get it right and it's a strong Black Friday channel. Here's how a campaign actually flows 🧵
6/7
It doesn't stop at checkout.
Order confirmations, shipping updates, a returns question next week: all in the same thread, through transactional templates. The relationship outlives the sale.
7/7
The pattern: consent, template, reply, 24h conversation, post-purchase.
Reach gets you seen. The window is where Black Friday sales get closed.
Full breakdown: messageflow.com/blog/whatsap…
1/6
SMS gateway and SMS API get used like synonyms when they're not. There’s a difference that decides whether your messages actually arrive.
Quick breakdown of what each one really is 🧵
5/6
Why it's worth knowing: the two are judged on completely different things.
Clean API docs are easy to admire on day one. Route quality, peak capacity, and whether a delivery report helps you diagnose an issue only show up once real traffic is flowing.
6/6
The real question isn't "gateway or API?"
It's whether the infrastructure behind the interface can carry your traffic reliably, at scale, to the countries you send to.
Full breakdown here: messageflow.com/blog/what-is…
