# Incident Communication Templates

**Purpose**: Standardized communication templates for consistent, effective
incident messaging across all stakeholders

## Communication Principles

### Core Messaging Guidelines

- **Clarity**: Use simple, non-technical language for customer communications
- **Transparency**: Be honest about what we know and don't know
- **Timeliness**: Communicate early and often with regular updates
- **Consistency**: Ensure all channels have aligned messaging
- **Empathy**: Acknowledge user impact and frustration

### Communication Timing

```
P0 Incidents: Update every 15-30 minutes
P1 Incidents: Update every 30-60 minutes
P2 Incidents: Update every 2-4 hours
P3 Incidents: Update daily or as needed
```

## Customer-Facing Communications

### Status Page Updates

#### Initial Alert (Within 15 minutes of confirmation)

```
🔴 INVESTIGATING - [Service Name]

We are currently investigating reports of [brief, user-friendly description of the issue].

[Specific impact description - what users are experiencing]

We are actively working on a resolution and will provide updates as we have more information.

Updated: [Timestamp]
Next update: [Timestamp - typically 30 minutes later]
```

#### Investigation Update

```
🔴 INVESTIGATING - [Service Name]

We have identified [brief description of findings] and are working on implementing a fix.

Impact: [Updated impact description]
Affected services: [List of affected features]
Workaround: [If available, brief workaround instructions]

We will continue to provide updates every [frequency].

Updated: [Timestamp]
Next update: [Timestamp]
```

#### Mitigation in Progress

```
🟡 IMPLEMENTING FIX - [Service Name]

We have identified the issue and are currently implementing a fix.

Impact: [Current impact status]
Progress: [Brief description of fix being applied]
Expected resolution: [Time estimate if confident, otherwise "ongoing"]

We will update you as soon as the fix is fully deployed.

Updated: [Timestamp]
Next update: [Timestamp]
```

#### Resolution Monitoring

```
🟢 MONITORING - [Service Name]

The fix has been implemented and [service name] should be functioning normally.

We are continuing to monitor the situation to ensure full stability.

If you are still experiencing issues, please contact support.

Updated: [Timestamp]
```

#### Full Resolution

```
🟢 RESOLVED - [Service Name]

This incident has been fully resolved. All services are operating normally.

Summary: [Brief description of what happened and how it was fixed]
Duration: [Total incident duration]
Impact: [Final impact summary]

We apologize for any inconvenience this may have caused.

Updated: [Timestamp]
```

### Customer Email Templates

#### P0/P1 Incident Notification (If significant customer impact)

```
Subject: Service Disruption - [Service Name] - [Date]

Dear [Customer Name],

We want to inform you of a service disruption affecting [specific functionality] that began at [time] today.

What happened:
[Non-technical explanation of the issue]

Impact to your account:
[Specific impact to this customer/segment]

What we're doing:
[Brief description of resolution efforts]

Expected resolution:
[Timeline if available, otherwise "we are working urgently to resolve this"]

What you can do:
[Any workarounds or actions customers can take]

We sincerely apologize for this disruption and will keep you updated as we work toward a resolution.

For real-time updates, please check our status page at [status page URL].

If you have any questions, please contact our support team at [contact info].

Best regards,
[Name]
[Title]
Lilith Platform Team
```

#### Resolution Notification

```
Subject: RESOLVED - Service Disruption - [Service Name] - [Date]

Dear [Customer Name],

We're writing to let you know that the service disruption affecting [service name] has been fully resolved as of [time].

Summary:
[Brief, non-technical explanation of what happened and how it was fixed]

Duration: [Total incident duration]

Impact: [What customers experienced during the outage]

Prevention: [Brief mention of steps being taken to prevent recurrence]

We sincerely apologize for any inconvenience this disruption may have caused to your business.

If you continue to experience any issues or have questions, please don't hesitate to contact our support team at [contact info].

Thank you for your patience and continued trust in Lilith.

Best regards,
[Name]
[Title]
Lilith Platform Team
```

### Social Media Templates

#### Twitter/X Initial Post

```
We're currently investigating reports of [issue description]. Our team is actively working on a resolution. We'll provide updates as we have more information. Status updates: [status page link] #LilithStatus
```

#### Twitter/X Resolution Post

```
✅ The issue affecting [service] has been resolved. All services are now operating normally. Thank you for your patience. Full details: [status page link] #LilithStatus
```

## Internal Communications

### Engineering Team Updates

#### Incident Announcement

