Global Markets (2)

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.

It is 5:30 a.m. A dispatcher sends a route condition update to a group chat on their personal phone. Fifteen drivers are in that group. Some are already on the road. Some have not left the terminal. At least two have the chat on mute.

The window between a booking confirmation and a guest's check-in is one of the most valuable communication opportunities a hotel has. It is also, at most properties across the Philippines, Indonesia, Thailand, Vietnam, and Malaysia, managed almost entirely manually. The same pattern holds at independent and mid-size hotels in Kenya, Tanzania, South Africa, and across much of East and Southern Africa. It likely holds across rest of APAC, EMEA and Americas too. 

The operators who have what global messaging platforms spend years and hundreds of millions acquiring (direct carrier agreements, registered sender IDs, shortcodes, and trusted enterprise client relationships) are losing ground to those same platforms. Not because the platforms have better connectivity. They do not. In most markets, a local gateway operator or regional aggregator has cleaner routes, better deliverability, and stronger carrier relationships than any global platform could replicate from the outside..

Something happened at one of your sites. An investigator is sitting across from you and they want to know whether the relevant workers were notified before the incident. You tell them your Safety Manager sent a text. The investigator asks to see the record.

At most mid-size hotels in the Philippines, the property management system and the guest messaging operation exist in two entirely separate worlds. Oracle Opera holds the guest record. It has the name, the booking date, the check-in date, the room type, the contact number. But the moment a guest needs to be reached for a pre-arrival confirmation, a reservation reminder, an upsell offer, or an in-stay promotion then someone leaves Opera, opens WhatsApp on a phone, finds the guest's number, and writes a message manually.

A digital reward in a SMS contest is a prize delivered directly to the winner's phone number at the moment of the draw: airtime credit, a mobile data pack, an app-specific bundle, or an e-voucher, with no physical handover, no staff coordination, and no delay between winning and receiving.

When a satellite detects a fire burning in a remote conservation reserve, the detection itself is not the hard part. The hard part is what happens next: getting the right message to the right people, across unreliable networks, in under sixty seconds, so that a field team can respond before the situation escalates.

The six weeks between ethics approval and your first survey wave are a strange period. The instrument is ready. The participant list is built. The field logistics are locked. And someone still has to figure out how to actually reach 400 farmers in western Kenya and northern Tanzania on a regular basis for the next 18 months, ask them structured questions, pay them something for their time, and bring back data clean enough to analyze.

Most messaging platforms sell you two things bundled together: a way to manage and automate your communications, and the routes those communications travel on. The bundling is usually invisible until you try to untangle it.

A messaging failover is the automatic rerouting of a message to a secondary channel when the primary channel fails to deliver  for example, switching from WhatsApp to SMS when a recipient has no internet connection, or from SMS to voice when a number is temporarily unreachable. Failover logic is the difference between a message that was sent and a message that actually reached someone. It operates invisibly when it works, and produces missed payments, missed appointments, and failed dispatches when it does not.

Most teams think about failovers as insurance. Something you set up in case things go wrong..