Vibe OnCall supports two paths to incident creation: automatic detection by Vibe AI, and manual declaration by a user. Both paths result in a fully tracked incident with Slack thread context attached.


How Vibe AI Monitors Slack

Vibe AI listens for incident signals in designated Slack channels. A channel becomes monitored when two conditions are met:

  1. Vibe AI is invited to the channel — add Vibe AI to any Slack channel the same way you would add any other member.
  2. The channel listener is configured by Vibranium Labs — channel-level listener configuration is currently set up by the Vibranium Labs team. Contact your account team to enable monitoring on additional channels.

Coming soon: Self-serve channel configuration will allow admins to manage monitored channels directly from the Vibe OnCall dashboard without engaging Vibranium Labs.


Automatic Incident Detection

When Vibe AI is active in a monitored channel, it continuously analyzes message activity for signals that indicate an incident. This analysis happens across multiple signals simultaneously — message content, conversational patterns, timing, and cross-thread context — to determine whether a thread represents an active incident.

When Vibe AI determines that a thread warrants an incident:

  1. An incident is automatically created — no user confirmation is required.
  2. Vibe AI posts a notification in the thread — acknowledging that an incident has been created and providing a link to the incident in Vibe OnCall.
  3. The full thread is transcribed — all messages and replies in the Slack thread are captured and attached to the incident as context.

image.png

Meeting Transcription

If a Google Meet or Zoom link is posted in a monitored thread, Vibe AI will automatically request to join the meeting. Once its join request is accepted, Vibe AI joins the call and transcribes the conversation. The meeting transcript is attached to the incident, extending the contextual record beyond Slack into live war room discussions.

Note: Vibe AI will only transcribe a meeting after its join request is explicitly accepted by a meeting participant. It does not join meetings automatically without acceptance.


Thread Grouping — Related Signals, One Incident