WhatsApp for logistics and delivery
Delivery comes down to one thing the customer wants to know: where is my parcel and when will it arrive, and every failed drop or unconfirmed cash payment costs a second trip and driver time. trtWhats connects your system through API and webhooks to turn each status change into a WhatsApp message and pull driver coordination into a single shared inbox.
What your customer receives
The automation flow for this sector
- 1
Parcel picked up
As soon as the shipment is created in your system, the customer gets a confirmation with tracking number, destination and estimated time.
- 2
Status update
In sorting, on the way, nearly there: each status goes out automatically via webhook from your system.
- 3
Delivery-window confirmation
Before dispatch, the customer confirms the window or proposes another time with one reply, cutting failures.
- 4
Driver on the way
A notification announces the driver is coming, with a tracking link and contact number, so the customer is ready.
- 5
COD collection confirmed
After handover, the system confirms the cash amount collected and sends a PDF receipt to the customer.
- 6
Reschedule a failed delivery
If a drop fails, the customer picks a new date from the message, and the route is replanned without calls.
What it fixes
Failed deliveries and second trips
An absent customer or unconfirmed address forces a costly second trip. Confirming the window ahead on WhatsApp reduces wasted attempts.
'Where is my parcel?' floods the office
Tracking calls never stop. Automatic status updates arrive before the customer asks, easing pressure on customer service.
Unconfirmed cash-on-delivery
Cash payment without a receipt creates disputes. Collection confirmation and a digital receipt document every transaction immediately.
Scattered driver coordination
Driver messages on personal phones get lost. A shared inbox pulls messaging, assignment and tags into one place.
In delivery, every parcel is one question in the customer's mind: where is it and when will it arrive? While the answer stays vague, customer-service lines fill with tracking calls, and a customer who is out when the driver arrives makes the attempt fail and triggers a second trip at full cost. trtWhats connects your shipment-management system through the REST API and webhooks, so each status change — parcel received, in sorting, out for delivery, nearly there — becomes a WhatsApp message sent automatically to the customer from your carrier's number. Customers know where their parcel is before they ask, and the volume of calls that occupy the office without adding value falls.
The costliest point is the failed delivery. An imprecise address or an absent customer turns one trip into two and delays the rest of the route. Before the driver leaves, trtWhats sends a delivery-window confirmation; the customer confirms with one reply or proposes another time, and if the drop fails they pick a new date from the message itself, so the route is replanned without a call. When the driver sets off, a 'driver on the way' notification arrives with a tracking link and contact number, and the customer is ready at the door. These messages are utility templates tied to an ongoing shipment, cheaper than marketing; Meta requires prior opt-in naming your business and WhatsApp before any template.
Cash on delivery needs clear traceability. After each handover, trtWhats confirms the cash amount collected and sends a PDF receipt to the customer; in Morocco, invoices are issued in a format aligned with the DGI's e-facture regime, and in Saudi Arabia in a format meeting the requirements of ZATCA phase 2 (XML and PDF/A-3 with a QR code). Driver and dispatch coordination happens in a shared inbox: field messages land in one place, with assignment to a supervisor and tagging by zone or status, so nothing is lost on a personal phone. Meta's per-message fees stay on your Meta account with no markup from trtWhats, while platform-side conversations remain unlimited on every plan.
For carriers that move real volume, the numbers matter. Meta's quality rating (green, yellow, red) and the per-number messaging limits — starting at 250 unique users a day and rising to 1K, 10K, 100K and beyond — climb as your sending stays clean and opted-in. The Pro plan adds a second number and WhatsApp calling with IVR for a dispatch line, and Business and Enterprise add more numbers and higher throughput for peak periods. The AI flow builder turns a plain-language description of your status updates into a branching flow, so a non-developer can map 'out for delivery', 'failed' and 'rescheduled' without code. Shipment data is processed on our own servers in the EU, in line with Morocco's law 09-08 (CNDP), with a data-processing agreement on request, and Meta's per-message fees are never marked up by trtWhats.
Features that matter here
Sector questions
trtWhats
Let's build your next growth channel.
- Free 20-minute consultation with a WhatsApp specialist
- Number live in 24–72 hours once documents are ready
- Official Meta API with opt-in messaging and approved templates