---
title: Major incidents and problems
description: "When an outage affects many people: declare a major incident, attach its tickets, inform everyone with a single message and resolve them together; then find the cause in a problem."
url: "https://illizeo.com/en/centre-aide/help-desk-major-incidents-and-problems/"
updated: "2026-11-20"
category: Help desk
---

# Major incidents and problems

E-mail is down, the VPN no longer responds: dozens of people write about the same thing. A major incident groups their tickets, informs everyone affected with a single message and resolves them together; a banner warns the others before they file a request. A problem then helps find the cause, work around it, and remove it. This article is for the people who manage incidents and for agents; it also shows what requesters see.

## Before you start

- The **Incidents and problems** right (Help center section of the role matrix): Access level to read incidents and problems, Execute to declare, inform about, resolve and edit an incident, attach tickets to it from its page and manage problems. By default, only the administrator holds it: grant it to the roles that steer outages. It is not billed.
- Without this right, an agent (**Help center agent** right, Execute level) attaches and detaches, from its page, a ticket they can move forward, to an ongoing incident that affects their service.
- To turn a problem into a knowledge base article, you also need the **Knowledge base writer** right (Execute level).

## Declaring an incident

1. Open **Help desk › Incidents** and click **Declare an incident**. From a ticket’s page, the **Major incident** card also offers **Declare an incident**: that ticket is then attached automatically.
2. Enter the **Title**, for example “E-mail unavailable”, and the **Banner message, read by users**, for example “We are working on it. No need to make a request: just let us know you are affected.”
3. Tick the **Affected services**.
4. If needed, add an **Internal description (never shown to users)**, then click **Declare the incident**.

The incident gets its number (INC-000001…) and its page opens. The agents of the affected services are notified by the notification bell and by e-mail, and the banner is shown at once to the users of these services. The title and the banner are written in your screen language: a person who reads another language sees the French version, otherwise the language entered.

![Incidents page: Declare an incident button, an ongoing incident and a resolved incident with their affected services, numbers of tickets and people affected, and dates](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-incidents-01.en_.png?resize=800%2C263&quality=80&ssl=1)
The list of incidents

The list shows the **Ongoing** incidents, then the **Resolved** ones, with their **Affected services**, the number of **Tickets** and of **People affected**, and their dates. While the incident is ongoing, **Edit**, on its page, changes its title, banner, services and description; a service that still has attached tickets cannot be removed.

## Attaching tickets

Attach the tickets that mention the outage to the incident, rather than answering them one by one:

- from the incident’s page, **Attached tickets** card: paste one or more numbers in **Attach by number**, or search your queue (**Search your queue: number or subject…**), tick the tickets, then **Attach the selection**. The summary says how many tickets were attached, and why the others were left out;
- from a ticket’s page, **Major incident** card: choose the incident under **Attach to an ongoing incident**, then click **Attach**. Only the ongoing incidents that affect the ticket’s service are offered.

![Page of ongoing incident INC-000002: Edit and Resolve buttons, banner as users see it, three attached tickets with Detach, Reach, Internal description and Related problems cards](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-incidents-02.en_.png?resize=800%2C391&quality=80&ssl=1)
An ongoing incident’s page

A ticket can be attached if it is open (neither “Resolved” nor “Closed”), in an affected service, neither awaiting approval nor anonymised, not part of the service catalogue (a request with tasks or one of its tasks), and does not already follow another ongoing incident. One submission attaches at most 200 tickets.

### What attaching changes

- The ticket keeps its status, and its deadlines are **paused**: no reminder and no escalation, first response included. A banner says so at the top of its page: “Attached to incident INC-…: its deadlines are paused.”
- While it follows the incident, it changes neither status nor service and cannot be merged: these actions are refused, with the reason. It can be taken or assigned, and you can leave an internal note on it and reply to the requester, without changing the status in the same move.
- A reply from the requester does not change its status; the agent who holds it is notified as usual.
- Attaching is recorded in the ticket’s internal timeline.

![Attached ticket as the agent sees it: Attached to incident INC-000002: its deadlines are paused banner, actions limited to assignment, and Major incident card with the attachment date and the Detach button](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-incidents-03.en_.png?resize=800%2C333&quality=80&ssl=1)
A ticket attached to an incident

**Detach**, on the ticket’s page or in the incident’s list, gives the ticket back its own lifecycle: the pause ends and the resolution deadline restarts, shifted by the time spent paused. The agent who can move the ticket forward detaches it, as can the person who manages incidents. A ticket resolved with the incident can no longer be detached.

## Informing the people affected

On the incident’s page, the **Inform the people affected** card sends a common message: write it, then click **Send to N person(s)**.

