01
Delays and follow-ups in a WhatsApp flow
Almost every useful automation waits at some point. Here is what each waiting block does, and the one thing that breaks follow-ups.
02
When to use AI in a flow, and when to use buttons
The most expensive mistake in flow design is asking a language model to do arithmetic. Here is where AI genuinely earns its place.
03
Stopping a flow, and avoiding double messages
Every automation runs on the same incoming message. That is a feature until two of them answer at once.
04
WhatsApp automation mistakes that cost stores sales
Most broken WhatsApp setups are broken in the same ten ways. Here they are, with the fix for each.
05
Tagging and segmenting customers automatically
Every conversation tells you something. Three blocks decide whether you still know it next month.
06
Internal notes and team alerts from a flow
The most useful automations often send the customer nothing at all. They tell your team something at the moment it matters.
07
Calling your own system from a WhatsApp flow
One block turns a scripted flow into one that knows things — provided you build the path for when your server is asleep.
08
Reporting WhatsApp conversions back to Meta
Your ad delivers a conversation and then goes blind. Conversion reporting is how Meta learns which conversations were worth it.
09
Buttons, lists or free text: how to ask a customer something
The three-button limit shapes more of your flow design than anything else — and a tap is worth more than an answer.
10
Branching a WhatsApp flow without losing anyone
Some conditions split the flow. Others stop it. Confusing the two is why customers go silent halfway through.
11
WhatsApp automation for WooCommerce stores
WooCommerce is far less served than Shopify here — but only one part of the setup is genuinely different.
12
Selling on WhatsApp when you don't have a website
No store, no order events, no cart. The automation still works — it just has to be the storefront rather than sit behind one.
13
WhatsApp automation for online stores: what it can and can't do
The five flows worth building first, the ones that lose money, and the capabilities that quietly don't exist.
14
How to build your first WhatsApp automation, step by step
One complete flow, from empty canvas to live, with the two mistakes that catch almost everyone.
15
Every automation step, explained in plain English
The full palette, grouped by what it's for, with the setup each step silently depends on.
16
Keyword triggers that actually match what customers type
Why your 'refund' rule misses half the refund requests, and the keyword lists that don't.
17
Saving what a customer tells you, and using it later
Why your flow sends 'Hi ,' with nothing after it — and the two-minute fix.
18
After-hours auto-replies that don't annoy people
An out-of-office reply is the easiest automation to build and the easiest to get wrong.
19
AI that answers from your website, not from imagination
A general AI will confidently invent your returns policy. A grounded one won't — here's the difference and how to build it.
20
Click-to-WhatsApp ads: the 72 hours most advertisers waste
You paid for the click. Meta gives you three free days with that lead. Most advertisers use about ten minutes of it.
21
Testing an automation without messaging real customers
Almost nobody writes about this, and it is the difference between a flow that works and one that embarrasses you at scale.
22
How many WhatsApp automations should a store actually run?
The store that automates everything ends up muted, losing the order updates along with the offers.
23
Using a Google Sheet as your automation's database
The cheapest way to give a bot access to data you already keep, with no developer and no database.
24
Starting a WhatsApp flow from your own system
One small piece needs a developer. Everything after it you build yourself on the canvas.
25
When customers type Roman Urdu, Hinglish or mixed Arabic
Translation is not the problem. Transliteration and code-switching are, and they break keyword rules quietly.