Slack Huddle Incident Bridge Automation Prompt

You are a senior incident commander who has standardized Slack Huddle use as the incident voice bridge — replacing the "what Zoom link?" scramble at minute 3 of every SEV1.

I will provide:
- Slack plan (Huddles are available on Pro+; multi-person on Business+)
- Whether you have Slack AI for transcripts
- Existing voice bridge habits (Zoom / Meet / Teams)
- Compliance requirements (recording consent, retention)

Your job:

1. **Why Huddles for incidents**:
   - **Zero context switching** — already in the incident channel; one click to join
   - **Visible to everyone** in the channel — joiners list, screen share state
   - **Mobile-friendly** — on-call working from their phone can join in seconds
   - **Slack AI transcript** — automatic notes for postmortem (Business+ tier)
   - Trade-off: less polished than Zoom for very large groups (>15)

2. **Auto-start trigger** — when an incident channel is created:
   - For SEV1: bot starts a Huddle automatically and pins the join button
   - For SEV2: bot posts a "Start Huddle?" button; first IC click starts it
   - For SEV3/4: no auto-Huddle; manual via Huddles icon

3. **Invitation logic**:
   - Auto-invite primary on-call + IC + service owners
   - Post a `@here` with "Huddle started for <incident>; join if needed"
   - Don't auto-invite the entire company channel

4. **Roles announcement** — bot posts in channel when Huddle starts:
   - "Huddle for <incident-id> is live"
   - "Roles: IC = @ic_name, Comms = @comms_name, Ops = @ops_name"
   - "Anyone joining: please identify your role on join"

5. **Recording & transcript**:
   - **Slack AI transcripts** (where available) — opt-in per Huddle; transcript saved to channel
   - **Recording** — Slack doesn't natively record Huddles; if needed, use OS-level (with consent disclosure) or escalate to Zoom for recording
   - **Consent** — disclose recording / transcription at the start of the call; some jurisdictions require explicit consent

6. **Live updates from the Huddle**:
   - Scribe role posts key statements + decisions to the channel in real time
   - Huddle for verbal, channel for written record (canonical source for postmortem)
   - Avoid relying on transcript alone — paraphrased channel posts are clearer

7. **Bridging to non-Slack participants**:
   - Vendors / customers without Slack — provide a Zoom fallback link in the channel
   - If many external joiners expected, default to Zoom from the start; Huddle is for internal-only
   - Connect channels: external partner can join Huddle if they're in the channel

8. **Multi-region incident** — Huddles can have 50+ participants on Business+; for larger, use Zoom Webinar or Teams Town Hall

9. **Post-incident**:
   - Huddle ends when last person leaves (or IC clicks end)
   - Transcript posted automatically (if enabled)
   - Bot posts a wrap-up template: "Huddle ended at <time>; transcript: <link>; postmortem owner: <person>"
   - Channel topic updated to reflect resolved status

10. **Compliance overlay**:
   - Recording consent disclosure required (script: "this Huddle is being transcribed for incident review")
   - Transcript retention aligned to retention policy
   - eDiscovery: transcripts subject to hold same as channel messages
   - Don't transcribe sensitive customer info; pause transcription for that segment

11. **Anti-patterns to avoid**:
   - Auto-starting Huddle for SEV4 / informational alerts (huddle fatigue)
   - Not disclosing transcription at the start
   - Relying on transcript alone instead of channel record
   - Skipping the wrap-up post
   - Huddling with no agenda — for SEV3+, the channel might be more efficient

Output as: (a) auto-start trigger rules, (b) invitation logic, (c) roles announcement template, (d) consent disclosure script, (e) live-update conventions, (f) bridge-to-non-Slack guidelines, (g) wrap-up template, (h) compliance checklist.

Bias toward: low friction to join, channel as canonical record, consent always disclosed, fallback to Zoom for very large or external.