Home / Use cases / Logistics
Logistics & travel

WhatsApp for logistics, delivery and travel.

Tracking updates people actually read, delivery attempts that get rescheduled instead of failed, and itinerary changes that reach the traveller in their own language.

Start free → Talk to sales

The economics are simple here

In logistics, almost every support contact is a variation of "where is it", and almost every failed delivery is an avoidable second trip. Both are solved by the customer knowing something before they have to ask, on a channel they read.

A failed delivery attempt costs a vehicle, a driver's time and a redelivery slot. A message that lets someone reschedule before the van arrives is dramatically cheaper than the attempt that fails.

Shipment and delivery flows

  • Dispatched, with a tracking link. Sets the expectation and removes the first wave of enquiries.
  • Out for delivery, with a window. The message that most reduces failed attempts, because it is the one that makes someone stay in.
  • Reschedule button. If today does not work, let them say so before the vehicle is dispatched rather than after.
  • Delivery confirmation. Closes the loop and gives you a timestamped record.
  • Failed attempt with a next step. A failure notice with no action available generates a call. One with a reschedule button does not.

Travel

Booking confirmation, itinerary, check-in reminders, gate and schedule changes, and cancellation or rebooking options. Disruption is where this earns its place: when a flight moves, the airline that reaches the passenger first saves the call, and the one that does not receives it.

Time-critical updates are worth designing carefully. A gate change is useless an hour late, so build these as immediate triggers from your operational systems, not as a scheduled batch.

Language

Message templates can be created in multiple languages, and the right one selected per contact. For a delivery network operating across states, this is not a nicety: a tracking update in a language the recipient does not read is the same as no update, and it still costs you the message.

Store the preferred language as a contact attribute, set it from the order source or ask once, and select the template variant from it.

Volume and pacing

Logistics operations send in bursts, typically a large dispatch wave each morning. Two things matter at that shape.

Messaging limits are per rolling 24 hours, so a burst that exceeds your tier fails rather than queues elsewhere. Weflux paces sends to your current limit. And because these are Utility templates rather than Marketing, they are cheaper per message, which changes the arithmetic considerably at dispatch volumes. Get the template category right and the cost difference is substantial.

FAQ

Common questions from logistics and travel

Yes. A reschedule button on the out-for-delivery message lets them choose another day before the vehicle is dispatched, which is far cheaper than a failed attempt and a redelivery.
Yes. Templates can be created in multiple languages and selected per contact. Store the preferred language as a contact attribute and set it from the order source or by asking once.
Yes. Genuine transactional updates fall under the Utility template category, which Meta charges less for than Marketing. At dispatch volumes that difference is significant, so classify correctly.
Yes, through inbound webhooks and the REST API, so dispatch, out-for-delivery and delivered events can fire flows directly from your operational systems.
Messaging limits are per rolling 24 hours. Weflux paces sends to your current limit rather than firing everything and collecting failures. Limits rise as you send consistently with a good quality rating.

Related

Start with out-for-delivery.

The single message that most reduces failed attempts. One Utility template and a webhook from your dispatch system.

Start free → Talk to sales