Blog

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.

Inbound communication in logistics is the system that handles messages originating from drivers, agents, and field personnel, exception reports, route change requests, delivery confirmations, and status updates, and routes them to the right person or automated workflow in real time. Most logistics communication systems are designed for outbound: dispatch instructions go out to drivers, delivery windows go out to customers. The inbound half, what happens when the field needs to reach the center, is the part that breaks under operational pressure..

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.

Automotive and EV brands in markets across Southeast Asia, South Asia, and Africa use WhatsApp and SMS to manage communication across a customer journey that spans months: from initial inquiry through test drive, purchase, delivery, and ongoing ownership. The communication requirement at each stage is different, lead qualification looks nothing like service reminders, and the channel mix shifts depending on where the customer is in the journey and what device and connectivity environment they are in.

From 1 July 2026, the Australian Communications and Media Authority's SMS Sender ID Register is live and in enforcement. If your organization sends SMS using a branded sender name, and that name is not registered, recipients are seeing the word "Unverified" where your business name should be. Their phone is grouping your message alongside other unregistered senders. Your delivery rate may hold, but your open rate and your customers' trust in what you send will not.