Skip to content
Logistics & Shipping · Website chat

A shipment tracking chatbot for your logistics website

A logistics website gets two kinds of question above all: where is my shipment, and what would it cost to ship with you. A website agent answers status questions in plain words and turns quote requests into complete leads for your sales team.

Updated

In short

What does a shipment tracking chatbot do on a logistics website?

It asks for the tracking number, looks up the status through a webhook to your tracking system, and explains it in plain language, such as what customs hold or exception at hub actually means and what happens next. It also answers service questions from your uploaded documents and, for new business, collects lanes, volumes and freight type for a quote.

Worked example

Translating status codes into plain answers

Status codes mean a lot to dispatchers and little to recipients. These are example statuses and the kind of answer you write once for the agent to use:

Example statusWhat the visitor reads
Exception at hubThe parcel needs a check at the sorting hub; it usually moves on the next scan. A team member is told if it does not
Held at customsCustoms is reviewing the shipment; you may be asked for documents or duties by the carrier
Address incompleteWe need a unit or apartment number; reply here and we will pass it to the depot
Delivered, signedIt was signed for at the time shown; if you do not have it, we will open a check

Write these in your own words and from your own processes. Visitors stop calling to ask what a code means.

Sales inquiries

Collecting a quote request that sales can price

For shippers, the agent asks the questions sales would ask: origin and destination, weekly volume, weight and dimensions, freight type (parcel, pallet, temperature controlled), and any hazardous goods. The lead lands in HubSpot, Salesforce, Zoho CRM or a Google Sheet with the transcript, so the first reply can include a price range instead of another form.

Setup checklist

What to connect and upload

  1. Tracking lookup through a custom webhook to your tracking system.
  2. Status glossary in plain words, like the table above.
  3. Service documents: coverage areas, cut-off times, prohibited items, claims process.
  4. Handoff rules: claims, damaged goods, complaints and contract questions go to people.

The agent is added with one line of embed code and trains on PDFs, DOCX files, spreadsheets or URLs. Chat answers go live in about 5 minutes once documents are uploaded; the tracking connection takes longer because it touches your systems.

Pitfalls

Do not let it guess a delivery time

If your system has no reliable ETA, the agent should say so and explain the next step rather than estimate. Do not show shipment details without the tracking number and a second check such as ZIP code. And keep pricing to ranges from your rate card unless sales has approved exact quotes in chat.

See logistics AI take a delivery exception report

Book a demo to map tracking questions or exception intake onto Botcadence with your service guide.

Common Questions

Shipment tracking chatbot questions

Yes, when you connect it to your tracking system through a custom webhook. Without that connection it can still explain statuses and processes but cannot look up a specific parcel.

No, it sits beside it. Visitors who are happy with the tracking page keep using it; the chatbot catches the ones who do not understand the status shown or need to ask what happens next.

Yes. It asks early whether the visitor is sending or receiving, then follows a different path: tracking help for recipients, account and quote questions for shippers.

The agent explains your claims process from your documents, collects the tracking number and a description, and hands the conversation to the claims team. Decisions on claims stay with your staff.

Start with one workflow

Start with tracking questions or exception reports

Begin with tracking questions and delivery-exception intake, then add proactive updates and rate-quote intake once ticket volume drops.

  • Reader-first workflows
  • Human handoff when needed
  • Grounded in your content

Ask AI about this page