Where is my order calls
Proactive tracking updates reduce support load when triggered from your dispatch system.
Logistics · WhatsApp API
WhatsApp API for logistics sends shipment alerts, rider ETAs, delivery confirmations, and COD verification. Delivery events must come from your TMS or rider app via API or webhook — Ominiflow does not track parcels by itself.
Shipment tracking, delivery ETAs, failed delivery recovery, and COD confirmation for last-mile logistics teams across India and the GCC — higher read rates than SMS for many routes, when customers have WhatsApp.
WhatsApp API for logistics sends shipment alerts, rider ETAs, delivery confirmations, and COD verification. Delivery events must come from your TMS or rider app via API or webhook — Ominiflow does not track parcels by itself.
WhatsApp often achieves higher open rates and supports buttons for confirm and reschedule actions. SMS still matters for customers without WhatsApp or in low-data scenarios — many logistics teams use both.
Last updated: September 2026
Proactive tracking updates reduce support load when triggered from your dispatch system.
Instant re-schedule links on WhatsApp recover attempts — customer must respond for the slot to stick.
AWB, ETA, and rider contact in Utility messages.
Failed delivery → customer selects reattempt slot in chat.
Out for delivery → COD confirm YES/NO → delivered proof photo or OTP.
WhatsApp often achieves higher open rates and supports buttons for confirm and reschedule actions. SMS still matters for customers without WhatsApp or in low-data scenarios — many logistics teams use both.
Your TMS, OMS, or rider app sends shipment events to Ominiflow via API or webhook. Each status change maps to a Utility template. Without that integration, updates are manual or batch uploads.
Riders typically use your dispatch app; customers get automated updates from the business number. Direct rider-customer chat on the brand number is possible via the team inbox but is uncommon for high-volume last-mile.