INTEGRATION / SLACK
An incident commander that lives in your Slack threads
Your incidents already happen in Slack. The problem is that a 200-message thread does not tell you who is in charge or what is still open. Incident Lake joins the thread, proposes the next decision, waits for a human to make it, and turns the conversation into a timeline you can hand to leadership.
1
Kick it off
An alert in a watched channel, or "@Incident Lake go"
2
One question at a time
"Pick a commander? Suggested: Alex, Sam." A person chooses
3
Tasks and a timeline
Decisions become tasks, open questions get nudged, the record writes itself
Illustrative mock. Demo video coming soon.
What it does
- Joins threads and responds to @mentions
- Proposes commander, severity and affected services for confirmation
- Creates tasks, chases unanswered questions, surfaces similar incidents
- Reads linked URLs and text inside screenshots
- Connects multiple workspaces
What it does not do
- Decide severity or declare resolution on its own
- Write to your monitoring, code or docs
- Watch channels an admin has not chosen
Setup at a glance
Install the app
A workspace admin approves the Incident Lake app.
Choose watched channels
Point it at your alert channels: 1 on the Free plan, up to 20 on Team.
Say the words
Type "@Incident Lake go" in a thread. We share detailed steps during onboarding.
FAQ
Will the bot overrule my incident commander?
No. It suggests; people in the thread confirm. Admins can set it to "Only when needed" or "Off".
Half our company is on Teams. Is that a problem?
No. Slack and Microsoft Teams are both supported.
What about decisions made on the bridge call?
A meeting bot joins Zoom, Google Meet or Teams calls and adds a transcript summary to the incident notes.
Add it to Slack and try it free
Work email and company name. That's the whole form.
Try it in Slack free →