Logistics & Transport /Drafting live field guide · 8 min

Shipment-Status Responder

Reads inbound "where is my order?" enquiries, pulls the current milestone and ETA from your TMS and carrier feeds, and drafts a cited reply for a person to approve — escalating any delayed or unavailable shipment instead of inventing a time. It never sends on its own.

Open the live demo

theater/demos/logistics_shipment-status-responder.html · sandbox · read-only

Open

FIG. 1

The live demo, running on fabricated data. Open it to step through the full flow — every output is shown for a person to approve before anything happens.

How it would work

Reads each "where is my freight?" enquiry, matches it to the consignment in your TMS, pulls the latest carrier scan and ETA, and drafts a cited reply for a person to approve before it sends.

Input 01

The enquiry + the freight record

A customer's status enquiry — usually a consignment or order reference — matched against the TMS consignment record, the carrier's scan history, and the customer's service-level terms.

Agent 02

Matches, reads, drafts

Resolves the enquiry to one consignment, reads the latest milestone scan and current ETA, checks it against the SLA, and drafts a reply citing the tracking reference and the timestamp of the last event.

Output 03

A draft, with its source cited

A complete reply with the consignment reference, last scan and ETA shown, laid out for a dispatcher or customer-service officer to review, correct and approve before it reaches the customer — delayed or ETA-less shipments are escalated, not answered.

Where it works well

It answers the routine WISMO enquiry in seconds and cites the scan it read.

Best where most enquiries are routine "still on track" lookups with a clean consignment or order reference to match on.
At the WISMO volumes a busy dispatch desk sees, answering the routine ones in seconds frees a person to chase the genuine exceptions.
The recaptured time goes back into exception-solving and customer calls that need judgement, not into the same lookup repeated.

The hidden cost of status enquiries is not any single lookup — it is that the same "where is my truck?" question, asked all day, buries the few shipments that have genuinely gone wrong behind a queue of routine ones.

Where it works badly

It is confidently wrong when the carrier scan is stale — the reply reads certain while the truck has moved.

Weak when the enquiry has no clean reference to match on, or matches more than one consignment — it should flag, not guess which one.
Multi-leg or interlined freight where the last scan is from a partner carrier is exactly where the milestone is least current.
A revised ETA that is a system estimate, not a carrier-confirmed time, must be shown as an estimate — never stated as a promise.

The honest test

If you cannot say, right now, how old the last scan is and whether the ETA is carrier-confirmed or estimated — this tool makes your wrong answer faster, not safer.

A consignment's last scan can be hours old, or the ETA can be a system estimate the carrier hasn't confirmed. Point the draft at that and it writes a clean, specific delivery time that no longer holds. That is the trap — the reply looks more certain than the data behind it.

What it doesn't do — and shouldn't

It drafts. A person approves. Nothing reaches the customer on its own.

WHAT IT DOES

Surfaces the consignment it matched and the last scan it read

Shows the ETA and whether the SLA window is at risk

Flags every enquiry it could not match cleanly, or where the shipment is delayed or has no ETA

WHAT IT WON’T

Send the reply to the customer

Commit a delivery time the carrier has not confirmed

Decide a service credit, refund, or who carries the delay

A status reply sets a customer's expectation and can commit your business to a delivery promise — and the underlying transport activity sits under Chain of Responsibility duties in the Heavy Vehicle National Law, where pressure to hit a stated time can flow back to the driver. The accountable person stays on the decision because the commitment, and its consequence, lands on them — not the tool.

What your data has to look like

A matchable consignment reference, and carrier scans current enough to trust the ETA.

Typical readiness

across orgs we see, before the first job

A consignment or order reference on the enquiry

Usual weak point

Live carrier scan history, with timestamps

Needs shaping

An ETA that flags confirmed vs estimated

Needs shaping

The consignment record in the TMS

Usually ready

The customer's service-level terms

Usual weak point

The real first job

The weak point is almost always scan currency — last-mile and interline scans arrive late, so the "latest milestone" is often hours behind the truck. Fixing how carrier feeds land in the TMS, and how fresh they are, is usually the real first job — larger and more valuable than the drafting layer on top. Once the milestone data is current and matchable, every reply after that is faster and right by default.

Right fit if…

WISMO is a large, repeating share of your inbound contact

Most enquiries carry a consignment or order reference to match on

Your TMS and carrier feeds expose milestone scans with timestamps

You can tell a carrier-confirmed ETA from a system estimate

Walk away if…

Enquiries are free-text with no reference to match a shipment

Carrier scans land hours late and nobody knows how stale they are

Most contacts are claims, damage, or pricing disputes — not status

You need a tool that will commit a delivery time for you

Open questions

The worried-buyer questions, answered straight

It can draft a wrong ETA — which is exactly why nothing is sent on its say-so. It matches the enquiry to one consignment, reads the latest carrier scan, and shows its working: the reference, the last scan and its timestamp, and whether the ETA is carrier-confirmed or a system estimate. Anything delayed or without an ETA is escalated to a person rather than answered. A dispatcher approves before it sends; the tool surfaces the time, the person stands behind it.

It works from a matchable reference and timestamped carrier scans. If an enquiry has no clean consignment or order reference, or matches more than one shipment, it flags rather than guesses. And a scan that is hours old is the main trap: in Australian freight the last milestone is often a partner-carrier or last-mile scan that arrives late. Getting carrier feeds landing currently in your TMS is usually the first piece of work — and the piece that pays off across every reply after.

No. It removes the routine lookup — the “still on track?” enquiry answered a hundred times a day — so dispatch and customer service spend their time on the shipments that have genuinely gone wrong: the delayed pallet, the failed delivery, the angry trade customer. The reply is still theirs to approve. The capacity it frees goes back into exception-solving and the calls that need a human.

Current enough that the last scan still reflects where the freight is. A milestone scan can be hours old, and an ETA can be a system estimate the carrier hasn’t confirmed — point a reply at either and it states a clean delivery time that no longer holds. The honest test: do you know, today, how old the last scan is and whether the ETA is confirmed or estimated before it goes into a customer’s reply?

Consignment data, delivery addresses and customer contact details are personal information under the Privacy Act, and freight records such as the consignment note and proof of delivery are commercial records you keep for years. Any deployment runs against your own TMS, carrier feeds and helpdesk — not a shared pool — and we scope where the data sits and who can see it as part of the build. The demo here runs entirely on fabricated data; Jordan Mills and Coburg Hardware Supplies are not real.

It reads the freight record to answer a status question — the consignment note, the scan history, the ETA — but it does not generate, sign off, or close the proof of delivery, and it does not decide a claim or service credit. Those are commercial and compliance records that a person owns. The tool drafts the customer reply; the accountable person handles the paperwork and the money.

What it takes to build

3–4 weeks · 4 phases

Reused from template~70%

Bespoke to this skin~30%

stack · Claude · TMS API · carrier feeds · helpdesk · review UI

What it would cost

Fixed scope, fixed price, fixed dates.

Bite-sized first piece

One contained change, low risk

Pilot build

Most builds land here

Embedded support

Scale on proof

Drowning in "where is my order?" enquiries?

The honest place to start is a bite-sized first piece — one contained change, low risk. Tell us where the WISMO load hurts; we'll play it back, scope it, and show you what's possible.

Book a call How we work