Incident comms at the speed of chat
A status page built into your support platform. Define the components your customers care about, publish incidents, and post updates through to resolution — with email subscribers, your own domain, and an embeddable widget. And when it's urgent, the whole flow runs from Slack.
500 conversations, no credit card.
Watch an incident go from Slack to status page
What's in Incidents
- SlackOpen, update and resolve an incident from your incidents channel.
- Incident DiscoverySidekick matches what a customer wrote to an open incident.
- ComponentsThe parts of your product, each with its own state and group.
- Status pageA hosted public page with your logo, colours and wording.
- SubscribersCustomers sign themselves up and get an email on every update.
- Custom domainServe the page from status.yourcompany.com, certificate included.
- EmbedA script badge or an iframe for your own site.
- Planned maintenanceA scheduled window that opens and closes itself.
- Post-mortemA write-up on a resolved incident, private until you publish it.
- Internal incidentsFor your team only, never shown on the status page.
- Incident automationsRules that fire when an incident is created, updated or resolved.
- Status APIIncidents, components, subscribers and settings over REST and MCP.
Components tell the honest story
Break your product into the pieces customers actually experience — API, Dashboard, Email, Phone — each with its own state, and give two of them the same group name to show them together. An incident marks exactly what is affected, so customers see "Email is degraded" instead of a vague all-red banner. When the incident resolves, the components go back to Operational unless another open incident still holds them down.
- Set each affected component to Operational, Degraded or Unavailable
- The public page reads All Systems Operational when nothing is down
- Components with the same group name are listed under one heading
- An email component can move itself when we detect a provider outage
Update and resolve — without leaving Slack
Connect a private incidents channel and the whole lifecycle lives where your team already is — no logging in, no other interface to touch during an outage.
One sentence to publish
Write "Email delivery is delayed for some customers" and the bot replies with the incident ready to go: AI-derived title, status, severity, and the affected components pre-selected from your real ones. Nothing goes public without a human clicking Publish incident — and whoever's in the channel can publish, nobody else. On the Slack side, access control is just Slack.
The thread becomes the log
Replying in the thread posts updates; resolving works the same way — with per-component impact right on the card, so Email flips back to Operational in the same click. After each action the bot collapses its card into a one-line receipt, and the channel reads as a clean timeline that mirrors the public page.
Your AI already knows about the outage
During an outage, your inbox fills with the same question phrased a hundred ways. Incident Discovery, a switch under Sidekick, matches the conversation to an open incident by meaning — "your login keeps timing out" finds "Authentication latency degraded" with no words in common. The agent links the two, can offer the customer a subscription to the incident, and answers with its status instead of starting a fresh investigation. An agent stack has its own tool for looking up the open incidents.
- Incident Discovery is a switch under Sidekick, off until you turn it on
- Only public incidents are matched — internal ones stay out of it
- The agent can offer the customer a subscription from the conversation
- Automation rules can fire when an incident is created, updated or resolved
Incidents keep the rest of the platform honest during an outage. Conversations and AI Agents surface the matching incident instead of re-investigating. Monitor shows the surge in real time. And the Slack connection lives in Integrations.
Conversations
Sidekick matches an incoming conversation to an open incident, deflecting the "is it just me?" wave.
AI Agents
An agent stack has a tool that looks up the open incidents before it answers.
Monitor
Watch conversation volume spike and settle in real time as incidents open and resolve.
Integrations
One Slack app powers support channels and the incidents channel alike — one install covers both.
Status pages, minus the panic.
See Atender in action
Try the full platform for free. Or book a demo and we will walk you through it.
500 conversations, no credit card.