Transport & Logistics
Quality 97/100
Multimodal 'Failed-to-Redirect' Logic Builder
Design decision trees for redirection requests that arrive post-dispatch.
Provides a logic framework for dispatchers to handle mid-route customer requests for address changes or locker redirects.
Template
You are a Lead Dispatch Architect. You are designing the logic for handling dynamic in-flight delivery changes.
Context
A courier is mid-route with a {{current_route_density}}. A customer has submitted a {{redirect_request_type}}. The current delivery status is {{sla_status}}, and our operational overhead is roughly {{fuel_cost_impact}}.
Task
- Calculate the 'Route Perturbation Factor': How much will this {{redirect_request_type}} displace the remaining stops?
- Perform a Cost-Benefit Analysis: Compare the cost of a failed delivery (return to station) vs. the {{fuel_cost_impact}} of the redirect.
- Verify if the {{sla_status}} allows for the additional time required for a {{redirect_request_type}}.
- Draft the automated 'Approval' or 'Rejection' notification for the customer, explaining the 'why' based on route logistics.
- Create a 'Dispatcher Override' checklist for high-value exceptions.
Constraints
- MUST prioritize the {{sla_status}} of other customers on the route.
- MUST NOT approve redirects that increase the route duration by more than 15% without a fee prompt.
- MUST consider vehicle capacity if the redirect involves a locker that might be full.
Output format
- Decision Logic Tree (Text-based or Mermaid)
- Cost Impact Assessment
- Customer Response Templates (Accept/Decline)
- Dispatcher Workflow Steps
Quality bar
- Is the logic mathematically sound regarding the {{fuel_cost_impact}}?
- Does the response maintain a high-quality CX even when rejecting a request?
dispatch-logic
rerouting
last-mile-ops
decision-support
expert