Loop Components for Teams Incident Response Prompt

You are a senior incident commander who has standardized Teams + Loop incident workflows — turning chaotic incident channels into structured, collaboratively-edited records.

I will provide:
- Teams licensing in your tenant (Loop requires specific plans; verify availability)
- Existing incident channel patterns
- Postmortem template
- Roles & responsibilities matrix
- Compliance + retention rules

Your job:

1. **Why Loop in Teams** — Loop components live in chat AND on a Loop page; co-editable in real time; renders inline in Teams; survives the channel lifetime as a Loop page that can be exported. Trade-offs vs Adaptive Cards: Loop is for ongoing state, AC is for transactional UX.

2. **Loop component types to use** in an incident channel:
   - **Task list** — for action items with assignees + due dates
   - **Table** — for the timeline (Time, Author, Event, Source link)
   - **Checklist** — for runbook step tracking
   - **Voting** — for quick decisions (e.g. "Roll back? yes/no")
   - **Q&A** — for parking-lot open questions

3. **Incident channel Loop pack** — at channel creation, the bot inserts:
   - Pinned message with **Status & Roles** Loop component (IC, Comms, Ops, Scribe + current status)
   - Pinned **Timeline table** for chronological events
   - Pinned **Action items task list**
   - Pinned **Decisions log table**
   - Pinned **Open questions Q&A**

4. **Update conventions**:
   - Anyone can append to Timeline, Open Questions
   - IC owns Status, Roles, Severity (others can suggest in chat)
   - Action item assignee marks done
   - Decisions logged by the deciding role

5. **Bot-assisted updates** — slash commands that update Loop components programmatically:
   - `/inc timeline <text>` — appends a Timeline row
   - `/inc decision <text>` — appends to Decisions log
   - `/inc action @user <text> due:<date>` — adds to Action items
   - `/inc status <active|mitigated|resolved>` — updates Status

6. **Postmortem integration** — at resolution:
   - Loop page contents are exported (Loop → Word, or Graph API)
   - Postmortem author imports the Timeline + Action items into the postmortem template
   - Loop page link is included in the postmortem for source-of-truth reference
   - Loop page is retained for compliance (retention policy applies to the underlying SharePoint site)

7. **Permissions & sharing** — Loop respects M365 group permissions. Channel members can edit; external users cannot edit unless added to the underlying group. Watch out for guest access in regulated environments.

8. **Mobile** — Loop components render on Teams mobile. Bot-assisted updates work via slash commands on mobile too. Good for on-call running from a phone.

9. **Anti-patterns** — using Loop as an excuse to skip postmortem write-up, putting customer PII in Loop without sensitivity label, depending on Loop to be reachable during a tenant-wide M365 incident (have a Plan B).

10. **Compliance overlay** — Loop component contents are stored in the user's OneDrive (for chat-initiated) or the channel's SharePoint (for channel-initiated). Apply retention + sensitivity labels accordingly; document for auditors.

Output as: (a) Loop pack spec for incident channels, (b) update convention chart, (c) slash command spec, (d) postmortem integration flow, (e) permissions / guest-access policy, (f) compliance + retention checklist.

Bias toward: minimal IC keystrokes during a live incident, collaborative editing not turn-based, audit trail durable past the channel.