What’s inside: routing · monitoring
The question this file answersWhat happens when a real replan is sitting in the same inbox as the routine delay notices?
Fits: logistics teams whose inbox answers status and booking mail by hand.
Pattern rather than measurement — the playbook counts delay notices inside “continuous” status traffic, with no separate number. Carrier delay mails land beside customers’ “where is my shipment?”. An agent reads each, writes the same paragraph to the customer, and sometimes finds one that needed a new truck hours ago.
Typical, from the industry playbook — not a client's day.
Mid-morning, the planner’s queue holds the shipments that actually need a new route, each with the carrier’s message and the customer’s deadline attached; the routine ETA changes have already updated tracking and told the customer. You can see how many notices needed a typed reply this week and which carriers cause them.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
notify, replan, claim — sorted before a person reads; same build as our shipment-status file; no published figure for inbound delay notices
Before: delay notices sit in the same inbox as “where is my box?”. After: routine ETA changes update tracking and tell the customer; replans and claims reach a named person with the message attached. We carry no percentage; the Capgemini figure stays with the parent.
No published benchmark covers the sorting of inbound carrier delay notices. Capgemini “Logistics 4.0” (2023) measured customer inquiries answered without escalation, not inbound carrier mail; that range stays on the parent file. Not an on-time claim.
Your TMS and tracking portal stay — SAP TM, project44, CargoWise or your own. The same sorting-and-replying build as our shipment-status file, turned towards inbound carrier mail:
Network replans. Customer penalties. Anything in the message that is not a timestamp.
Not an on-time claim.
Carriers write delays in free text — “slight delay” from one is a day from another — so the sort is a suggestion the planner sees, and a wrong sort is a slower reply, not a lost shipment, because replans always wait for a person. If your customer commitments and penalties are not on the shipment record, the build cannot tell a cheap delay from an expensive one.
The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →
Scoped in the audit — the playbook has no estimate for this exact desk.
That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.
Not a named Aperanda client. Process file · Logistics.
Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.