The detail page is where you see everything about a single item and drive its lifecycle.

Header

At the top: ID · Title · Status · Assignee · Type (Incident or Alert) · Severity · Created time.

Quick links

Below the header, an icon row links straight out to the incident's connected resources — tap to jump there in the right app:

• Chat channels — the originating channel, related channels, and the Slack/Teams war room (duplicates are collapsed).
• Meeting — the active call link (Google Meet / Teams / Zoom), following your org's platform preference.
• Tickets — linked Jira / Linear issues.

Two tabs: Details & Timeline

• Details — summary information about the item.
• Timeline — chronological log of state changes (opened, acknowledged, resolved, reopened, etc.) and other events. Entries backed by an external resource (a new Slack channel, a created Jira/Linear ticket) are tappable and open that link.

Each entry shows who performed the action — a teammate, or the Vibe OnCall agent. Agent actions display an agent pill; when the agent acted on someone's instruction, the pill reads "directed by {name}", with a chip showing where the command came from (Slack, web, etc.) and the quoted command itself. Event descriptions (status, severity, responder, and field changes) appear in your app language. The header's Acknowledged / Resolved by attribution matches the timeline — actions taken autonomously by the agent are credited to the agent, not a person.

Actions & lifecycle

Every item moves through the same lifecycle:

Open ──Acknowledge──▶ Acknowledged ──Resolve──▶ Resolved
  ▲                                                │
  └──────────────────Reopen────────────────────────┘

Incidents — a single action button at the bottom advances the incident:

• Open → tap Acknowledge ("I'm taking ownership")
• Acknowledged → tap Resolve ("It's fixed")