- The message is added, public and signed with your name, to the conversation of each attached ticket. The **Messages sent** card keeps its history.
- Each person affected receives it **only once**, even with several attached tickets: requesters, requesters grouped by a merge, people in copy and observers. An employee receives it in the notification bell and by e-mail, an external person by e-mail.
- It does not count as the tickets’ first response.

## The banner and “I am affected”

While the incident is ongoing, a banner announces it, with its message, to the users of the affected services:

- employees, for a service open to employees: at the top of **My requests**, and in the filing window when the chosen service is affected;
- external people, for a service open to external people: on the external portal home page and in the help widget.

![An employee’s My requests page: banner of the VPN access unavailable incident, its message, the sentence No need to file a request for this outage and the I am affected button, above the list of requests](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-incidents-04.en_.png?resize=800%2C412&quality=80&ssl=1)
The banner in My requests

**I am affected** creates the person’s request, already attached to the incident, with the incident’s title as its subject. They receive an acknowledgement that says so, then the common messages and the resolution notice; the team sees how many people are affected. The banner then shows “You already follow this incident”. On the portal without an open session, and in the widget, the button opens the usual request form, prefilled (service and subject), stating that the request will follow the incident; on the portal, **My request is about something else** removes this link. Filing a request as usual remains possible for another matter.

## Resolving the incident

1. On the incident’s page, click **Resolve**.
2. Read the warning: the number of tickets still open that will move to “Resolved” and of people who will be notified.
3. Write the **Resolution note (read by each person affected)**, then click **Resolve the incident**.

Each attached ticket still open moves to “Resolved”, in your name and with the note. Each person affected receives a single resolution notice: no status notice and no satisfaction survey per ticket. The deadline pause ends, and the banner disappears on its own. A resolved incident cannot be reopened and no longer receives messages or tickets; a request resolved with it can be reopened like any resolved request.

## Problems: finding and removing the cause

A problem describes the cause of one or more incidents, how to work around it, then the permanent solution.

1. Open **Help desk › Problems** and click **New problem**, or, from an incident’s page, **Open a problem to find its cause** (the incident is linked automatically).
2. Enter the **Title** and, if needed, the **Description**, then click **Open the problem**. The problem gets its number (PRB-000001…).
3. On its page, fill in the **Root cause**, the **Workaround** (what to do in the meantime) and the **Permanent solution**, and move the **Status** along: *Open*, *Workaround in place*, *Resolved*. A problem can only be *Resolved* with its permanent solution.
4. Link the incidents (**Link an incident**) and the tickets (**Link a ticket by its number**) concerned, then click **Save**.

![Page of problem PRB-000002, Workaround in place status: title, description, root cause, workaround and permanent solution; Related incidents, Related tickets and Knowledge base cards with Create an article](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-incidents-05.en_.png?resize=800%2C613&quality=80&ssl=1)
A problem’s page

Related problems are shown on each incident’s page and, in the **Major incident** card, on each linked ticket. The list of problems shows unresolved ones first.

### Turning the solution into an article

A problem’s solution can help others. In the **Knowledge base** card of its page, **Create an article** creates a knowledge base draft: the problem’s title, then the workaround and the solution, each under its own heading. Choose its **Service** and **Category** if needed, then click **Create the draft**. An article filed under a service can be read by that service’s users; without a service, the article is internal. Review it before publishing it (see [The knowledge base](https://illizeo.com/en/centre-aide/help-desk-knowledge-base/)). This requires the writer right and a saved workaround or solution; a problem has only one article.

## Good to know

- The search and the numbers on the incident’s page cover the tickets of your queue: someone who manages incidents without being an agent of the affected service finds no ticket there. Agents then attach from their tickets’ pages.
- The first-response deadline of an attached ticket is not shifted: it has no reminder and no escalation during the incident, and the common message does not meet it. Reply to the requester if that first response matters to you.
- Notifications follow the checkboxes in the personal settings, **Notifications** tab: the declaration, “Help desk — requester activity on my tickets”; the common message, “Help desk — replies to my requests”; the resolution, “Help desk — progress of my requests (in progress, resolved, closed)”.
- The e-mails (incident declared, news about an incident, incident resolved, acknowledgement of a request that follows an incident) are templates you can edit in **Settings › Manage Illizeo › Emails**, Help desk category. Employees are addressed informally, external people formally, and the e-mails carry your brand.
- For workflows and rules, the resolution is a status change of each attached ticket; there is no trigger specific to incidents.
- Incidents, their common messages and problems are recorded in the activity log, without their descriptions, notes or messages. An incident or a problem holds no requester personal data; anonymising a ticket detaches it from its incident and removes its links to problems.
- The banner only appears in the help desk (My requests, filing window, portal, widget), not elsewhere in Illizeo, nor in Microsoft Teams, nor in the mobile app.

### *Similaire*
