WhatsApp for Shipment Exceptions
A shipment exception is any event that knocks a parcel off its expected path: a failed delivery attempt, an address that won't resolve, a courier hold, a customs or documentation snag, an out-for-delivery that keeps looping, or a return-to-origin about to be triggered. Every one of these needs a fast decision from the customer — reconfirm the address, pick a new slot, pay a COD balance, or authorise a reattempt. InfiQ moves that conversation onto WhatsApp, where Indian customers actually read and reply, so exceptions get resolved before they harden into RTOs and refunds.
Playbook TL;DR
Shipment exceptions handled by call or email leak into failed deliveries and RTOs because customers ignore both. InfiQ automates the exception alert on WhatsApp — triggered from your courier, OMS or store — with a one-tap reply that reconfirms address, reschedules, or authorises a reattempt, so more parcels land the first time.Why shipment exceptions quietly drain margin
The cost of a shipment exception is rarely the exception itself — it is the silence that follows. A courier flags 'consignee unavailable' or 'address incomplete', the parcel sits at a hub, and the clock starts ticking toward a return-to-origin. Your team tries a phone call the customer doesn't answer because the number is unknown, then an email that lands unread. Two or three attempts later the courier auto-triggers an RTO, and you eat the forward freight, the reverse freight, the re-stocking effort, and often the entire order value when the customer has already moved on. For COD-heavy Indian catalogues, unresolved exceptions are one of the single largest sources of RTO and blocked working capital. The failure is not logistics — it is communication that never reached the one person who could fix it in ten seconds.
- Failed delivery attempts that lapse into automatic RTO before the customer is even reached
- Address-incomplete and PIN-mismatch holds that stall a parcel at the last hub
- COD confirmation gaps where the customer never verified they still want the order
- Out-for-delivery loops where the rider and customer keep missing each other
- Customs or documentation exceptions on cross-border and regulated shipments
The WhatsApp exception workflow, end to end
InfiQ listens for exception events from your logistics stack and turns each one into a two-way WhatsApp conversation the moment it fires. When a courier webhook reports a failed attempt or an address hold, an approved template goes out on your verified business number — with the customer's name, order ID, tracking link and the specific problem stated plainly. Instead of a dead-end 'call us', the message carries quick-reply and interactive buttons: Confirm address, Change address, Reschedule delivery, or Talk to support. The customer taps once; their choice is written straight back to your order-management or courier system, and only the genuinely complex cases are escalated to a live agent. Because the reply arrives inside WhatsApp's free 24-hour service window, most follow-up during an active resolution costs nothing beyond the initial template message.
- Exception event fires from courier, OMS, WMS or store webhook
- Approved utility template sends instantly on your verified WhatsApp number
- Customer resolves in one tap — confirm, reschedule, update address or escalate
- The response syncs back to your system and, if needed, routes to a live agent
Templates and categories that keep you compliant
Getting the WhatsApp template category right is what keeps exception messaging both compliant and cost-efficient. A genuine shipment-exception alert about an order the customer already placed is transactional, so it belongs in the utility category — 'Your delivery for order #INFQ-4821 couldn't be completed. Reconfirm your address to reschedule.' Utility templates carry lower per-message pricing than marketing and are the right fit for reattempt prompts, address-confirmation requests, COD verifications and RTO-warning nudges. If you later want to win back a customer whose order already returned with a discount offer, that crosses into the marketing category and needs prior opt-in. InfiQ helps you draft, structure and submit these templates for Meta approval, so the transactional ones clear quickly and your library stays clean.
- Utility templates for reattempt, address-confirmation, COD-verify and RTO-warning flows
- Interactive quick-reply and list buttons so customers resolve without typing
- Marketing templates (opt-in required) for win-back after a return has completed
- Guided submission so your transactional templates clear Meta review fast
Plugs into the stack you already run
Shipment-exception automation is only useful if it fires from real logistics events, so InfiQ connects to the tools Indian sellers already use. Order and payment context comes from platforms like Shopify and your CRM, while exception and tracking events flow in from your courier aggregator, warehouse system or a lightweight webhook from your backend. When the customer updates an address or reschedules on WhatsApp, InfiQ writes that back so your OMS and courier stay in sync and the reattempt actually happens. Teams that prefer to build their own logic can wire everything through the InfiQ API and webhooks; teams that want it running today can start from prebuilt exception flows and go live within a day of onboarding.
- Order and customer context from Shopify and connected CRMs
- Live exception and status events from your courier aggregator or WMS
- Two-way sync so address changes and reschedules reach your systems
- Full API and webhook access for custom exception logic
Built for the businesses that ship most
Shipment exceptions hit hardest wherever volume, COD and last-mile complexity meet. D2C and marketplace sellers use InfiQ to cut RTO on high-value and COD orders by confirming intent before the courier attempts delivery. Logistics and 3PL operators run exception resolution as a customer-facing layer on top of their tracking, turning every 'consignee unavailable' into a scheduled reattempt. Pharmacies, grocery and perishables businesses use time-sensitive slot rescheduling so nothing spoils on a doorstep. Electronics, furniture and appliance brands handle high-ticket reattempts and delivery-window coordination where a single failed drop is expensive. In every case the pattern is the same: reach the customer on a channel they read, give them one tap to fix it, and keep the parcel moving forward instead of back to origin.
Frequently asked questions
What counts as a shipment exception?+
Do shipment-exception messages need customer opt-in?+
Which template category should I use — utility or marketing?+
How is WhatsApp billed for this, and what does InfiQ charge?+
Can the whole exception flow run automatically?+
Will this actually reduce my RTO rate?+
How does the resolution get back into my systems?+
How quickly can we go live?+
Still have questions?
Talk to an industry specialistStop losing parcels to silence
See how InfiQ turns every shipment exception into a one-tap WhatsApp resolution — book a demo and go live within a day.