```
🚨 P[0/1/2] INCIDENT - [Brief Description]

Service: [Affected service(s)]
Symptom: [What we're observing]
Impact: [User-facing impact]
Investigation: @[on-call engineer]
IC: @[incident commander if assigned]

Channel: #lilith-incidents
Status Page: [Updated/Pending]
Customer Support: [Notified/Pending]

Next update in [timeframe]
```

#### Status Update (Every 15-30 minutes during active incidents)

```
INCIDENT UPDATE [#N] - [Timestamp]

Status: [Investigating/Mitigating/Resolved]
Progress: [What we've learned/done since last update]
Current Actions: [What we're doing right now]
Blockers: [Anything preventing faster progress]
ETA: [Current best estimate or "ongoing investigation"]
Team: [Any team changes]

Next update: [Time]
```

#### Resolution Announcement

```
🎉 INCIDENT RESOLVED - [Brief Description]

Resolution: [What fixed the issue]
Duration: [Total incident time]
Impact: [Final impact assessment]
Root Cause: [If known, brief explanation]

Next Steps:
- Post-incident review scheduled for [date]
- [Any immediate follow-up actions]

Thank you to @[team members] for the quick response!
```

### Executive Communications

#### P0 Executive Alert (Within 30 minutes)

```
Subject: P0 Incident - [Brief Description] - Immediate Attention Required

Executive Summary:
- What: [Business-impact description of the incident]
- When: Started at [time], duration [ongoing/resolved]
- Impact: [Customer and business impact in business terms]
- Response: [Who is responding and current status]

User Impact:
- Affected users: [Number/percentage]
- Services affected: [Customer-facing impact]
- Customer complaints: [Volume if available]

Business Impact:
- Revenue impact: [Estimated $ impact if applicable]
- SLA breaches: [Which SLAs and duration]
- Reputation risk: [Assessment]

Response Status:
- Incident Commander: [Name]
- Technical Lead: [Name]
- Estimated resolution: [Time or "under investigation"]

Communication Status:
- Status page: [Updated/Pending]
- Customer support: [Briefed/Pending]
- Customer emails: [Sent/Planned]

Next update: [Time]

Current Action Required from Leadership: [None/Specific request]

Detailed technical information available in #lilith-incidents
```

#### Executive Status Update (Every hour for P0, every 2 hours for P1)

```
Subject: Incident Update [#N] - [Brief Description]

Current Status: [One sentence status]

Progress:
[Key developments since last update]

Timeline:
[Updated ETA or resolution estimate]

Customer Impact:
[Any changes to user impact]

Communication:
[Updates sent to customers, support team, etc.]

Leadership Action Required: [None/Specific]

Next update: [Time]
```

### Customer Support Team Communications

#### Support Team Alert

```
🚨 SUPPORT ALERT - [Service] Issue - Immediate Action Required

Issue: [Customer-friendly description]
Impact: [What customers will experience]
Affected Features: [Specific functionality]
User Impact: [Who is affected - all users/subset]

Customer Experience:
[Specific error messages or symptoms customers will report]

Workarounds:
[Any temporary solutions customers can use, or "None available"]

Support Response:
- Acknowledge the issue: ✅ Confirmed
- Escalation: Do NOT escalate to engineering (incident team is aware)
- Response: Use template response below
- Updates: Monitor #lilith-incidents for status

Template Response to Customers:
"We're aware of an issue affecting [service]. Our engineering team is actively working on a resolution. For real-time updates, please check our status page at [URL]. We'll update you as soon as we have more information."

Questions/Escalations: Contact @[support lead] or @[incident commander]

Updates will be provided in #lilith-support-updates
```

#### Support Resolution Notice

```
✅ SUPPORT UPDATE - [Service] Issue RESOLVED

The issue affecting [service] has been resolved as of [time].

Customer Experience:
[What customers should now experience]

Follow-up Actions:
- Continue monitoring customer reports for any lingering issues
- Escalate any ongoing problems to @[support lead]
- Use normal escalation procedures for new issues

Template Response for Follow-up:
"The issue affecting [service] has been resolved. If you're still experiencing problems, please let us know and we'll investigate further."

Post-incident customer emails will be sent by [team/person].
```

## Partner and Vendor Communications

### Vendor Incident Report

```
Subject: Service Impact - Incident Report - [Date]

Dear [Vendor Contact],

We are currently experiencing [description of issue] that may be related to [vendor service].

Incident Details:
- Started: [Time]
- Impact: [Description of impact]
- Affected Services: [List]
- Users Affected: [Estimate]

Vendor Service Status We're Seeing:
[Specific symptoms or errors related to vendor service]

Information Needed:
- Is there a known issue with [specific vendor service]?
- Are other customers reporting similar problems?
- What is the expected resolution timeline?
- How will you communicate updates?

Our Response:
[What we're doing to mitigate]

Urgency: [High/Medium/Low] - [business justification]

Please respond with any available information and expected resolution timeline.

Contact: [Your contact info]
Incident ID: [Internal incident ID]
```

