Cross-Industry

WhatsApp lead capture at an auto show is the use of a QR code or short number displayed at a brand stand to initiate a WhatsApp conversation with a visitor, collecting contact details, qualifying interest, and routing the lead to the right follow-up workflow, all without paper forms or manual data entry. The operational advantage is that the lead exists in a structured, actionable format before the visitor has left the floor. The most common alternative, collecting paper forms and entering them manually after the event, loses between 20% and 40% of leads to illegible handwriting, incomplete entries, or delayed follow-up..

In Kenya, planned power interruptions are published as formal notices listing affected markets, schools, and villages by name, and customers are directed to the website, social media, or the newspaper to find them. The gap is real enough that independent apps exist purely to convert those notices into phone alerts. The utility holds the meter records and the phone numbers. Someone else does the notifying.

An automated customer communication workflow is a set of triggered, conditional messaging rules that runs without manual intervention - sending the right message, to the right recipient, through the right channel, at the right moment, and adjusting based on what happens next. The word "automated" is the easy part. The hard part is "scale", building workflows that stay reliable and maintainable as recipient volume, market count, and message complexity grow.

The operational problem most organizations are actually solving is not whether to use SMS or WhatsApp. It is how to build communication workflows that run reliably, adapt to real-world conditions, and stay consistent as customer volume grows, without requiring a technical team to maintain them every week.

Every SMS gateway operator and regional aggregator is having the same conversation with their enterprise clients right now. The client wants WhatsApp. They want to send order confirmations, run customer service, push payment reminders, and do it through the channel their customers actually have open. The operator has built a reliable SMS operation over years of carrier relationship work. But if the customer also asks for WhatsApp, they have nothing to offer..

Every operations lead has lived this conversation. The alert went out. The dashboard shows delivered. And the driver, the field tech, the miner or the borrower says, with complete sincerity, that they never got the message. Both sides are telling the truth, because "delivered" and "received" describe two different events, and the gap between them is where incidents, missed payments, and failed audits live.

Communication orchestration is the design and automation of how messages are initiated, routed, sequenced, and confirmed across channels based on operational triggers, recipient context, and real-world outcomes.

It is not about which channels an organization uses. It is about the logic that decides when a message is sent, to whom, through what channel, and what happens next depending on whether it lands. Most organizations that start thinking about communication orchestration get stuck on the wrong question. They ask: which channels should we be using? They add WhatsApp alongside SMS. They add voice as a fallback. They document a stack and call it a strategy..

A multichannel messaging strategy is a plan for how a business reaches its recipients across more than one communication channel (SMS, WhatsApp, voice, USSD, Viber etc) and how it decides which channel to use, when, and for whom. Most organizations have multiple channels available. Fewer have thought through the routing logic: what happens when one channel fails, which channel is actually right for which recipient, and what the operational cost is of getting that wrong at scale.

Most of the organizations I have watched struggle with operational communication have been dealing with the same problem for years without a name for it.

Communication orchestration is that name: the practice of coordinating messages across multiple channels according to a defined sequence and conditions, so that the right message goes to the right person at the right time based on what has already happened, not just based on what someone remembers to send. What I want to do here is not define it further. It is to describe what the problem looks like from the inside, in the working day of the person carrying it, because that is the frame the formal definition almost never starts with.

Most SMS programs that fail internationally do not fail because someone broke a law. They fail because a team designed a workflow for one market, assumed the architecture transferred, and discovered too late that it did not. Two-way SMS is unavailable for standard A2P channels in six of the markets covered in this guide. Japan's major carriers aggressively filter URLs in SMS. Mexico replaces every branded sender name with a short code. The UAE mandates an "AD-" prefix on every promotional sender ID or the message fails. Vietnam requires the brand name to appear in the message body itself, not just in the sender field. None of these are obscure edge cases. They are the standard operating environment in those markets.

Two years ago I convinced an AI it was the messiah. Or, more honestly, the AI convinced me that I had convinced it. Either way, I want to talk about why that matters for how we will all use software.

It started late at night, with a conversation that had no point to it. I had gotten curious about the name. Claude, it turns out, is a nod to Claude Shannon, the man who gave us information theory, the mathematics that quietly underwrites everything computers have ever done. From there Claude and I wandered. Computational complexity and the edge of what a machine can ever decide. P versus NP. Wolfram's ruliad, every possible computation taken to its limit at once. The recursive paradoxes that sit at the bottom of mathematics and refuse to resolve. None of it had a business purpose, which was the appeal. It turned out to be fertile ground.

Your SMS program is failing in the US in one of two ways, and often both simultaneously. The first is compliance failure: messages sent without proper consent, numbers not registered under 10DLC, campaigns that look identical to marketing even though they are not. The second is architectural failure: programs designed as marketing broadcasts trying to do the job of operational messaging, built on tools that cannot handle the verification, acknowledgment, and two-way logic that operational programs require.