Use Bridge Links and Alert Context

Before you start

• Open the incident command center.
• Make sure the incident has the right integrations linked for the response workflow you use.

Do this

1. Use the bridge buttons at the top of the incident to jump to Slack, Microsoft Teams, Zoom, Google Meet, Jira, or Statuspage when those links exist.
2. Keep the command center open while you work so the incident remains the source of record.
3. Review Alert Occurrences to see how many times the same alert has fired, when it first appeared, and when it last repeated.
4. Check related incidents if the alert has reopened over time or returned after a previous resolution.
5. Use the change summary to spot recent deploys, commits, or dependency changes that may explain the incident.
6. Use transcripts if you need to review bridge activity without replaying the meeting or chat manually.

Check it worked

• Responders can reach the active bridge from the incident page.
• The team can see whether the alert is still arriving or is a repeat of earlier noise.
• The incident record keeps the bridge links and recent context in one place.

If it does not work

• If a bridge link is missing, fix the corresponding integration before the next live incident.
• If repeated alerts are creating confusion, review the source mapping and dedupe behavior.
• If related incidents look wrong, check whether the source is sending a stable external id or dedupe key.

Next

• Map and route alerts
• Close the incident and hand off follow-through