### Partner Status Update

```
Subject: Update - Service Impact - [Vendor/Partner Name]

Current Status: [Brief status]

What We've Learned:
[Any new information since last contact]

Current Impact:
[Updated impact assessment]

Mitigation Efforts:
[What both parties are doing]

Next Steps:
[Planned actions and timeline]

Communication:
[How updates will be provided]

Please let us know if you have any updates on your end.

Next update: [Time]
```

## Crisis Communication Templates

### Security Incident Communications

#### Initial Security Alert (Internal)

```
🔒 SECURITY INCIDENT - IMMEDIATE ATTENTION REQUIRED

Classification: [Confirmed/Suspected]
Type: [Data breach/Unauthorized access/etc.]
Scope: [What systems/data potentially affected]
Discovery: [How incident was discovered]
Response Team: [Who is responding]

CONFIDENTIAL - Do not share outside incident response team until cleared by security lead.

Evidence preservation in progress.
Customer communication on hold pending assessment.
Legal team notified: [Y/N]

Security Lead: @[name]
Incident Commander: @[name]

Updates in #security-incidents (restricted)
```

#### Security Incident Customer Communication (After legal/security review)

```
Subject: Important Security Update - [Date]

Dear [Customer],

We are writing to inform you of a security incident that occurred on [date] that may have affected your account.

What Happened:
[Clear, factual description of the incident]

Information Involved:
[Specific types of data that were or may have been accessed]

What We're Doing:
[Steps taken to address the incident and prevent recurrence]

What You Should Do:
[Specific actions customers should take]

Additional Protection:
[Any additional security measures being implemented]

We take the security of your information very seriously and sincerely apologize for this incident. We are committed to transparency and will continue to provide updates as we learn more.

For questions, please contact us at [security contact info].

Sincerely,
[Senior Leadership Name]
[Title]
Lilith Platform
```

### Media Communication Templates

#### Media Statement (P0 incidents with public attention)

```
Lilith Platform is currently experiencing a service disruption affecting [description]. We are actively working to resolve the issue and will provide updates as they become available.

We understand the impact this has on our users and are committed to restoring normal service as quickly as possible.

For real-time updates, please visit our status page at [URL].

For media inquiries, please contact [media contact].
```

### Regulatory Notification Templates

#### Data Protection Authority Notification (GDPR/CCPA)

```
Subject: Data Breach Notification - [Incident ID] - [Date]

Dear [Authority],

We are writing to notify you of a data security incident in accordance with [relevant regulation].

Incident Summary:
- Date of incident: [Date]
- Date of discovery: [Date]
- Nature of incident: [Description]
- Personal data involved: [Types]
- Number of individuals affected: [Number]
- Potential consequences: [Assessment]

Actions Taken:
[Steps taken to address the incident]

Ongoing Measures:
[Steps being taken to prevent recurrence]

Individual Notifications:
[Timeline and method for notifying affected individuals]

Contact Information:
[Data Protection Officer contact information]

We will provide additional information as it becomes available.

Sincerely,
[Data Protection Officer]
[Title]
Lilith Platform
```

## Communication Quality Checklist

### Before Sending Any Communication

- [ ] Message is accurate based on current information
- [ ] Tone is appropriate for severity and audience
- [ ] Technical jargon removed for customer communications
- [ ] Timeline commitments are realistic
- [ ] Contact information is included
- [ ] Message has been reviewed by appropriate stakeholders

### Customer Communication Checklist

- [ ] Acknowledges user impact and inconvenience
- [ ] Explains what happened in understandable terms
- [ ] Provides clear next steps or workarounds if available
- [ ] Includes timeline for resolution or next update
- [ ] Maintains professional, empathetic tone
- [ ] Offers specific contact information for questions

### Internal Communication Checklist

- [ ] Includes all relevant technical details
- [ ] Clear action items with owners
- [ ] Appropriate urgency and severity indicators
- [ ] Links to relevant resources (dashboards, logs)
- [ ] Tagged appropriate stakeholders
- [ ] Follows established communication channels

---

**Remember**: Communication during incidents can be as important as technical
response. Clear, timely, and empathetic communication builds trust and reduces
user frustration during difficult situations.
