Suspension Incident SOP
Handle account suspensions with a calm, evidence-based playbook
Account suspensions can be existential for businesses. This recipe creates an incident SOP: information capture, likely causes, remediation steps, communications, and an escalation path. It also generates a "postmortem" template to prevent repeats.
INGREDIENTS
PROMPT
Create a suspension incident response plan. Output: - Timeline + evidence capture checklist - Likely cause shortlist (ranked) - Remediation steps (in order) - Appeal narrative (factual, policy-aligned) - Business continuity options for the next 7 days - Postmortem template (to prevent recurrence) Inputs: - Suspension notice (paste exact text): - Date/time it happened: - Any changes in last 14 days: - Business category: - Revenue impact urgency (daily revenue at risk):
How It Works
This SOP treats suspensions like an operations incident: stabilize, diagnose, remediate, document.
Triggers
- Ad account is suspended or appeals stall
- Multiple accounts in an MCC/portfolio are affected
- You need to protect business continuity
Inputs
- Suspension notice text + policy category
- Account history (recent changes, billing updates, domain/URL changes)
- Business verification status and legal details (high-level)
Outputs
- Incident log (timeline, actions, evidence)
- Remediation checklist by policy type
- Stakeholder comms template (client/exec)
Actions / Steps
- Freeze changes; capture evidence (screenshots, timestamps, notices).
- Triage likely triggers: URL/domain changes, destination issues, policy-sensitive claims.
- Remediate systematically; submit appeal only with documentation.
- Create a continuity plan: alternate channels, temporary budgets, lead capture contingencies.
Parameters
- Severity (full suspension vs limited serving)
- Escalation threshold (time without response)
- Continuity tactics (approved list)