---
title: "The service catalogue: one request, several teams"
description: "Turn a request type into a service catalogue item: one request creates tasks for several services, in parallel or in sequence, which the requester follows as a whole, up to automatic filing from an onboarding journey."
url: "https://illizeo.com/en/centre-aide/help-desk-service-catalogue/"
updated: "2026-11-20"
category: Help desk
---

# The service catalogue: one request, several teams

A new employee’s arrival needs a workstation from IT, a badge from facilities and access to the applications. With the service catalogue, a single request creates these tasks in the right teams’ queues, in parallel or in sequence, and the requester follows the whole as one. This article is for the help desk administrator, who sets up the catalogue, and for the agents who coordinate a request or handle a task; it also shows what the requester sees.

## Before you start

- To set up a catalogue item, you need the **Administer the help center** right (Execute level).
- To coordinate a request or handle a task, you must be an agent of the service concerned: a member of one of its agent groups who holds the **Help center agent** right (Execute level).
- Each service that receives a task must be active and have its agents (see [Setting up the help desk](https://illizeo.com/en/centre-aide/help-desk-setting-up/)).
- For a journey step to file the request: the Onboarding module installed and the **Onboarding — Create / edit step** right (Onboarding / Offboarding section of the role matrix).

## How it works

A catalogue item is a request type of one service, to which you add tasks spread across several services. The item’s service **coordinates**: the request filed arrives in its queue like any request. Each task is created in its own service’s queue: it is a real ticket, with its number, its agent and its deadlines.

- Tasks are arranged by **step**. The tasks of the same step start together, in parallel; those of the next step start once the previous step is finished.
- A resolved or closed task is finished. When all of them are, the request moves to “Resolved” on its own.
- The requester only follows the request: its progress task by task and the teams’ messages. They see neither the tasks, nor their agents, nor their internal notes.

## Creating a catalogue item

1. Open **Settings › Help center › Services**, then the service that will coordinate the request, for example Human resources.
2. In the **Request types** section, click **New request type**, or **Edit** for an existing type. Fill it in as usual: name, description, default priority, audience and form.
3. In the **Distributed tasks (service catalogue)** section, click **Add a task** for each team to involve.
4. For each task, set the **Step** (1 to 10: same number, in parallel; next number, in sequence), the **Service** that handles it, if needed its **Type (optional)** among that service’s types, and its **Label**, for example “Workstation”. The arrows change the order; the bin removes the task.
5. Click **Save**.

![Distributed tasks (service catalogue) section of a request type window: three tasks, Workstation and Access badge at step 1 (IT, Facilities), Application access at step 2, and the Add a task button](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-catalogue-01.en_.png?resize=718%2C629&quality=80&ssl=1)
The tasks of a catalogue item

In the service’s list of types, the item carries the **Item · 3 task(s)** badge. An item has at most 20 tasks, and a label at most 80 characters. The label is entered in your screen language; the other languages already saved are kept, and the requester reads it in their language, otherwise in French. A task’s optional type classifies it within its service: its rules and reporting use it as for any ticket. Removing all the tasks turns the type back into an ordinary request.

### Approval before the tasks

To have the request approved before the teams start, use a “Ticket to approve” workflow limited to this request type (see [Workflows and ticket approval](https://illizeo.com/en/centre-aide/help-desk-workflows-and-approval/)). The tasks are only created once the request is approved, and never if it is refused. A task never goes through an approval process itself.

## Coordinating the request

An agent of the coordinating service takes the request and follows it. Its page has one card per step: **Tasks — step 1**, **Tasks — step 2**… The current step carries the **Current step** badge. For each task: its number (a link when you can open it), its label, its state — *Upcoming*, *In progress*, *Resolved*, *Refused* or *Cancelled* —, its service, its agent, its deadline and, where relevant, the reason for a refusal or a cancellation.

![Page of a catalogue request as the coordinator sees it: The follow-up awaits your decision banner with Restart the follow-up and Cancel the follow-up, Tasks — step 1 card with a resolved task and a refused task with its reason, Tasks — step 2 card with an upcoming task and the Cancel button](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-catalogue-02.en_.png?resize=800%2C447&quality=80&ssl=1)
The request awaits the coordinator’s decision

- **Cancel**, next to an upcoming or in-progress task, cancels it with a reason that the requester will read. An upcoming task will not start; an in-progress task is closed in its service’s queue, and the agent who held it is notified.
- The request moves neither to “Resolved” nor to “Closed” while a task is in progress or a step is still to come; the screen says so: “This request still has tasks in progress: it is resolved when all of them are finished.”
- You reply to the requester and write internal notes on the request as on any ticket.

These actions belong to the agent who can move the request forward: the one who holds it, the service manager or, while it is unassigned, any agent of the service. The coordinator is notified, by the notification bell and by e-mail, of each refused or cancelled task and of each follow-up waiting for their decision: the agent who holds the request, otherwise the service’s agents.

## Handling a task

A task arrives in its service’s queue with its label followed by the request’s subject as its subject (“Workstation — Arrival of…”). The agent takes it, handles it and resolves it like any ticket: their service’s rules, macros, commitments, transfer and reporting apply to it. Its page also shows:

- the **Task of AST-…** banner, with the request’s status, the task’s step and the coordinating service;
- the **Original request** card: the request’s subject, description and form answers, and the employee concerned when it comes from a journey;
- the **Request conversation** card: the requester’s exchanges with all the teams, read-only.

![Agent’s page of a task: Task of AST-000074 banner, step 1, coordinated by Human resources, with Refuse the task; Original request and Request conversation cards; Task notes in Reply to the requester mode, which writes on the request](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-catalogue-03.en_.png?resize=800%2C560&quality=80&ssl=1)
A task in its service’s queue

There is a single conversation, held on the request. In **Task notes**, **Reply to the requester** writes on the request: the requester receives the message as a reply to their request, marked with your service’s name, and every task reads it (“From task AST-…”). An **Internal note** stays on the task. When the requester replies, the agent who holds each in-progress task is notified.

### Refusing a task

If your team cannot do the task, click **Refuse the task** in the banner, write the **Reason (read by the requester)** (up to 1,000 characters), then confirm. The task is closed, the reason is written in the request’s history, which the requester reads, and the coordinator is notified. A task is refused by the agent who holds it, or by their service manager; when unassigned, by any agent of the service.

## When a task is refused or cancelled

The other tasks of the same step carry on. When all the tasks of the step are finished:

- if none was refused or cancelled, the next step starts on its own;
- if one of them was and a step follows, the follow-up waits for the coordinator’s decision: the request’s page carries the **The follow-up awaits your decision** banner;
- if no step remains, the request is resolved.

The coordinator then chooses:

- **Restart the follow-up**: the next step starts;
- **Cancel the follow-up**, with a reason read by the requester: the upcoming tasks are cancelled, and the request is resolved once the remaining tasks are.

## What the requester sees

In **My requests**, as on the external portal for an external person, the request carries a **Progress** card: by step, each task with its label, its service, its state and, where relevant, the reason for a refusal or a cancellation. The counter (for example 2/3) shows how many tasks are finished.

![Progress card of a request as its requester sees it: 2 of 3 tasks finished, step 1 with Workstation resolved and Access badge refused with its reason, step 2 with Application access upcoming](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-catalogue-04.en_.png?resize=800%2C321&quality=80&ssl=1)
Progress as the requester sees it

- The teams’ messages arrive in the request’s **Conversation**, marked with the name of the service that writes. The requester’s reply is read by every task.
- The history shows each refused or cancelled task, with its label, its service and the reason, and the cancellation of the follow-up.
- Nothing that happens on a task notifies them (taking, status change, survey): they receive the teams’ replies and the request’s status changes.

## Resolving the request

When the last task is finished and no step remains, the request moves to “Resolved”; the history says “The system”. The requester is notified and receives the coordinating service’s satisfaction survey, if that service sends it; tasks send no survey. If the requester reopens the request, no task restarts: the coordinator takes over again.

## Deadlines

Each task takes the request’s priority and its own service’s commitments. The request’s resolution deadline covers those of its tasks: it is extended to the latest one, when the tasks are created and each time a task’s deadline changes (after a requalification, for example). A request whose service has no commitment for its priority gets none. See [Help desk service commitments](https://illizeo.com/en/centre-aide/help-desk-service-commitments/).

## Filing the request from an onboarding journey

A journey step can file a catalogue item on its own, for the employee who is arriving:

1. Open **Settings › On-Off/Boarding › Onboarding Steps**, then a step of the *General* type, or create one with **New step**.
2. In **Catalogue item (Help center)**, choose the item. *None — the step is handled manually* removes the link.
3. Click **Save**.

![New onboarding library step: Catalogue item (Help center) field with the Employee arrival — Human resources item, and the sentence explaining the filing when the journey starts](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-catalogue-05.en_.png?resize=800%2C147&quality=80&ssl=1)
A journey step linked to an item

When this step is created in an employee’s journey:

- the request is filed automatically, in the name of the step’s first owner, who is its requester, receives the acknowledgement and follows it in **My requests**;
- it is made for the employee concerned: its subject is the item’s label followed by their name, its description recalls the journey and the start date, and the agents’ page shows “For:” followed by their name;
- in the employee’s journey, the step shows “Request AST-…” and its status; it is completed on its own once the request is resolved.

The onboarding step library also serves crossboarding and reboarding journeys. The link only applies to a step of the *General* type, to an active item, and only if the help desk is active. If the step has no authorised owner, no request is filed: the step is handled manually.

## Good to know

- The tasks are taken when the request enters the queue: changing the item afterwards does not change requests already filed. A request that is transferred or requalified keeps its tasks, and nothing restarts.
- A task never creates tasks: choosing another item as a task’s type only gives it that type. A follow-up request (a reply after closure) is an ordinary request.
- Neither the request nor its tasks can be merged or attached to a major incident; they can be linked (see [Merging duplicates, linking tickets, observers and copies](https://illizeo.com/en/centre-aide/help-desk-merge-links-observers-copies/)).
- A rule that replies with a canned response has no effect on a task: the requester follows the request, and the task’s timeline says so.
- The notifications to the coordinator and to the task agents follow the “Help desk — requester activity on my tickets” checkbox in the personal settings, **Notifications** tab. Their e-mail is a template you can edit in **Settings › Manage Illizeo › Emails**, Help desk category.
- In reporting, each task counts as a ticket of its service, and the request as a ticket of the coordinating service.
- Data protection: erasing an employee also erases the content of the requests made for them by a journey, and an erased request erases its tasks.
- The mobile app shows the request and its conversation, without the Progress card.

### *Similaire*
