WhatsApp Shipment Exception Desk
Bilingual AR/EN WhatsApp exception desk on n8n for delay, damage and wrong-item flows. Points at AfterShip-class tracking and Extensiv / NetSuite ops handoff as targets—Origin is retail WhatsApp support applied to shipment exceptions; no invented deflection metrics.
- Logistics/3PL
- n8n
- AfterShip
- Extensiv
- NetSuite
Overview
The project at a glance
"Where's my order?" and "it arrived damaged" messages flood support. This page documents a self-hosted, bilingual (Arabic/English) WhatsApp agent pattern with per-customer memory, explicit flows for delay, damage, wrong-item and missing-item cases, and a clean handoff to a human — applied to 3PL and last-mile exception handling. Sell-side handoff points at AfterShip-class tracking and Extensiv-style WMS ops queues (targets, not delivered lookups).
Origin pattern: Pattern built for a bilingual e-commerce retailer, applied to shipment-exception handling. Not a claim that the original client was a 3PL.
What the engagement had to achieve
- Recognise exception types (delay, damage, wrong item, missing item, return, complaint)
- Collect the right details once, with bilingual AR/EN responses
- Remember the customer across turns (per-customer memory)
- Hand off to a human with a structured summary — without inventing delivery dates
The story
Exceptions arrive on WhatsApp, in two languages
What was at risk
The Challenge
In the Gulf especially, customers and consignees don't email, they WhatsApp. A single late or damaged delivery can generate a dozen messages across two languages. The CS team either drowns or bolts on a generic chatbot that confidently invents delivery dates. A 3PL or last-mile operator needs something narrower. It should recognise the exception type, collect the right details once, remember the customer's history and hand off to a person cleanly, without making promises it can't keep.
Delay and damage threads arrive as mixed Arabic/English WhatsApp traffic. Generic bots either stall or invent ETAs.
Free-form chat loses the reference number, photo, and exception type — so the human agent re-asks everything on handoff.
Live order-status / tracking lookup was an upsell in the source project and was not built. Carrier or WMS tracking APIs would be new work.
How we responded
The Solution
n8n + WAHA keeps conversation data on infrastructure you control. "Self-hosted" refers to this stack — not an official Meta partnership.
Responses in Arabic and English, with per-customer memory in Postgres so the agent does not re-ask known facts.
Rather than free-form chat: return/refund, exchange, wrong / missing item, damaged item, delivery delay, complaint. Flow-by-flow regression testing on real customer messages before go-live.
The agent summarises the case so the human agent doesn't re-ask. For a 3PL, handoff routes to ops or claims.
Tracking data would typically come from Aramex, SMSA, Naqel, Shipox, Quiqup-class platforms, AfterShip or carrier APIs. Those are integration targets — live tracking lookups are not claimed.
What we built
The concrete capabilities designed, built, and shipped in this engagement.
Self-hosted WhatsApp stack on n8n + WAHA
Conversation data stays on infrastructure you control. "Self-hosted" refers to this stack — not an official Meta partnership.
Bilingual AR/EN responses
The agent replies in Arabic and English so Gulf WhatsApp-first exception traffic is handled in the customer's language.
Per-customer memory in Postgres
Known facts persist across turns so the agent does not re-ask for reference numbers, photos or prior exception context.
Explicit exception decision-tree flows
Rather than free-form chat: return/refund, exchange, wrong / missing item, damaged item, delivery delay, complaint — mapped here to shipment-exception handling.
Structured human handoff
The agent summarises the case so the human agent does not re-ask. For a 3PL, handoff routes to ops or claims.
Flow-by-flow regression testing before go-live
Each exception flow was regression-tested on real customer messages before go-live. Live tracking lookup was an upsell and was not built.
The stack
The tools behind the build, and the role each one played.
n8n
WAHA
PostgreSQL
OpenAI
Extensiv
Integration target (sell-side) — not claimed as delivered.
NetSuite
Integration target (sell-side) — not claimed as delivered.
AfterShip
Integration target (sell-side) — not claimed as delivered.
MercuryGate
Integration target (sell-side) — not claimed as delivered.
FreightPOP
Integration target (sell-side) — not claimed as delivered.
QuickBooks
Integration target (sell-side) — not claimed as delivered.
Descartes
Integration target (sell-side) — not claimed as delivered.
Courier POD images
Integration target (sell-side) — not claimed as delivered.
What changed
Beyond the launch
Lasting improvements
The changes that keep paying off after the engagement ended.
- Outcome metrics: none claimed (no response-time or deflection figures)
- Design/process outcome: Explicit decision-tree exception flows instead of free-form chat that invents ETAs
- Design/process outcome: Structured human-handoff summary so ops/claims do not re-ask known facts
- Design/process outcome: Origin honesty disclosed on-page — retail WhatsApp pattern applied to shipment exceptions; live tracking lookup not claimed
Swipe to see more
All case studies
Want an outcome like this one?
A short workflow review maps where automation, AI, or a platform would pay off in your operation — and the first system worth building.