A WhatsApp bot for courier and last-mile services
that answers where a parcel is, without a call
A courier customer's first instinct when a delivery feels late is to call, and a support line that cannot answer fast turns a minor delay into a bad experience. We build a WhatsApp bot that answers delivery status, pricing by distance and weight, and proof-of-delivery checks directly from your real dispatch data, so most questions never need to reach a human at all.
Why courier and last-mile services lose money today
A customer who feels a delivery is running late almost always reaches for the phone or a messaging app immediately, and a support team that cannot answer within minutes turns a normal delay into a frustrated customer and a support call that eats real staff time. The status that would answer the question usually already exists in a dispatch or tracking system, but reaching it still means someone stopping other work to check and reply.
A second cost is the pricing question that repeats for every new or occasional customer: what does a delivery of this weight to this distance cost. Answering this consistently, every time, by hand, takes dispatcher time that a rate-table lookup could handle instantly and more accurately.
A third, quieter cost is volume spikes. A courier that handles message volume comfortably on a normal day can see the same number of questions compressed into a few hours during a promotion or a holiday period, exactly when dispatch staff are busiest with the actual deliveries.
What we build
A WhatsApp bot that answers delivery status directly from your real dispatch system or tracking feed, so a customer gets an accurate, current answer any hour. Pricing lookup pulls from your real rate table by distance and weight, and proof-of-delivery checks confirm a completed order’s details without a dispatcher needing to look it up manually.
A short intake form handles new delivery requests or business client inquiries, asking for pickup, destination, weight and urgency before generating a quote or routing to dispatch. Every new order or flagged issue notifies the right dispatcher immediately, with a reference given to the customer so nothing gets lost during a busy period.
Typical integrations: your dispatch system or fleet management tool’s API for live status, your rate table as a structured feed, and your CRM if business client inquiries should land there directly.
What stays with humans
Every complaint, damage claim and compensation decision stays entirely with your team. The bot’s job is lookup and intake: it answers what the dispatch and rate data already say and collects what a dispatcher needs for a new request, then gets out of the way. Anything touching a complaint or a dispute is flagged and routed, never resolved automatically.
Price and timeline
| Model | Price | What you get |
|---|---|---|
| Agency runs it | from $900 | We build, launch and host the bot; you send rate and service-area updates as they change |
| Full control, handover-ready | from $1,530 | Same build, full source code and bot credentials transferred to your team, documentation included |
Both run on the same 1 to 2 week build for a single service area and language.
Related
Pair this with the fuller AI agent for courier and last-mile services if you also want business client intake and FAQ beyond status lookup, or a website for courier and last-mile services if new business clients need a proper quote request page too. See the full package breakdown on the development service page. An instant-delivery marketplace engine built on similar dispatch logic is detailed in the Telegram marketplace case study, and the OCR and document-automation work behind a similar status-lookup build is in the visa slot monitoring case study. Get a written plan with a fixed price for your fleet.
FAQ
How much does a WhatsApp bot for a courier company cost?
A single-service-area, single-language status and pricing bot starts at $900 and takes 1 to 2 weeks. A multi-area build with CRM integration for business clients starts at $1,500.
Can it resolve a complaint about a damaged or late delivery?
No. It answers status and proof-of-delivery questions from your real data only. Any complaint, damage claim or compensation request is flagged and routed to a human, never resolved by the bot.
How does it stay accurate during busy periods?
It checks your live dispatch system or tracking feed each time a customer asks, so the answer reflects the real current status, not a number that was accurate an hour earlier during a busy shift.
Can business clients request a delivery or get a quote through it?
Yes, through a short form that asks for pickup, destination, weight and urgency, so a quote or a dispatch request is generated from your real rate table instead of a manual lookup.
Does it connect to our dispatch or fleet system?
Yes, where it exposes an API or a reliable export. We build on a manual status log for operations without a dispatch API yet, which still beats a customer calling in to ask.