Incidents
The customers who are only checking.
Many affected customers never contact you — they look for a status page, find nothing, and form a view. Publishing early costs very little and prevents most of that.
Published from the same incident
The public update and the message on the cases come from one source, so the public wording and what an agent says cannot contradict each other.
Separate what is public
Internal investigation notes stay internal. The boundary is structural rather than a checkbox somebody may forget under pressure.
It renders on your own site
Where your website is on a platform this can publish to, the status page is on your domain. Everybody looks at yourcompany.com first.
Incidents
The rest of this area.
Group related cases, communicate once, close them all together.
Spotting the cluster
Similar cases arriving together, flagged as probably related.
Who is affected
Everyone hit, including the ones who have not written in.
Status updates
One message, to every affected customer, at once.
Telling everyone it is fixed
One action closes the loop with every affected customer.
When it happens again
Repeated incidents pointing at one root cause.
Take better care of every customer.
Give your team the context, knowledge and AI they need to resolve problems properly — and know who needs attention before they ask.
Keep the mailbox you already use · The AI is never metered · [email protected]