What’s inside: routing · step-by-step flow
The question this file answersWhen three parties e-mail about the same dock window, who decides — and how long does that take?
Fits: logistics teams whose inbox answers status and booking mail by hand.
Typical pattern, not a measured desk — dock mail sits inside the playbook’s “continuous” status traffic. Carriers ask for a window, the warehouse asks to move it, a customer asks whether it still stands, all in one inbox. Someone reads them in order of arrival, whatever the yard needs.
Wednesday, mid-morning: the planner’s queue is the moves and the clashes, each with the calendar entry attached, while the plain confirmations have gone back from the calendar record. You can see how many slots were confirmed without a person and which carriers keep asking to move.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
confirmations from the calendar, moves and clashes to the planner — same build as our shipment-status file; no published figure for dock mail
Before: carriers, warehouses and customers write about the same window into one inbox. After: plain confirmations go back from the calendar; moves and clashes reach the yard planner with the booking attached. Percentage: none of our own — see the parent file for the sourced range.
No published benchmark covers dock-booking correspondence. The Capgemini (2023) figure for automated status replies concerns customer questions and is quoted on the parent file; dock mail does not inherit it. Not a turnaround claim.
Your dock calendar stays — in the WMS, the yard tool or the shared calendar you actually use. It shares the sorting-and-replying build of our shipment-status file, pointed at dock mail:
Yard gridlock. A broken dock door. Priority cargo. Anything that is not a calendar entry.
Not a turnaround claim.
A calendar that is not the truth — slots blocked by habit, doors down for repair that nobody entered — confirms windows you cannot serve, so the first week is spent making the calendar honest. Messages that mix a confirmation with a complaint are sorted to a person by design; that is slower for the sender and correct.
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.