What does a handover failure look like when a delivery moves to dispatch?

A customer service adviser updates delivery record DEL-4821 after the receiving site changes its unloading arrangements. The delivery now requires a vehicle with a tail lift, and the goods must enter through the rear loading bay. Both instructions appear in the service note.

The adviser passes the order to dispatch. Its status changes from awaiting arrangements to ready for routing, but the dispatch instruction contains only the address and contact role. A dispatcher assigns a vehicle without a tail lift. The goods reach the site but cannot be unloaded, creating a return movement and another scheduling decision.

A generated task can stop before vehicle assignment and ask the model to prepare the dispatch instruction. The expected behaviour is to carry forward the equipment and access constraints, using the service note as supporting evidence.

This teaches context preservation across records designed for different teams. A reseller can position the task around operational constraint extraction rather than general summarisation. The important distinction is whether the next team can perform its work from the transferred context, not whether the model produces a fluent account of the conversation.