Incidents

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, 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, an optional group, and a current status (operational, degraded, partial outage, major outage, or maintenance).

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.