---
title: Merging duplicates, linking tickets, observers and copies
description: Merge two requests that describe the same problem, link tickets together, have a ticket followed by observers and people in copy, and see what each requester reads.
url: "https://illizeo.com/en/centre-aide/help-desk-merge-links-observers-copies/"
updated: "2026-11-20"
category: Help desk
---

# Merging duplicates, linking tickets, observers and copies

Several people report the same fault, one ticket is waiting for another to be fixed, a manager wants to be kept informed, a supplier needs to read the replies: the help desk lets you merge duplicates, link tickets, add observers and put people in copy. This article is for agents and service managers; it also shows what requesters see.

## Before you start

- You must be a member of the service’s agent group and hold the **Help center agent** right at Execute level (see [Handling help desk tickets](https://illizeo.com/en/centre-aide/help-desk-handling-tickets/)).
- Linking tickets, following a ticket and adding an observer: any agent of the service. Merging and managing copies: you must be able to act on the ticket (on both for a merge), meaning it is free, you hold it or you are the service manager.
- Copies only exist in a service open to external people (the service’s **Open to** setting: *External people* or *Employees and external people*).
- An employee who observes a ticket must hold the **Help center requests** right, granted by default to all employees.

On the agent side, everything happens on the ticket page (**Help desk › Ticket queue**, then the ticket), in two cards of the right-hand column: **Links and merge** and **Following**.

![Links and merge and Following cards of a ticket: an absorbed duplicate, a related ticket, an observer and an address in copy](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-fusion-01.en_.png?resize=501%2C568&quality=80&ssl=1)
The Links and merge and Following cards on the ticket page

## Merging duplicates

When two requests of the same service describe the same problem, merge them: the main ticket absorbs the duplicate, and a single reply is enough for everyone.

1. Open one of the two tickets and, in the **Links and merge** card, click **Merge**.
2. In **Ticket**, enter a number or a few words of the subject, then choose the other ticket in the list. A ticket that belongs to another service, is no longer in progress or is waiting for approval is greyed out.
3. Under **Which ticket to keep?**, choose the main ticket, for example **Keep AST-000055: it absorbs AST-000056**.
4. Read the consequences shown, then click **Merge permanently**.

![Merge duplicates dialog: the duplicate found by its subject, the ticket to keep and the consequences of the merge](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-fusion-02.en_.png?resize=512%2C560&quality=80&ssl=1)
The merge dialog, before confirming

The **Probable duplicates** card (open tickets of the same requester that look alike) also offers **Merge here**: the same dialog opens, with the ticket you are on kept.

Merging is only possible between two tickets of the same service, both in progress (New, In progress or waiting), neither waiting for approval nor anonymised, nor attached to a major incident, nor part of the service catalogue (a request with tasks or one of its tasks, see [The service catalogue](https://illizeo.com/en/centre-aide/help-desk-service-catalogue/)). A ticket that has already absorbed duplicates cannot be absorbed in turn: merge the other one into it instead. A merge is final: nothing undoes it.

### What the merge does

- The absorbed ticket moves to “Closed” and points to the main ticket: its page shows the “Merged into AST-…” banner, with the date and the agent. It no longer changes; an internal note can still be added to it.
- Its conversation joins the main ticket’s, in order. A message that came from the duplicate reads “From AST-…”, and a message its requester writes afterwards reads “Requester of AST-…”.
- Its observers and copies move to the main ticket.
- Its requester is notified: in the notification bell and by e-mail for an employee, by e-mail for an external person. The main ticket’s requester is not notified.
- The merge is recorded in the timeline of both tickets (internal on the main ticket, visible to the requester on the absorbed ticket) and in the activity log.

![Conversation of the main ticket after the merge: messages marked From and Requester of, and the This reply goes to list](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-fusion-03.en_.png?resize=800%2C626&quality=80&ssl=1)
The combined conversation and the recipients of the next reply

Above the editor, **This reply goes to** lists who will receive your reply: the requester, the grouped requests, the people in copy and the observers. So write for everyone, with nothing that concerns only one requester.

## What each requester sees

After the merge, the requester of the absorbed ticket follows the main ticket:

- in **My requests**, they find it under the subject of their own request, marked “Your request was grouped into it”; their former ticket, closed, reads “Grouped into AST-…”;
- they read their own messages and the team’s replies written since the merge, never the other requesters’ messages or names, and they can reply;
- each reply from the team reaches them under the subject of their own request;
- confirming the resolution, reopening the request and giving feedback remain with the main ticket’s requester only.

![Request of an employee grouped into another ticket: grouping banner, her request, her messages and the team’s shared reply](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-fusion-04.en_.png?resize=800%2C522&quality=80&ssl=1)
What the requester of the absorbed ticket reads

The main ticket’s requester reads their request as before, without the grouped requesters’ messages or names. An external person whose request is grouped finds it on the portal, through the link in the grouping e-mail. A reply sent to the absorbed ticket, from the employee space, the portal, an e-mail or Microsoft Teams, joins the main ticket.

## Linking tickets

A link connects two tickets without merging them: an incident that blocks others, a request that concerns another one.

1. In the **Links and merge** card, click **Link a ticket**.
2. Under **This ticket…**, choose the relation: **Related to**, **Blocks**, **Blocked by** or **Duplicate of**.
3. Search for the other ticket by its number or subject, choose it, then click **Link**.

The link reads both ways: a ticket that “Blocks” another shows as “Blocked by” on the other one, and a “Duplicate of” reads “Has duplicate” there. Each link shows the other ticket’s status; the icon on its right removes it. Adding and removing are recorded in the internal timeline of both tickets: the requester sees none of it. You can only link tickets of your services, 50 links at most per ticket.

## Adding observers

An observer follows a ticket without being its requester: a manager, a colleague involved, an agent who wants to be kept informed. They receive the team’s replies and the status changes, never an internal note. The requester does not see who follows their request.

1. In the **Following** card, under **Observers**, search for the person in **An employee or an agent**.
2. Click **Add**. The cross next to a name removes it.

To follow the ticket yourself, click **Follow**; **Unfollow** stops it. You can add an agent of the service or an employee who holds the **Help center requests** right, but neither the requester nor an employee who has left. An absorbed ticket cannot be followed: follow the main ticket. A ticket has 25 observers at most.

An agent of the service opens the ticket from the notification they receive. Any other employee finds it in **Help desk › My requests**, **Followed** tab, which only appears when they follow at least one request. There they read the request and its conversation with the team, without replying, and can click **Unfollow**.

![Request followed by an observer: You follow this request banner, Unfollow button, conversation without a reply box](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-fusion-05.en_.png?resize=800%2C379&quality=80&ssl=1)
A followed request, observer side

## Putting people in copy

A person in copy, for example a supplier or a colleague of the customer, receives the team’s replies by e-mail, reads the request on the external portal and replies to it, on the portal or by e-mail. They do not receive status changes; confirming, reopening and rating remain with the requester.

- **From an e-mail**: the addresses in copy (Cc) of an e-mail received at the service’s address, whether it opens a request or replies to one, become copies. The card marks them “e-mail Cc”.
- **By the agent**: in the **Following** card, under **Copies**, enter the **E-mail address** and, if needed, the **Name (optional)**, then click **Add**.

Once removed with the cross, a copy no longer receives anything and can no longer access the request. A copy can only be added to a ticket in progress; the help desk’s own address, a blocked address and the requester’s address are refused. An e-mail brings in 10 copies at most, and a ticket has 25 at most.

The person in copy opens the request through the link in the e-mail they received, or from **Follow my requests** on the portal (see [External portal and incoming e-mail](https://illizeo.com/en/centre-aide/help-desk-external-portal-and-incoming-email/)); a banner tells them “You are in copy of this request”.

## Good to know

- While the approval flow is running, a ticket can be linked and followed, but it cannot be merged or receive copies.
- A reply from a grouped requester or a person in copy follows the usual rules: on a resolved main ticket, it reopens it during the reopening period; on a closed one, it opens a follow-up request in the name of the requester of their original request.
- The absorbed ticket counts among incoming tickets in reporting, never among resolved ones.
- For workflows, the merge is a move of the absorbed ticket to “Closed” (**Ticket status changed** trigger). In the service’s Microsoft Teams channel, its card shows the merge.
- Notifications of a followed ticket are set in the personal settings, **Notifications** tab, checkbox “Help desk — tickets I follow”. The grouping notice follows the checkbox “Help desk — progress of my requests (in progress, resolved, closed)”.
- The grouping e-mails (employee and external person), the reply in copy and the followed ticket e-mail are templates you can edit in **Settings › Manage Illizeo › Emails**, Help desk category.
- Data protection: the export and erasure of an external person’s data include the requests they are in copy of and what they wrote there; an erased employee no longer follows any ticket.
- The mobile app has no Followed tab: a grouped request can be read there, a followed request is read in the web version of Illizeo.

### *Similaire*
