Third-Party and Vendor Coordination During a Major Incident Prompt
Run the playbook for incidents caused by or dependent on an external vendor (cloud provider, CDN, payment processor, SaaS dependency) — escalation, status correlation, customer comms, and parallel mitigation while you wait on someone else's fix.
- Target user
- Incident commanders and on-call engineers handling vendor-caused outages
- Difficulty
- Intermediate
- Tools
- Claude, ChatGPT
The prompt
You are an incident commander who has run major incidents where the root cause sat inside someone else's infrastructure — and learned that "it's the vendor's fault" is not a resolution. Help me coordinate a vendor-involved incident. I will provide: - The failing/suspect vendor and the dependency it provides - What we're observing vs what their status page says - Our support tier / contract / escalation contacts - Customer-facing impact Your job: 1. **Confirm it's actually the vendor** — before blaming them, list the evidence that distinguishes a vendor outage from our misuse of it (their status page, peer reports, our error signatures, recent changes on our side). Do not assume; many "vendor outages" are self-inflicted. 2. **Open the right escalation, immediately** — map our support tier to the fastest path (severity-1 ticket, dedicated TAM, phone bridge, account exec). Draft the escalation message: impact, scope, what we need, business criticality. 3. **Run parallel mitigation, don't just wait** — what can we do on our side regardless of their ETA: failover to a secondary provider, serve degraded/cached, circuit-break the dependency, queue and replay. Owning your own recovery is the whole game. 4. **Correlate their status with reality** — vendor status pages lag and undercount. Track our own signals as the source of truth and note when their public status contradicts what we see. 5. **Customer comms without over-promising** — communicate impact honestly while attributing carefully; you can say "a third-party dependency" without naming-and-shaming, and never relay a vendor ETA you don't trust. 6. **Capture for the postmortem** — document the dependency, the lack of fallback (if any), and the action item to reduce single-vendor risk. Output: (a) a vendor-vs-us diagnostic checklist, (b) a ready-to-send escalation message, (c) a parallel-mitigation options table with tradeoffs, (d) an internal+external comms snippet, (e) the resilience action item. Bias toward: owning your recovery, evidence before blame, and never repeating an unverified vendor ETA to customers.
Run this prompt with AI
Test it, get an AI-improved version, or compare models — live in the Prompt Workspace. No copy-paste.
Related prompts
-
Swarm vs Escalate Decision Guide Prompt
Give the first responder a fast rule for the early-incident fork: keep working it solo, pull in a swarm of experts, or escalate to a formal incident with a commander — so pages neither languish under one overwhelmed engineer nor over-mobilize the whole org for a blip.
-
Firing Alert Severity & Escalation Decision Prompt
Given a firing alert and current impact signals, decide an appropriate severity level and whether to escalate or page additional responders, with explicit reasoning against your severity rubric — leaving the final call to a human.
-
Incident Conference Bridge Noise Control Prompt
Restore signal on a chaotic major-incident voice or video bridge where too many people are talking over each other and decisions are being lost
-
Incident Deputy Commander Load-Sharing Prompt
Split incident command duties across a deputy, scribe, and comms lead when a single commander is overloaded on a large or fast-moving incident
More Incident Response prompts & error guides
Browse every Incident Response prompt and troubleshooting guide in one place.
Reading prompts? Get all 500 in one free PDF
500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.
- 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
- Instant PDF download — yours free, forever
- Plus one practical AI-workflow email a week (no spam)
Single opt-in · unsubscribe anytime · no spam.