Incidents

Set a status page component's System link to an internal system key like Email so Atender's dependency watcher automatically opens, updates, and clears incidents on your status page — and posts to Slack — when that provider has an outage.

Write a post-mortem on any resolved, non-maintenance incident from the incident detail screen. Drafts autosave and stay private to your team; Publish puts the report on the public status page and can email subscribers.

Announce planned work before it happens by scheduling a maintenance with a start and optional end time. Manage it from the Planned tab and planned-window panel, and control when affected components actually show impact on the status page.

Designate a Slack channel as your incidents channel. Posting there launches an interactive Publish flow for a status-page incident, and thread replies become gated updates — no need to leave Slack.

Every value the status field of an incident can hold, what each one means, when to pick it, and how the composer's suggested next status works.

Every value a component status can hold, what each means, how each is labelled and coloured on each surface, how they roll up to the overall system status, and the difference between component status and incident status.

Open the incident, expand the composer, pick a status, write the update, and post. Subscribers receive an email; the public page reflects the new status immediately.

Customers self-subscribe from the public status page. As an admin you don't add subscribers — you manage who's already subscribed, export the list, and choose which email address sends the notifications.

Add a small live-status indicator to your main website or product, with one of two embeds — a script snippet that adapts to the host page, or an iframe with full color control.

Open the Incidents module, click New incident, fill in a title, pick affected components, and post the first update — the public status page, your subscribers, and your AI agents all pick it up immediately.

Add a domain like status.yourcompany.com so visitors see your status page at your own URL instead of the default tenant slug.

Define the named pieces of your system that customers see on the status page. Each component has a name, a current status (operational, degraded, partial outage, major outage, or maintenance), and an optional description.

If more than one customer is likely to ask the same question, or the issue is visible to anyone watching your service, create the incident. The break-even is much lower than people expect.

Atender's Incidents module is a built-in status page system. Communicate outages and maintenance to customers, let subscribers receive email updates, and surface ongoing incidents to both AI and human agents so the response to inbound questions stays consistent during a disruption.