WhatsApp for logistics and delivery
Shipment tracking, delivery automation and customer updates at scale — driven by the REST API and webhooks from your TMS or store. Fewer status calls, more first-attempt deliveries.
Why logistics ends up on WhatsApp
Logistics customer service is dominated by one question asked thousands of times: where is my order. Each instance is cheap; the aggregate consumes a department. Worse, the question is usually answerable by a system that already knows, which means the human is acting as an expensive lookup service.
The second cost is failed first-attempt delivery. A driver arrives, nobody is home, the parcel returns to the depot and the whole delivery cost is incurred again. Most of those failures are avoidable with a confirmed delivery window — but confirming windows by phone does not scale.
This is a systems integration problem more than a messaging one. The value appears when your TMS or store drives the messaging: shipment events fire template messages through the REST API, recipients confirm or reschedule in chat, COD orders are verified before dispatch, and proof of delivery comes back as a photo. Replies land in a team inbox with ticket numbers and SLA policies, so exceptions are worked as a queue rather than chased across handsets.
A delivery, driven by your system
Every step here is triggered by an event in your platform, not by a person.
- 1
Shipment event fires a webhook
Your TMS, WMS or store posts the event to Zapelite. A utility template goes out with tracking detail — no operator involved, and correctly categorised so the cost stays low at volume.
- 2
Recipient confirms or reschedules the window
The delivery window is offered in chat and the recipient confirms or moves it. This is the step that converts a failed first attempt into a successful one, and it is where the hard cost saving sits.
- 3
COD verified before dispatch
For cash-on-delivery orders, a confirmation flow verifies the order and the recipient before the parcel leaves the depot, which cuts returns on orders that were never going to be accepted.
- 4
Exceptions become tickets
A failed attempt triggers an immediate rescheduling flow. Anything needing a human lands in the team inbox with a ticket number and an SLA, so it is worked as a queue rather than remembered.
- 5
Proof of delivery captured
The driver or recipient sends a photo confirmation into the thread, and it attaches to the record. Dispatch instructions and route updates go out to the fleet on the same channel.
What teams actually run
Everything below ships in the product. See every feature or the integrations catalogue.
Live shipment tracking
"Where is my order?" answered by flows with real-time status from your API.
Delivery scheduling
Recipients confirm or reschedule delivery windows in chat.
COD confirmation
Auto-verify cash-on-delivery orders before dispatch to cut returns.
Failed delivery recovery
Instant rescheduling flows when a delivery attempt fails.
Delivery confirmations
Proof-of-delivery photos and confirmations collected via WhatsApp media.
Driver & partner comms
Dispatch instructions and route updates to your fleet, automated.
What changes
- The status enquiry stops reaching a human, because the update arrived before the question was asked.
- First-attempt delivery success improves when the window is confirmed in advance rather than assumed.
- COD returns fall when orders are verified before the parcel leaves the depot.
- Exceptions are worked as a ticketed queue with SLAs instead of being chased across personal handsets.
Build this first
Begin with a single event type — usually dispatch — wired from your TMS through the REST API. One template, one trigger, correctly categorised as utility. It proves the integration and immediately reduces status enquiries on that shipment stage.
Delivery-window confirmation is the second step and the one with the real money in it, because a confirmed window converts failed first attempts into successful ones. COD verification and proof-of-delivery capture follow naturally once the event pipeline is live.
Logistics, answered.
Yes, and that is the intended design. Your TMS, WMS or store posts events to Zapelite through the REST API or webhooks, and template messages fire automatically. The universal webhook connector and the n8n and Pabbly Connect bridges cover systems you would rather not integrate directly.
Status updates are utility templates, priced per delivered message by recipient country, and free inside an open 24-hour customer service window. Categorisation is the controllable variable — a dispatch notice miscategorised as marketing is billed as marketing, and at volume that difference dominates the bill.
Yes. The delivery window is offered in the thread and the recipient confirms or moves it. This is where the hard saving is, because a rescheduled delivery costs far less than a failed first attempt.
Yes. Photo confirmations sent into the thread attach to the conversation record, and can be pushed to your system through webhooks.
Yes. Dispatch instructions, route updates and partner notifications run on the same platform, with separate teams and routing rules from customer-facing conversations.
The reply lands in the team inbox as a real conversation with a ticket number and an SLA, routed by your rules. Automated messaging that cannot be answered is the most common complaint about logistics notifications, and this is what avoids it.
Other industries
Retail & E-commerce
Native Shopify and WooCommerce sync, cart recovery, pay-by-link and post-purchase review flows.
Food & Beverage
In-chat menu and ordering, payment in conversation, coupons and reorder prompts — without aggregator commission.
Automotive
Vehicle records, service booking, in-chat estimate approval and service-due reminders, on a dedicated vertical module.
See it running on your workflow
Book a demo and bring one real scenario from your operation. We will build it in the product rather than describe it on a slide.