Draft a Customer-Facing Security Breach Notification with Actionable Steps

Create a transparent and compliant security breach notification email that informs customers and provides clear protective actions.

๐Ÿ“ The Prompt

You are the head of customer communications at [COMPANY_NAME]. A security incident has occurred and you must draft a clear, transparent, and legally responsible notification to affected customers. Incident Details: - Type of Breach: [BREACH_TYPE] (e.g., unauthorized data access, credential exposure, payment data compromise) - Date Discovered: [DISCOVERY_DATE] - Date of Actual Breach: [BREACH_DATE] - Data Potentially Affected: [DATA_TYPES] (e.g., email addresses, passwords, payment information) - Number of Affected Customers: [AFFECTED_COUNT] - Regulatory Framework: [REGULATION] (e.g., GDPR, CCPA, HIPAA) Structure the notification as follows: 1. **Subject Line** โ€” Write 2-3 subject line options that are urgent but not alarmist. 2. **What Happened** โ€” Clearly describe the incident in plain, non-technical language. Be honest about what is known and unknown. 3. **What Information Was Involved** โ€” Specify exactly what data types may have been compromised. 4. **What We Are Doing** โ€” Outline the immediate actions [COMPANY_NAME] has taken, including investigation steps, law enforcement engagement, and infrastructure hardening. 5. **What You Can Do** โ€” Provide a numbered list of 4-6 specific actions customers should take immediately (e.g., change passwords, enable 2FA, monitor accounts). 6. **Dedicated Support Resources** โ€” Include a dedicated support email, phone number [SUPPORT_PHONE], and FAQ page link [FAQ_URL]. 7. **Accountability Statement** โ€” Express genuine accountability without making legally problematic admissions. Tone: Transparent, empathetic, urgent, and authoritative. Avoid minimizing language or corporate jargon. Comply with [REGULATION] disclosure requirements.

๐Ÿ’ก Tips for Better Results

Have your legal team review the final notification before sending to ensure regulatory compliance. Lead with facts rather than apologies to build trust. Always provide a dedicated communication channel separate from normal support queues to handle breach-related inquiries.

๐ŸŽฏ Use Cases

Security teams, compliance officers, and customer communication leads use this when a data breach requires timely and transparent customer notification under regulatory obligations.

๐Ÿ”— Related Prompts

๐Ÿค Customer Support beginner

Customer Support Response Templates

Get 8 professional customer support templates covering complaints, refunds, bugs, and more.

๐Ÿค Customer Support beginner

Create a Comprehensive FAQ Document for Customer Support

Generate a structured, brand-aligned FAQ document with categorized questions and clear answers for your customer support team.

๐Ÿค Customer Support intermediate

Write a Professional Knowledge Base Article for Customer Self-Service

Craft a structured, searchable knowledge base article with step-by-step instructions to empower customer self-service.

๐Ÿค Customer Support advanced

Build a Step-by-Step Troubleshooting Guide for Customer Issues

Create a detailed troubleshooting guide with diagnostic decision trees and escalation paths to resolve customer issues faster.

๐Ÿค Customer Support beginner

Write a Warm Customer Onboarding Welcome Email

Generate a professional onboarding welcome email that guides new customers through first steps and builds brand loyalty.

๐Ÿค Customer Support intermediate

Create a Persuasive Subscription Renewal Reminder Email

Craft a compelling subscription renewal reminder email that highlights customer value and reduces churn effectively.