Why Indian logistics is moving delivery updates to WhatsApp
Every shipment that goes quiet generates a phone call. Support teams call them WISMO calls "where is my order?", and each one ties up an agent for a few minutes that an automated message would have prevented. Multiply that across a few thousand shipments a day and the support desk is doing work a webhook should be doing.
SMS was the old answer, and it half-works: delivery reports are unreliable, links look suspicious, and a growing share of customers simply never open the messages folder. WhatsApp is where the customer already is. A tracking update lands in the same app as their family chats, the tracking link is tappable, and if something goes wrong they can reply in the same thread instead of dialling a call centre.
There's a second, more expensive problem WhatsApp attacks directly: failed deliveries. A rider reaches the address, no one answers, the shipment travels back, and for COD orders that often becomes an RTO, where you pay freight both ways and sell nothing.
A message the evening before delivery, asking the customer to confirm they'll be available or pick a new slot, prevents a meaningful share of those failed attempts. Our guide on reducing COD RTO with WhatsApp goes deeper into that flow.
Courier tracking messages, triggered by your own systems
The point of the API is that nobody sits and sends these messages. Growcord exposes a REST API and webhooks, so your TMS, OMS or shipment-tracking software calls one endpoint when a status changes and the customer gets the update seconds later.
If your stack is Shopify or WooCommerce, the order notification automations work out of the box; for anything custom, one POST request per status event is all it takes. Replies "can you deliver after 6 pm?", "the flat number is 402, not 302", land in a shared team inbox where your customer support or last-mile coordinators answer from one screen.
What logistics teams run on Growcord
Shipment status updates
Automated messages at pickup, in transit, out for delivery and delivered, each with the AWB number and a tracking link.
Address confirmation before dispatch
Ask the customer to confirm the address and landmark before the parcel leaves the hub, not after the rider is lost.
Failed-delivery (NDR) rescheduling
When an attempt fails, the customer gets a message with reschedule options instead of a silent return to origin.
COD verification
Confirm cash-on-delivery orders before shipping. Fake and impulse orders drop out before they cost you two-way freight.
Out-for-delivery with rider details
Share the delivery window and a contact number on the morning of delivery so the customer plans to be reachable.
One inbox for delivery queries
Replies from every shipment flow into a shared team inbox. A bot answers tracking queries; agents handle exceptions.
Message templates that work for couriers
These are utility templates. Meta approves them quickly because they relate to a transaction the customer initiated. Three examples you can adapt:
Out for delivery. "Hi Ramesh, your parcel from Meena Sarees (AWB 78412356) is out for delivery today between 11 am and 3 pm. Rider: Suresh, 98XXXXXX21. Please keep ₹1,249 ready, it's a cash-on-delivery order. Track live: [link]."
Failed attempt / NDR. "We tried delivering your parcel (AWB 78412356) at 1:40 pm today but couldn't reach you. Reply 1 to get it re-delivered tomorrow, 2 to choose another day, or 3 to update the delivery address. Unclaimed parcels return to the seller after 3 attempts."
Delivery slot confirmation. "Your order from Kanpur Leather Works arrives tomorrow. Will someone be available at B-14, Ashok Vihar between 10 am and 6 pm? Tap Yes to confirm or Change slot to pick a better time."
Each of these uses merge fields, name, AWB, amount, address, filled per shipment from your data, and quick-reply buttons so the customer answers with a tap. More patterns are in our template message examples library.
How a courier company goes live
Connect your number
Bring a fresh number or one already on the Business app onto the WhatsApp Business API through Growcord's guided Meta signup, typically done in under an hour.
Create your status templates
Write templates for each shipment stage with merge fields for AWB, amount and address, and submit them to Meta from inside Growcord.
Wire up your tracking system
Point your TMS or OMS at the send-message API, or use the Shopify, WooCommerce or Zapier integrations if orders live there. Each status change triggers the matching template.
Route replies to the right people
Set a bot to answer tracking queries automatically and assign exception messages, wrong address, reschedules, complaints, to your support agents in the shared inbox.
What it costs per shipment
Delivery updates are utility conversations in Meta's pricing, the cheapest paid category, currently around ₹0.12 per 24-hour conversation in India, and multiple updates for the same shipment within that window count as one conversation. So a shipment that gets picked-up, out-for-delivery and delivered messages inside 24 hours usually costs one utility conversation, not three. The conversation pricing guide explains the categories.
On top of Meta's fees, which you pay at Meta's published rate, with no markup from us, Growcord's platform fee starts at ₹299/month (₹99/month billed yearly). A hub shipping a few hundred parcels a day runs past Startup's 1,000 included conversations inside a week, so Commerce at ₹1,999/month (₹999/month yearly) is the working tier, with extra conversations at ₹399 per 1,000 beyond it.
Every plan includes the API, webhooks, the shared inbox and bots, see the full pricing breakdown. The free tier (1 number, 50 conversations a month) is enough to pilot the flow on one lane, and paid plans carry a 7-day unconditional money-back guarantee.
Put your shipment updates on WhatsApp
Start free with 50 conversations a month, enough to run a pilot on one delivery route and count the WISMO calls that don't happen.
Start free, no card neededWhy Growcord
What you get here that you don't get elsewhere
Frequently asked questions
Can we send tracking updates automatically from our own software?
Yes. Growcord gives you a REST API and API keys: when a shipment status changes in your TMS or OMS, your system makes one API call and the customer receives the matching approved template with their AWB and tracking link merged in. Webhooks push replies and delivery receipts back to your system, so the integration works in both directions.
Do customers need to save our number to get delivery updates?
No. Messages sent through the WhatsApp Business API reach any opted-in customer whether or not they saved your number. Your brand name and logo appear in the chat header, which is also why customers trust these updates more than an SMS from a random six-digit sender ID.
What does a delivery update cost per shipment?
Delivery updates bill as utility conversations, currently around ₹0.12 in India for a 24-hour window. Several updates for the same shipment inside that window count as one conversation. Growcord's plan fee starts at ₹299/month (₹99/month billed yearly), and the estimated credit cost shows before any campaign or automation goes live.
How does WhatsApp reduce RTO for COD shipments?
Two automations do most of the work: a COD confirmation message right after the order, which filters out fake and impulse orders before you ship, and a pre-delivery confirmation that asks the customer to confirm availability or reschedule. Failed attempts and silent returns both drop when the customer has actually agreed to the delivery slot.
Can multiple support agents handle delivery queries on one number?
Yes. Replies from all shipments land in Growcord's shared team inbox, where any number of agents (per your plan's seat count, extra seats at ₹149/month) work from the same WhatsApp number with assignment and full conversation history. A bot can answer routine tracking questions before a human ever sees them.
Will sending thousands of updates a day get the number banned?
Not on the official API, transactional updates to customers who ordered from you are exactly what the channel is built for. Meta assigns your number a messaging tier that grows with volume and quality. Bans hit unofficial bulk tools that automate the consumer apps, which is a different thing entirely.
Why businesses pick Growcord
Official WhatsApp Business API
Built on Meta's Cloud API, the sanctioned channel, not a modded app. No number-ban roulette.
Indian pricing, GST invoice
Plans from ₹99/month billed yearly. Paid in ₹ via Razorpay, with a proper GST invoice every time.
Free tier, no card needed
1 number and 50 conversations a month to prove it on real customers before paying anything.
Support from New Delhi, in IST
A real team on email and WhatsApp, Monday to Saturday 10:00–19:00 IST, not a ticket void.
Talk to us
Get set up on WhatsApp this week
Tell us what you sell and how many customers you message. We'll reply on WhatsApp with the plan that fits and, if you want it, walk you through the Meta approval step.
- No sales call unless you ask for one
- Answers from the team that builds it, in IST hours
- Free tier available. You can start before you decide
Keep reading
Related guides and comparisons
Last updated: 2026-08-07