A customer's card declines at checkout. They retry. They retry again. Three of their last six transactions have failed, all on Visa. They wonder if their card is broken.
Three actors. Six stages. Blast radius determines autonomy — not system confidence.
No source-owning team correlates signals across payment, fulfillment, devices, and CS in real time. Shield does. PRFAQ FAQ 6
The AI knows what to do at every scale. The question is whether the stakes require human approval first. PRFAQ FAQ 3
At low blast radius, the customer never knows. Trust is preserved by absence, not by communication. PRFAQ HTD 1
Proactive resolution scores 12 points higher in satisfaction than reactive (82.5% vs 70.1%). The recovery layer earns its build cost. PRFAQ Appendix A
2026 projections from PRFAQ FAQ 1 and Appendix A. Each number is the gap Shield is built to close. Sources in the sidecar; underlying study deck and Appendix D pending PM forward.
PRFAQ stats marked "needs sourcing" until PM forwards underlying study deck and Appendix D. · Sources & methodology
Six stages through time, read left to right. The customer is invisible to the disruption; Shield sees the pattern across domains; a human approves the response inside the 15-minute window; trust holds. The same shape applies at every blast radius — what changes is the weight of Stage 4.
Each row is one dimension of the experience. What the customer does, feels, sees, and what's happening behind the scenes.
Read left to right. Every column is one stage of the journey. The bar at the top of each stage shows where you are in the arc.
Pointing or tabbing to any stage lights up the whole column. Use it to read one moment vertically, top to bottom, across every layer.
A ring opens a popover with evidence. A framed thumbnail enlarges a screenshot, or every screen for that stage.
A customer's card declines at checkout. They retry. They retry again. Three of their last six transactions have failed, all on Visa. They wonder if their card is broken.
Visa and Mastercard auth failures elevated. Amazon Pay unaffected. Root cause candidate: a deployment 47 minutes ago. The pattern was there all along; only Shield could see it.
Outcome attributed. Pattern enters the playbook. Next time auth-failure rates climb on a single network, the system may handle it autonomously.
"My card was just declined. Let me try again."
"Third time. Is my card broken?"
"They caught it before I even called."
"Honestly impressed they caught that so fast."
Phase 0 detection (Perfect Mile delivery POC, Jul-26) is the live reference for cross-domain detection. Payments onboarding targets Sep-26. Stages 4–6 are Phase 2 vision — recovery levers tagged TBC in PRFAQ Appendix E.
What the map implies
The journey shows what's broken about today; these patterns name it. Each one shows up across multiple stages and across multiple incidents. Shield is built to break each one.
Detection trails customer experience by minutes at best, days at worst. The MX deployment failure ran six days before anyone noticed; the IN payment-delay state ran for two years. Customers know first.
Stages 1–2: customer is retrying; CS associate is fielding contacts. Shield (Stage 3) has not yet crossed threshold.
About 55% of customers experiencing a delivery delay never contacted CS. They absorb the disruption silently, shift behavior quietly, and the business never sees the trust loss in real time.
PRFAQ Appendix D: silent-sufferer cohorts spend $0–$16 less in the 30 days following an unresolved incident; lowest spend tier loses $21.50.
When recovery happens, it is one-size-fits-all. The Belgium carrier strike sent identical €5 gift cards to 21,000 customers regardless of order value, urgency, or history. The remediation acknowledges the disruption but doesn't fit the customer.
PRFAQ FAQ 1 Problem 2: the €5 amount was decided on what finance was anecdotally felt to approve, not what would resonate with customers.
Outcomes aren't measured. The same incident shape recurs, and the system can't tell whether last time's response worked. Each event is a fresh investigation, not the next iteration of a learned playbook.
PRFAQ Appendix H: post-recovery CSAT, customer-journey metrics, and downstream-spend impact are all "not measured" today. Repeat-incident rate runs at ~21%.
A real Amazon payment incident, before and after Shield. Same disruption shape; opposite outcomes.
A bad deployment broke checkout in Mexico. 133,000 stuck orders. Six days before anyone noticed. Discovered by chance through ad hoc Slack and email reports. No proactive customer outreach. No coordinated remediation.
Combined with the January 2026 IN incident (178K stuck orders, undetected since 2024): $17M in lost revenue. Trust cost is uncounted — the customers who reached out got reactive resolution; the silent population was never reached at all.
Cross-domain correlation surfaces the deployment-borne auth-failure pattern within minutes. Shield projects blast radius. Recommendation goes to the operator inside the 15-min window. Approved — rollback fires, recovery campaign deploys.
Customers receive proactive notification with credit applied. Stuck transactions reprocess. The same 133K customer base absorbs <30 minutes of disruption with explicit acknowledgment and recovery. Trust cost approaches zero. Phase 2 capability — Concessions Orchestrator dependency unfunded.
Phasing follows PRFAQ FAQ 10. Phase 0 proves the detection layer with one delivery use case. Phase 1 builds the response interface and onboards payments. Phase 2 closes the loop with the customer-facing recovery engine.
Now through Sep-26 · Phase 0
Demonstrate that faster detection delivers measurable value. Perfect Mile delivery POC (Jul-26), recovery experiment (Aug-26), CS incident scorecard (Sep-26). By end of phase: detection approach validated, recovery impact measured, data to justify dedicated investment.
Oct-26 through Mar-27 · Phase 1
Build the production interface incident teams use to handle bridges, resolvers, action items, impact quantification, associate alerts. Onboard payments into the detection layer. First production-grade detection and response capability.
Q1-27 through Q3-27 · Phase 2
Customer-facing recovery engine: personalized outreach, segment-tailored credits, channel-of-choice notification. Closed-loop attribution measures cost per incident and trust impact. The vision in the storyboard becomes operational reality.
Resourcing ask: two two-pizza teams (BI / engineers / scientists) per PRFAQ FAQ 8. Critical dependencies: CS DI ingestion, CS Concessions tooling refresh (proposed Concessions Orchestrator, currently unfunded), CJM outbound rails, AC3 in-line associate context.