Profile
During an outage, most of the time goes not on fixing it but on explaining it, to everyone, one by one.
The Outage Communicator spots the pattern in incoming tickets and monitoring, and prepares one message instead of fifty replies.
While the specialists work on the outage, it keeps the organisation informed.
What it does, step by step
- Recognise the patternSeveral tickets about the same thing in a short time, or a signal from monitoring.
- Draft a noticeWhat is happening, who it affects and what people can do in the meantime.
- Publish after approvalOn the status page and in the channels your organisation uses.
- Link incoming ticketsNew tickets about the same outage are linked instead of handled separately.
- Close and report backA message that it is resolved, with what happened.
Works with these systems
- APIs
- Databases
Azure DevOps
Jira Service Management- Freshdesk
Zendesk
SharePoint- Help centre
Is your system not listed? We can connect any system, even if there is no standard integration. View all integrations.
What runs automatically and what does not
You stay in control.
Not every decision should be made automatically. For each workflow, we set out:
- What can happen automatically.
- What is put forward for approval first.
- When a person is brought in.
- What information is stored.
- How actions are logged.
Is this a fit for your organisation?
A good fit if
- Organisations with many internal users of the same systems.
- Businesses with a status page that is currently updated by hand.
- Situations where outages produce lots of duplicate tickets.
Less of a fit if
- Fixing the outage itself.
- Organisations without monitoring: you only see an outage when someone calls.
What it can deliver
- One message instead of fifty separate replies.
- Specialists who can work on the outage instead of the communication.
- A timeline of what was reported when.
Directions, not promises. As soon as there is evidence from a client project, it will appear here as a substantiated result.
Frequently asked questions
Does the AI publish an outage notice by itself?
Only if you set it up that way, and we usually recommend approval from the administrator on duty. A false outage notice does damage of its own, especially when customers are reading along.
How does it recognise that it is one outage?
From the pattern: several tickets about the same topic or system within a short time, possibly combined with a signal from your monitoring. You set the threshold yourself.
Can it inform customers as well, not just colleagues?
Yes, but that is a separate decision with a different tone and a different approval route. We keep them apart on purpose, because an internal notice can be rougher than an external one.
What does this give you after an outage?
A timeline of what was reported and communicated, and when. That is exactly what you need for a review or for a customer asking for an explanation.
How to put this to work
- 1A short callTogether we look at your process and your systems, and whether this task is the best place to start.
- 2Set up on your rulesIntegrations with your own systems, and agreeing what may run automatically and what a person approves.
- 3Measure and adjustFirst alongside your team, only then on its own. We look at what it delivers and adjust.