WhatsApp is where customers in these markets actually are, and most businesses use it as a manual channel – a person reading a system and typing what it says. That is a lookup service staffed by a human, and it does not scale or run at night.
The useful version is event-driven. A visa stage moves to approved and the applicant is told. A driver is assigned and the passenger gets the vehicle and arrival time. An instalment falls due and a reminder goes out with the amount and the reference. Nobody types any of it, and every message is attached to the record that triggered it.
What runs in production today
Automated WhatsApp notification operates in FT-ERP for visa status and booking updates, and in Kingdom Drive for trip notifications. Both are event-driven from system state rather than sent by hand.
The honest constraint
Anything beyond notification – conversational flows, automated replies, a bot that answers questions – needs the WhatsApp Cloud API. That means a Meta business account, business verification, a phone number not already on WhatsApp, template approval for anything you initiate, and a per-conversation fee. It is justified once message volume makes manual handling the bottleneck, and not before. We will tell you which side of that line you are on rather than quote for the larger version by default.