Vibe OnCall is available as an active collaborator throughout the incident lifecycle, not just as a passive observer. It can answer questions, surface context from connected tools, and take action on your behalf, both from the Ask Vibe tab on the incident detail page and directly from Slack.

Where to Interact with Vibe OnCall

From the incident detail page Open any incident and navigate to the Discussions → Ask Vibe tab. This interface is scoped to the full context of that specific incident — all associated Slack threads, meeting transcripts, timeline events, and data from connected integrations. Type your question in the input field at the bottom to get a response.

From Slack Tag Vibe OnCall in any monitored channel thread or send it a direct message. When referencing a specific incident from Slack, include the incident ID for the most accurate results (e.g., "What's the status of incident 1477?").

What Vibe OnCall Knows About an Incident

When answering questions about an incident, Vibe OnCall draws on all available context attached to that incident, including:

• Slack threads — All messages and replies from every associated thread, across any number of channels
• Meeting transcripts — Full transcriptions from any Google Meet or Zoom sessions Vibe OnCall joined during the incident
• ITSM tools — Tickets, issues, and updates from connected tools such as Jira and Linear
• Documentation — Relevant pages from connected knowledge bases such as Confluence and Notion
• CMDB — Service and dependency information from tools such as Backstage
• Monitoring & observability — Metrics, logs, and alert data from connected tools such as Datadog

The specific integrations available depend on which tools your organization has connected to Vibe OnCall. See Contextual Intelligence — Integrated Tools for more detail.

A Note on Response Quality

Vibe OnCall's ability to answer questions accurately and thoroughly is directly shaped by two factors: the integrations available for your organization and the quality of context those integrations provide.

Integrations determine what Vibe OnCall can see. If a tool is not connected — or if access has not been granted — Vibe OnCall cannot draw on it. For example, if Confluence is not integrated, Vibe OnCall cannot surface relevant runbooks or documentation during an incident. The richer the integration footprint, the more comprehensively Vibe OnCall can answer questions.

Context quality determines how well Vibe OnCall can reason. Vibe OnCall synthesizes answers from the conversations, documents, tickets, and data available to it. If Slack threads are sparse, meeting transcripts are absent, or Jira tickets are poorly documented, Vibe OnCall's responses will reflect those gaps. Conversely, teams that maintain detailed incident threads, write descriptive Jira tickets, and keep documentation up to date will get significantly more accurate and actionable responses.