Most writing about WhatsApp marketing is about sending. Almost none of it is about what happens after somebody answers, which is where the work actually is. This is the other half.
Step by step, for somebody with the console already open.
The code is written, it runs on your laptop, and it is sitting on GitHub. Then the instructions start saying “configure a reverse proxy” and it has been three weeks. This is what the missing step actually involves, what you can skip, and how to deploy by sending a message.
Read it →From nothing to a delivered message and a webhook carrying the reply. Copy-paste curl throughout, with the errors you will actually hit and what each one means.
Read it →A working agent in about twenty minutes: persona, knowledge, confidence threshold and handover. Including how to test it against real questions before it is anywhere near a customer.
Read it →Abandoned cart recovery works on WhatsApp and is the fastest way to get reported if you overdo it. This builds the version that does not: one message, correctly timed, stopping on reply.
Read it →Three things a WordPress site usually wants from WhatsApp, and how to set up each — including the form-to-WhatsApp bridge that most sites get wrong by tying it to email delivery.
Read it →Your business runs on sentences like “I’ll send the quote tomorrow”. They are not in a CRM or on a list — they are in a thread, and they are forgotten at a rate nobody measures because nobody can see it.
Read it →The moment you send someone to a payment page is the moment you find out how much they wanted it. Every step between “yes” and paid costs you some of the people who said yes.
Read it →Most advice about bans is about avoiding them. This is about the morning one happens anyway: what a standby number can carry across, what it cannot, and why setting it up afterwards is too late.
Read it →An email sequence that keeps going after somebody answers is rude. A WhatsApp sequence that does it is a report, and reports are what bans are made of. The rule is simple and almost nobody implements it properly.
Read it →Two ways to send WhatsApp from software, and they are not competing versions of the same thing. One is a Meta product with per-conversation pricing and a template approval queue; the other is the account already on your phone. Which one is right depends on whether you are broadcasting or replying.
Read it →“Sent” means WhatsApp took the message from you. It says nothing about whether it reached anybody. Here is what each acknowledgement really means, the failures that produce a tick and no delivery, and how to find out which one you are looking at.
Read it →A chat widget, a click-to-chat button and a QR code are three different trades between how many people start a conversation and how many you keep. This walks through all three, and why the answer for most sites is both of the first two rather than either.
Read it →Every growing business hits the same wall: one WhatsApp number, several people who need to answer it, and a phone that can only be in one pocket. The usual workarounds all break in the same place. Here is what actually has to happen.
Read it →Most WhatsApp bots are decision trees wearing a hat, and the ones that use a language model tend to invent answers confidently. Retrieval is the difference between a bot that quotes your refund policy and one that imagines it.
Read it →Email open rates for transactional mail are a known quantity and WhatsApp is not close to them. But a shop that pushes marketing through the same pipe as receipts loses the number. This covers both halves.
Read it →