Blog

The usual setup at a mid-market hotel goes like this: reservations handles WhatsApp inquiries on one number. The front desk manages arrival coordination on another. Housekeeping works through a shared group chat. F&B takes room service requests through a fourth number entirely, saved in the personal phone of whoever is on shift.

Before I started Telerivet, I spent two years as a Peace Corps volunteer in Tanzania, working on local ICT skills in communities where a feature phone was often the only computer anyone owned. What stuck with me was not the technology itself, but how much people did with it once they could talk back instead of just receive.

When a mobile money payment arrives for a PAYGo solar account, a loan repayment, or a utility service, the payment itself is only half the workflow. The other half is the inbound confirmation: the system that detects the payment, parses the transaction details, matches it to the correct account, and triggers the downstream action, enabling the device, updating the balance, sending a customer confirmation. Most operators build the outbound half carefully and underinvest in the inbound half. That is usually when they discover what the inbound half costs when it fails.

An early warning system (EWS) that successfully alerts a dispatch team but fails to reach the community at risk has not completed its job. In disaster risk reduction (DRR) practice, the difference between a warning sent and a warning received, understood, and acted upon is often where lives are lost.

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.

Most fintech communication systems are built for one direction: outbound. Repayment reminders go out. Disbursement confirmations go out. Overdue alerts go out. The workflow is automated and the timing is configured. Then a borrower replies.
They have a question about their balance, a dispute about a charge, or a request to reschedule a payment. In most setups, that reply goes nowhere useful, and the borrower's next interaction is with a collections call they did not expect. Two-way communication in fintech is not a feature. It is what separates a communication system from a one-way broadcast pipe.

There is a specific moment when a lending operation discovers the ceiling of its messaging setup. It is not a deliverability failure. The reminders go out on time, at volume, month after month. The moment comes when a borrower replies to one of those reminders and nothing happens, because nothing was ever built to happen. We are seeing this play out right now with high-volume lenders sending millions of messages a month through providers they are otherwise satisfied with. They are not leaving because messages fail to arrive. They are leaving because the conversation only goes one direction.

Ask a high-volume sender what they value in a messaging platform and you will hear about deliverability, routing, and cost per message. Almost nobody says opt-out handling. Yet when we listen to what enterprise operators actually cite as their top value drivers after a year of running campaigns across multiple countries, automated opt-out handling keeps appearing near the top of the list. One global event operator named it among their top three.

A worker is injured at a remote site on a Friday night. Their crewmate calls a supervisor, who is off shift. The supervisor texts the site manager in the morning. The site manager mentions it to the safety lead on Monday. Somewhere in that chain, a legal clock has been running the whole time, because in Australia and New Zealand the duty to notify the regulator starts the moment the business becomes aware of the incident. Awareness travels exactly as fast as your reporting channel.

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.

Speed-to-lead in Philippine real estate refers to the time between a prospective buyer's inquiry and the developer's first substantive response. Research across markets consistently shows that lead conversion rates drop sharply when response time exceeds five minutes, and in a competitive condominium market with multiple developers running concurrent campaigns on the same portals and platforms, the developer who responds first wins the conversation.

Picture this- A prospective buyer submits an inquiry on a property portal at 3pm on a Saturday. They are looking at two condominiums from two developers. By Monday morning, one developer has responded twice: an immediate Viber message with a unit availability summary, then a follow-up that morning with a link to a virtual tour. The other developer sends an email at 9:15am Monday. By that point, the buyer is already scheduled for a site visit with the first developer.