The logistics playbook. Built in the builder, answered by your dispatch system.
Ten journeys, each drawn below as it runs. The decision comes from your dispatch, booking and order systems or criteria you set; the journey carries it. Aims are targets to agree in the pilot, not results.
Rescue the second failed attempt before the parcel comes back.
A second failed attempt at the same address takes the reason from your dispatch system; not home sends one WhatsApp with Pick a slot or Collect from hub, an unfound address asks for a shared location, and every answer is written back before the next run.
- Decides
- your dispatch system; the consignee.
- Aim
- fewer parcels returned to the shipper.
Confirm the cash-on-delivery order before it leaves the hub.
A cash-on-delivery order from a consignee who refused the last one triggers a call with a keypad answer, escalating to WhatsApp, then SMS, if unanswered; Confirm releases the dispatch, Cancel stops it, and the order is held until one arrives.
- Decides
- your order system; the consignee.
- Aim
- fewer refused parcels on the van.
Catch the shipper whose bookings are thinning.
A shipper whose bookings have fallen three weeks running enters a segment and gets one message from the account owner; a reply becomes a task in your CRM, silence waits, checks your system again, and ends in a call.
- Decides
- your segment definition; your booking data.
- Aim
- the leaving shipper reached before the last lane goes quiet.
Turn the quote that was never booked into a booking.
A session with a quote calculated and no booking checks consent, asks your rating engine whether the rate still stands, and sends it once with a tap to book; the tap creates the booking in your system and confirms the pickup.
- Decides
- your rating engine; the shipper.
- Aim
- more quotes that become bookings.
Add cover when the declared value deserves it.
A declared value above the standard cover asks your booking system whether cover is available for the lane and the value, then sends one WhatsApp with Add cover or Send as is; a tap adds it before the parcel leaves the hub.
- Decides
- your cover rules per lane.
- Aim
- cover sold without a call.
Turn three ad-hoc pickups into a subscription.
A third pickup booked in one week asks your system whether the shipper is already on a contract, then sends one WhatsApp with Daily pickup or Not now; a tap sets it up in your system and confirms the first collection.
- Decides
- your contract rules; the shipper.
- Aim
- ad-hoc volume moved onto a standing pickup.
Turn a slipped delivery into a choice the consignee makes.
A delivery that slips in your dispatch system sends one WhatsApp with Deliver tomorrow or Pick a slot; tomorrow updates your system and confirms by SMS, a slot fetches the open options from your system, and silence becomes a call.
- Decides
- your dispatch system; the consignee.
- Aim
- fewer failed deliveries and fewer calls.
Answer the tracking page before it becomes a call.
A session with the tracking page opened three times in an hour and no slot chosen fetches the rider's window from your dispatch system and sends it by push over our own network, with SMS if the push is not delivered.
- Decides
- your session rule; your dispatch system.
- Aim
- fewer where-is-my-parcel calls.
Fix the address before the van leaves the hub.
An address your dispatch system cannot map at the hub sends one WhatsApp asking the consignee to share a location or confirm the address; the pin is written back and the parcel released, silence becomes a call, and the parcel is held with an SMS if nobody answers.
- Decides
- your dispatch system; the consignee.
- Aim
- fewer address failures on the first attempt.
Deliver the handover code as the rider arrives.
A rider-arriving event from your dispatch system sends the code by push over our own network to app users, falls back to SMS on the carrier's failure signal, and goes straight to SMS on the OTP lane for everyone else.
- Decides
- your channel order for the OTP lane.
- Aim
- codes that arrive while the rider is at the door.
Where a step says your system decides, the journey calls your system and branches on its answer. xNotify carries the journey; it does not become the model.