
Lead generation
Where a WhatsApp Lead Comes From Is Not WhatsApp
Nobody discovers a business by browsing this channel. Leads arrive through a door you placed somewhere else, and the door decides what you know when they walk in.
5 min read
Writing
Notes on Instagram’s API, the replies a tool should refuse to send, and the parts of automation that are easy to get wrong. Written by the people who ship it.

Lead generation
Nobody discovers a business by browsing this channel. Leads arrive through a door you placed somewhere else, and the door decides what you know when they walk in.
5 min read

Playbooks
This channel has no public comments, so nothing fires until somebody writes to you first. That single fact changes the words you match on and how you find them.
5 min read

Playbooks
Two different things get called verification on this platform, and only one of them is required to send. Nobody can promise you the other one, including us.
5 min read

Compliance
GDPR is not DPDP with different words. Where the two diverge for a messaging channel, and which parts of the problem software can genuinely help with.
4 min read

Playbooks
We have no flow builder on any channel, and the canvas is the wrong picture anyway. Every stage here is a question about who is allowed to speak next, and why.
5 min read

Compliance
Restrictions on this channel are usually earned by message quality rather than by volume. What actually triggers them, and what a tool can and cannot do about it.
4 min read

Product
Flows is a Meta feature that puts a structured form inside a chat. What it solves, what it costs to build, and the cases where a plain conversation wins.
5 min read

Compliance
Sending the ask is the easy part. What destroys the data — and in places the legality — is paying for answers or routing unhappy customers away from the public form.
5 min read

Compliance
Before any question about obligations, a simpler one: what data does this channel generate, who ends up with a copy, and how much of it did you choose to collect?
4 min read

Playbooks
Deflection is the wrong goal. The job is to clear the repeated factual questions so the people on your team spend their day on the messages that needed a person.
5 min read

Playbooks
The journey map that helps is built by reading two hundred threads and coding four things about each. The one drawn in a meeting describes a customer nobody has met.
5 min read

Product
Leads leave as a downloaded file, on every channel. That is a real limitation, and a file also avoids a specific set of failures that two-way sync quietly introduces.
5 min read

Playbooks
There is no analytics product here and no attribution anywhere. What is genuinely observable on a messaging channel, and the one lever that actually moves.
5 min read

Comparison
Almost everything about a WhatsApp conversation follows from who spoke first — the window, whether a template is required, and how the thread gets charged.
5 min read

Playbooks
Confirming a cash-on-delivery order before dispatch is one of the few genuinely useful automations in Indian ecommerce. It is also easy to word dishonestly.
5 min read

Comparison
They share a logo and almost nothing else. What each one is for, what you give up moving between them, and how to tell which one you actually need.
5 min read

Tutorial
No-code removes the typing, not the thinking. Here is what you actually fill in on a builder screen, and the six decisions no builder can make for you.
5 min read

Lead generation
Someone asked the price and vanished. What a follow-up can legally do inside Meta's window, when it converts, and the message that does not read as a chase.
4 min read

Playbooks
Here the number and the consent may genuinely exist, so the obstacle moves. It becomes a message about stock, price and delivery that your system cannot actually confirm.
5 min read

Compliance
Which WhatsApp Business rules are actually enforced, what changed this year, and a working checklist — instead of re-reading the whole policy every time Meta edits it.
5 min read
Prefer a feed? RSS.