On this page
In short
- Shipment status updates sent from your system through the API as utility messages; delivery OTPs as authentication templates
- Exceptions (address issues, failed delivery, reschedule) handled in chat with buttons instead of calls
- Pickup bookings for senders, support routed by team, and B2B account updates
Logistics and delivery businesses use WhatsApp to tell customers where their parcel is before they ask, to confirm delivery with an OTP, to handle exceptions with buttons instead of calls, and to take pickup bookings from senders. VGraple CRM receives status events from your TMS through the API and turns them into utility messages, routes exceptions and support to hub teams, and runs pickups as appointments; the outcome is far fewer "where is my parcel" calls and failed deliveries resolved in chat.
The problem in numbers
Delivery businesses field the same call thousands of times: where is my parcel. Every one is avoidable with a status update sent at the moment the scan happens. Failed deliveries cost a second attempt because the customer could not be reached; an address query by phone waits for a callback. Delivery OTPs by SMS fail on poor networks. WhatsApp answers the status question automatically from your system's events, confirms delivery with an authentication template, and turns exceptions into a button the customer taps, all as utility or authentication messages at Rs 0.115, with the support conversation free once the customer replies.
Six things logistics teams automate on WhatsApp
1. Status updates from your system
Your TMS posts events (picked up, in transit, out for delivery, delivered, failed) to VGraple CRM through the REST API or webhooks; each sends a utility template with the tracking link as a URL button.
logi_out_for_delivery (utility)
Hi {{1}}, your parcel {{2}} from {{3}} is out for delivery today with {{4}}. Track: {{5}}.
REST API, webhooks, templates.
2. Delivery OTPs
An authentication template carries the delivery code with a copy-code button; the rider verifies it at the door.
logi_delivery_otp (authentication)
{{1}} is your delivery code for parcel {{2}}. Share it only with the delivery partner at your door.
Authentication templates through the API.
3. Exceptions handled with buttons
A failed delivery or an address issue sends a utility message with Reschedule, Update address and Call buttons; the reply updates the shipment through a webhook and reaches the hub team's queue.
logi_delivery_failed (utility)
Hi {{1}}, we could not deliver parcel {{2}} today: {{3}}. Tap Reschedule to pick a day, Update address, or Call to speak to the hub.
Flow builder with webhook nodes; team inbox with routing by hub.
4. Where is my parcel, answered by the flow
A Track button asks the tracking number and reads the status through a webhook; the AI answers policy questions; anything else lands with support.
logi_status (session, free)
Parcel {{1}} is {{2}} at {{3}}. Expected delivery {{4}}.
Flow builder with webhook nodes; AI chatbot.
5. Pickup bookings for senders
A flow collects the pickup address, parcel details and slot, creates the pickup as an appointment and sends a utility confirmation; a reminder before the slot; B2B senders get a daily manifest.
logi_pickup_confirmed (utility)
Hi {{1}}, your pickup is booked for {{2}} between {{3}}. Parcel: {{4}}. Reply to change.
Appointments and automation rules.
6. Key account updates
A team per key account; invoices, daily manifests and SLA reports as utility documents; new services and rate cards as marketing with consent.
logi_manifest (utility)
Hi {{1}}, today's manifest for {{2}} is attached: {{3}} pickups, {{4}} deliveries. Reply with any changes by {{5}}.
Teams under security and roles; broadcasts for consented marketing.
Hyperlocal delivery businesses use the same events with shorter timers: order confirmed, rider assigned with a live location message, and delivered, all within an hour, with the OTP as the proof of delivery.
Feature map
| Job | Feature | Plan |
|---|---|---|
| Status updates and OTPs from your system | REST API, webhooks, templates | Free |
| Exceptions with buttons | Flow builder, team inbox | Free |
| Tracking and policy answers | Flow builder, AI chatbot | Free; AI on Growth |
| Pickup bookings | Appointments | Free |
| Key account teams | Security and roles | Free |
| Rate cards with consent | Broadcasts, delivery protection | Free within Meta limits |
| Hub and support teams | Seats | Growth to Scale |
What it costs
A courier moving 30,000 shipments a month: four status updates per shipment, many inside windows opened by the tracking question, about 60,000 utility messages billed at Rs 0.115 for the ones outside windows, roughly Rs 5,500; 30,000 delivery OTPs (Rs 3,450); exceptions and pickups about Rs 500. Meta's total is about Rs 9,500 a month; VGraple CRM is Rs 7,999 on Scale with unlimited seats and conversations.
A 30-day rollout plan
Week 1. Connect the number; submit utility and authentication templates; connect the TMS through the API for status events; teams per hub.
Week 2. Status updates and OTPs live; the tracking flow with webhook lookup.
Week 3. Exception flow with buttons updating the shipment; support routing; the AI for policy questions.
Week 4. Pickup bookings for senders; key account teams and manifests; review call volume, failed delivery resolution and OTP delivery rate.
Getting the number ready
Most logistics businesses already run WhatsApp on the owner's phone, so the first decision is how to connect: coexistence keeps the WhatsApp Business app working on that phone while the team uses the inbox, with up to six months of history imported; an API-only connection suits a new number for the team. Either way, Embedded Signup takes a few minutes, the display name is reviewed by Meta, and business verification in Meta Business Manager lifts the marketing limit from 250 unique recipients a day to 1,000 and beyond. Submit the templates on day one; most are approved within the hour, and the template library has an industry collection ready to submit.
Consent, privacy and the rules that apply
A customer who messages first has consented to service replies and to utility messages about that transaction; marketing needs an explicit yes, recorded with source and date, and an opt-out on every marketing template. VGraple CRM records consent automatically from inbound messages, YES replies, forms, ads and imports, suppresses opted-out and blocked contacts before every send, honours STOP and Meta's app-level opt-out at once, and keeps marketing to United States numbers paused as Meta requires. Personal fields are encrypted at rest, access is by role and team, and the audit log records exports and deletions, which covers India's DPDP Act and GDPR for logistics data in practice. The opt-in rules guide has the detail.
Numbers to watch each week
First-response time on new conversations (minutes, not hours); the share of enquiries that reach the step that matters for logistics (a booking, a visit, an order, an enrolment); utility messages sent and how many were free inside open windows; replies to the last marketing send; and blocks on it, which should stay under 0.2 percent. The Analytics page shows them per agent and per campaign on Starter and above; the channel page shows the quality rating and tier, which the blocks feed. A yellow rating is the signal to tighten the segment before the next send, not after.
Common mistakes
- Status updates in batches hours after the scan; send on the event.
- Exceptions by phone call.
- OTPs by SMS on poor networks when WhatsApp delivers.
- Marketing rate cards to every sender regardless of consent.
- One support queue for every hub.
Why VGraple CRM for logistics
The REST API and webhooks for status events, utility and authentication templates with a validator, flows with webhook nodes for lookups and updates, teams and routing by hub, appointments for pickups, the AI for policy questions and broadcasts with consent and delivery protection are on every plan; Scale fits high-volume operations with unlimited seats. The REST API quickstart shows the status event calls.