Answering ‘where’s my shipment?’ emails automatically, safely
Every forwarding team knows the email. "Any update on the Felixstowe container?" "Has our pallet been delivered?" "When will it clear?" Each one is reasonable. Each one means someone stopping what they're doing, finding the job, checking the carrier's tracking and writing a reply. And the answer is usually already sitting in your system.
That makes status emails a good candidate for automation. It also makes them easy to get wrong, because a status reply is a statement to a customer about their goods. This guide sets out how to answer them automatically without promising things you can't stand behind.
Why status replies need care
Keeping customers informed is part of the job. BIFA's guide to the benefits of using a freight forwarder describes consignment management as including monitoring the consignment through track and trace systems and, where required, monitoring arrival, customs clearance and final delivery.
But what you tell a customer matters. The BIFA Standard Trading Conditions (2025 edition) include a "delivery not guaranteed" clause: unless expressly agreed otherwise in writing, the company has no liability for failing to meet agreed departure or arrival dates, whatever the cause. BIFA's March 2026 member guidance on disruption in the Middle East advised members to avoid offering guarantees or inflexible service commitments during rapidly changing events, and to keep clear records of conversations confirmed by email.
An automated reply that says "it'll be with you Friday" when the data only shows an estimate can create an expectation your terms don't support. So the rule for every automated status message is simple: report what has been recorded, say when and where it came from, and label estimates as estimates. Check your own trading terms with your adviser.
Where the answer usually lives
- Your TMS or forwarding system: job milestones such as booked, collected, departed, arrived and delivered.
- Carrier and line tracking: container, air waybill or consignment events, and the haulier's proof of delivery.
- Customs status: HMRC's Customs Declarations Information API lets authorised users get the status of a declaration by MRN, DUCR, UCR or inventory reference, including when it was accepted and when the goods were released. It's in beta, and it only returns declarations received by CDS in the last 180 days. For goods moving through ports that use the Goods Vehicle Movement Service, GOV.UK explains that a goods movement reference (GMR) shows "complete" for customs-cleared drivers and "Embarked" where a driver has been flagged for an inspection.
- Inboxes and spreadsheets: for overseas agents and smaller hauliers who don't offer tracking.
How a safe automated reply works
1. Find the shipment
The automation reads the email and looks for a reference: your job number, a house or master bill of lading, a container number, an air waybill, a purchase order or the customer's own reference. If it can't match one job confidently, it asks the customer for the reference or passes the email to a person. It doesn't guess.
2. Check who's asking
Shipment details, such as consignee, value and where goods are right now, shouldn't go to anyone who asks. The automation should only reply to contacts already linked to that customer account. An unknown sender goes to a person.
3. Pull the latest status
It checks the job in your TMS and, where connected, the carrier tracking and customs status, noting the time of each event. If two sources disagree, for example the TMS says "departed" but the line's tracking shows the container still at the terminal, that's an exception, not a reply.
4. Draft the reply
The draft states the latest confirmed event and when it was recorded, the next expected step, any estimated date clearly labelled as an estimate with its source, and the name of the person looking after the shipment.
5. Send or queue
At the start, every draft waits for someone in ops to approve it. Later, you might decide that the most routine replies, such as "collected" or "delivered, proof of delivery attached", can go automatically for certain customers. Everything else stays in the review queue.
Illustrative example: a customer emails asking where their container is. The automation matches the container number to an import job, sees that the vessel has arrived, the import declaration has been accepted and the goods haven't yet been released, and drafts: "Your container arrived at Felixstowe on the vessel this morning and the import declaration has been accepted. We're waiting for customs release before we can book delivery. We'll update you as soon as it's released. Sam is looking after this shipment." Sam checks it, approves it and it's logged against the job.
What always goes to a person
Some messages should never be answered automatically. The automation's job is to spot them and put them in front of the right person quickly:
- a delay against the plan, a rolled booking or a missed connection
- a customs hold, an inspection, a query or missing documents
- damage, shortage or loss, and anything that might become a claim
- extra charges, such as storage, demurrage or detention
- conflicting data between sources, or no recent tracking event
- requests to change the delivery address or consignee details
- hazardous, high-value or unusual cargo
- a frustrated or escalating tone, or a sender the system doesn't recognise
BIFA's guidance on insurance and claims handling says forwarders should manage client expectations by keeping them updated on correspondence and timeframes when a claim arises. That's a job for a person who knows the file, not a template.
Proactive updates mean fewer questions
The best way to handle "where's my shipment?" emails is to receive fewer of them. When a milestone is recorded, such as collected, departed, arrived, cleared or delivered, the automation can draft a short update to the customer before they ask. Larger accounts might prefer a single daily summary of all open shipments instead of an email per event. Agree the format with each customer and keep exceptions out of the automatic path.
Customs: report the status, don't interpret it
An automation can tell a customer that a declaration has been accepted or that goods have been released, because that's a recorded fact. Why goods are held, what duty is due and which commodity code applies are questions for your customs team. Our guide to freight quote request automation covers why classification and declarations should stay with qualified people.
Which systems can it connect to?
We work with tools that have an API or an export. CargoWise offers an integration module, eAdaptor, to licensed customers, and Descartes runs an API portal with approved access. What carriers, lines and hauliers offer varies a lot: some provide tracking APIs, some only a web page or an email. HMRC's customs API needs authorisation and is still in beta. It's worth listing where your status data actually comes from before planning anything ambitious, and if a source has no reliable integration route, we'd say so.
Data and access
Status replies need read access to job data, not the ability to change it. Give the automation only the access each step needs, keep a copy of every message on the job file, and make sure the logs show what was sent, to whom and based on which data. That also helps with the record-keeping BIFA recommends.
Where to start
Choose one customer account or one mode with a steady flow of status questions. Turn on matching and drafted replies only, with ops checking every draft for the first few weeks and noting what it gets wrong. Add proactive milestone updates next. Only then consider sending the simplest replies automatically. Measure your own before-and-after rather than relying on anyone else's numbers.
Questions we often hear
Will it send replies without anyone checking?
Only if you decide it should, and only for the types of message you choose. We start with every reply drafted for a person to approve.
What if the tracking data is wrong or out of date?
Each reply says where the status came from and when it was recorded. If sources disagree, or there's been no tracking event for longer than you'd expect, the email goes to a person instead of getting an automatic reply.
Can it give customers delivery dates?
It can pass on an estimated date from your system or the carrier, labelled as an estimate. It shouldn't promise or guarantee one. Check your own trading terms.
Does this work alongside quote automation?
Yes. Many of the same pieces, such as reading emails, matching to jobs and drafting replies for approval, also apply to quote requests.
The honest summary
Most "where's my shipment?" emails ask for facts that are already in your TMS, your carriers' tracking or the customs status. Matching the email to the job, pulling the latest status and drafting a clear, sourced reply is a sensible thing to automate. Delays, holds, damage, charges and anything unusual stay with your team, and no automated message should promise what your terms don't.
To see how this fits with the rest of a forwarding operation, read AI automation for freight forwarders and logistics teams, or email luke.sewell@melonjuice.ai.
This article is general information, not legal, customs or insurance advice. Check your trading conditions and current GOV.UK guidance for your obligations.
Email us or read how we work with freight forwarders and logistics teams, see how a project runs, or use the contact form
More questions? Read the FAQ.