boundary
When Does a Delivery Failure Need Escalation Instead of an Automatic Refund?
Escalate when carrier events, the promised delivery date, and your evidence gap do not support a safe customer answer — and when money movement would require a person. ResolveBay maps carrier scans, SLA breaches, and missing proof to an escalation owner. Cross-channel records may disagree and are never silently overwritten. Refunds, cancellations, and stock corrections need an authorized operator. This is the boundary guide: the workspace may plan; it may not claim verified delivery outcomes or live carrier connection.
What this question usually means
The rewrite cluster is: which carrier event last fired, whether the promise date passed, what proof is missing, who escalates to the carrier or 3PL, and what the customer should hear. People also want automatic refunds on late delivery. That crosses into authorized operator territory.
Escalation is for cases where the next action is investigative — trace request, claim filing, re-ship decision — not for cases where a single scan already proves delivery.
Materials or prerequisites
Bring order, inventory, and logistics exports from each channel, including tracking IDs, carrier status codes, and promised delivery windows.
Bring exception definitions and assigned owners for logistics escalation and customer compensation. If tracking comes only from a marketplace feed, note that it may lag the carrier export.
Step 1: List carrier events in time order
Label created, picked up, in transit, out for delivery, delivered, exception, return to sender — using timestamps from the logistics export. Gaps between events are evidence gaps, not silent assumptions.
Step 2: Compare the promised date to the last scan
Write the customer-facing promise and the latest carrier event before that date. If the promise passed with no delivery scan, mark SLA breach for review — not auto-refund.
Step 3: Name the evidence gap and what would close it
Missing proof of delivery, conflicting POD, or warehouse handoff without carrier acceptance each need a different escalation. Write what document or scan would resolve the gap.
Step 4: Assign the escalation owner
Carrier liaison, 3PL account manager, or internal logistics lead — one named person who may open traces or claims. Support may draft customer language; they do not replace the escalation owner on carrier contracts.
Step 5: Separate customer impact from compensation authority
Describe impact: late gift, perishable loss, subscription miss. Compensation — refund, reship, credit — needs an authorized operator. ResolveBay does not execute refunds or cancellations.
Step 6: Document the escalation path in ResolveBay
Review exceptions in the conversation with tracking exports attached. ResolveBay may describe candidate workflows and sample outputs for the escalation timeline. Do not claim production availability, verified outcomes, or guaranteed results.
Verification
Carrier timeline, promise comparison, evidence gap, escalation owner, and customer impact are written. No step claims a refund issued or a carrier claim accepted without operator evidence.
Limits that belong next to escalation
Cross-channel records may disagree and are never silently overwritten. Refunds, cancellations, and stock corrections need an authorized operator. Do not claim live connection to external platforms, including live carrier APIs.
Do not claim production availability, verified outcomes, or guaranteed results. An escalation plan in ResolveBay is review material; closure requires human action and external proof.
What ResolveBay does in this workflow
ResolveBay organizes delivery investigations from exports you supply: event order, SLA comparison, and handoff to the escalation owner. It makes the boundary visible — humans own refunds and cancellations; the workspace does not.
FAQ
Questions this guide is for
Can ResolveBay file a carrier claim?
No. It helps you describe the evidence gap and escalation owner. Filing claims stays with authorized logistics or finance operators outside automated refund paths.
Should we refund when tracking stops updating?
Not automatically. Escalate for trace proof first unless policy and an authorized operator accept immediate compensation with the evidence you have.
What if marketplace tracking shows delivered but the customer disagrees?
Treat it as conflicting evidence. Cross-channel records may disagree and are never silently overwritten. Escalation needs POD or carrier investigation, not a silent refund.
Start in the workspace
Plan this delivery escalation in the workspace
Sign in or create an account. You return to the ResolveBay conversation. Bring logistics exports, name the escalation owner, and keep refunds with authorized operators.