"Where's My Shipment?" — Answering Status Requests Automatically

Why "where's my load?" eats up whole mornings

It plays out the same way in almost every forwarding company: the phone rings, and the inbox fills with emails titled "status shipment 4711?" or "ETA today?". The answer is usually already sitting in the system — in the TMS, in telematics, in the carrier's tracking. Even so, a dispatcher or customer service employee has to read the request, look up the shipment, check the status, and type a reply. Three to five minutes per request, thirty to fifty times a day — that quickly adds up to two to four hours that don't go into dispatching, sales, or handling real problems.

On top come the typical side effects:

• Status requests interrupt dispatch right in the middle of route planning — every interruption costs concentration
• Outside office hours, requests just sit there, even though recipients and shippers also want to know in the evening whether the goods are coming
• International customers ask in English, Polish or French — the answer takes correspondingly longer
• With delays, customers call multiple times because nobody informed them proactively

The core of the problem: people manually answer questions whose answer already exists digitally.

How a shipment-status agent works

An AI agent is a digital employee that takes over this process completely — connected to your existing systems, without a software change.

Step 1: Recognise and match the request

The agent reads incoming emails, web form entries or portal requests and recognises that it's a status request. It extracts shipment number, reference, loading point or customer number — even if the customer only writes "the delivery for hall 3 from last week." If the reference is missing, the agent asks specifically instead of guessing.

Step 2: Pull the status from real data

The answer doesn't come from a text template but from your systems: TMS, telematics, carrier tracking portals, or a simple status export. The agent checks current position, planned delivery and any deviations.

Step 3: Reply — in the language of the request

The agent formulates a clean reply with status, expected delivery and the agreed information — in German, English, or the customer's language. You define in advance what may be shared with whom: end customers get different details than shippers or partners.

Step 4: Hand special cases to humans

Complaints, damage reports or sensitive delays are not answered by the agent on its own initiative. It recognises such cases, prepares a summary with all shipment data, and hands it to your team — with a draft reply for approval. Every step is logged, so it's always traceable who received which information and when.

Step 5: Proactive instead of reactive

The master discipline: for foreseeable delays, the agent informs affected customers on its own initiative — before they call. A large share of status requests never even arise if the information arrives in time.

Which systems get connected

HVNH AI's agents work with what's already in your forwarding company: legacy TMS landscapes, telematics portals, email inboxes, spreadsheets and customer portals. Where there's no modern interface, access is set up through exports, files, or operating the existing user interface. Your familiar programs stay in use — that's our core promise.

On data protection: operation runs on German servers or entirely within your own environment, with a data processing agreement and complete logging. Shipment and customer data doesn't leave the defined framework.

What you can realistically expect

A typical result after implementation: the majority of standard status requests get answered without human involvement — in minutes instead of hours, including nights and weekends. For dispatch, depending on request volume, that means several fewer hours of interruption per day. Two effects follow:

• Calmer dispatch: whoever isn't pulled out of route planning every ten minutes plans better — and makes fewer mistakes.
• A more professional image: customers get fast, consistent, multilingual answers. Shippers with their own service commitments notice this immediately.

Important for expectations: the agent doesn't replace your customer service. It takes over the routine so your team has capacity for the cases that genuinely need experience — complaints, special requests, difficult conversations.

An everyday example

Friday, 5:50 p.m.: a recipient writes in English asking whether Monday's early delivery is confirmed — their production line depends on it. In the past, the email would have sat until Monday morning. Now the agent recognises the shipment from the reference, checks telematics and the route plan, sees the planned delivery at 7:30 a.m., and replies within a few minutes with status and time window. On Monday at 6:15 a.m., telematics reports a thirty-minute delay — the agent proactively informs the recipient. The call to the dispatcher that would otherwise have come at 7:35 a.m. never happens.

Common objections from the field

"Our customers want a human on the phone." For difficult cases: absolutely, yes. But nobody wants to resolve the standard "where's my load?" request over the phone — customers want the answer, fast and reliable. That's exactly what the agent delivers, and your team is available again for the real conversations.

"Our data is too incomplete for this." The agent can only report what your systems provide — but that's exactly the same limitation your employees face today. In practice, implementation often reveals where status data is lagging and makes the gaps visible. You start with the routes where the data is solid.

"What if the agent commits to something wrong?" The agent only passes on information that's in the system, and only to recipients you've approved. Binding commitments, goodwill or contractual matters stay with your team — with an approval step.

Self-check: is this worth it for your forwarding company?

• Your team answers more than 15 status requests a day
• Status requests regularly arrive outside office hours
• International customers ask in several languages
• With delays, customers call before you inform them
• Your dispatch complains about constant interruptions

If three or more of these apply, the shipment-status agent is very likely the process with the fastest noticeable benefit.

The next step

We'll work out whether your status requests can be automated in a free intro call: we'll look at which channels the requests come through, where the status data sits, and how much volume adds up. A pilot follows within a few weeks. For more use cases, see our industry page AI in logistics.