---
title: "The help desk and the CRM: linked customers and contracts"
description: Link external people to their CRM contact and organisation, give an organisation a contract (service level) and follow its tickets from the CRM.
url: "https://illizeo.com/en/centre-aide/help-desk-crm-and-customer-contracts/"
updated: "2026-11-18"
category: Help desk
---

# The help desk and the CRM: linked customers and contracts

When your space also has the CRM, the help desk recognises your customers: an external person who writes to the help desk is linked to their contact and their organisation. The organisation’s contract (its service level) then sets the deadlines of their tickets, and the CRM records show their tickets. This article is for agents, the help desk administrator and sales teams.

## Before you start

- The **Help desk** and **CRM** modules must be active. Without the CRM, client organisations and contracts work too (see [Client organisations](https://illizeo.com/en/centre-aide/help-desk-client-organisations/)); the CRM adds the contact, linking by exact address and the Tickets tab on its records.
- Only external requesters are concerned: those from the portal, from incoming e-mail and from tickets filed by an agent for an external person. An employee has no contract.
- Linking a requester: the **Help center agent** right (Execute level), on a ticket you can handle.
- Setting up contracts: the **Administer the help center** right (Execute level; Access to read them).
- Seeing the **Tickets** tab of a CRM record: being able to read that record (“CRM accounts — View” or “CRM contacts — View”, within your scope).

## How a requester is linked

### Automatically, by their address

If a single CRM contact has exactly the requester’s e-mail address, and that contact is attached to a single active account, the requester is linked to that contact and their organisation as soon as the ticket is filed. The organisation’s contract applies straight away.

A client organisation can also link automatically the people who write from its domains, or who sign in through its directory (see [Client organisations](https://illizeo.com/en/centre-aide/help-desk-client-organisations/)).

### Through a suggestion

Otherwise, the ticket page suggests a link in the **Requester** card, under **Customer in the CRM**:

- **CRM contact with this address**: a contact has this address, but is attached to several accounts;
- **Organisation with the same domain**: an organisation’s website or e-mail address has the domain of the requester’s address. A public mailbox (Gmail, Outlook, Bluewin…) never points to an organisation.

![Requester card of a ticket: Customer in the CRM section with an organisation suggested by domain, Confirm, Search for an organisation and Dismiss the suggestions](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-crm-01.en_.png?resize=426%2C325&quality=80&ssl=1)
A link suggestion

1. Check the suggestion, then click **Confirm**.
2. If no suggestion fits, click **Dismiss the suggestions**: they will not come back for this person.

### Chosen by the agent

1. Click **Search for an organisation** (or **Link to another organisation** to change a link).
2. Type at least two letters of the name: the list shows active organisations, with their contract.
3. Choose the organisation. If you read CRM contacts, you can also choose one of its contacts in **Contact (optional)**.
4. Click **Link**.

The link applies to the person, not just to the ticket:

- their open tickets take the organisation and its contract, and their deadlines are recalculated;
- their resolved or closed tickets take the organisation for the record, with no recalculation;
- the organisation they had typed is replaced with the name of the linked organisation.

A wrong link is removed with **Remove the link**: its open tickets go back to the service commitments. After a removal, or dismissed suggestions, the person is no longer linked automatically; only an agent can link them again.

## What the ticket page shows

![Requester card of an automatically linked ticket: organisation, contact, account owner, Premium contract and its minimum priority](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-crm-02.en_.png?resize=426%2C462&quality=80&ssl=1)
A requester linked to their organisation

- Every agent sees the organisation, the contact, the contract with its minimum priority, where the link comes from and who confirmed it.
- The account owner and the link to the account record only appear to people who read that account in the CRM. The link to the contact record follows the same rule for contacts. An agent without CRM rights therefore only sees names, never sales data.
- An escalation reader reads this section without being able to act on it.

## Customer contracts

Service levels are set in **Settings › Help center › Customer contracts**.

![Customer contracts page: Premium level with its minimum priority and its grid in business hours, organisations under contract](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-crm-04.en_.png?resize=800%2C821&quality=80&ssl=1)
Customer contracts

### Creating a service level

1. Under **New level**, type a name (for example “Premium”), then click **Create**.
2. Choose the **Minimum priority**, or leave *None*.
3. Fill in the grid, in business hours: **First response** and **Resolution** for each priority the contract sets. A priority left empty follows the service commitments.
4. Leave **Active** on, then click **Save**.

### Giving a contract to an organisation

1. Under **Give a contract to an organisation**, type the organisation’s name.
2. Next to the organisation found, choose the level.

The **Organisations under contract** list lets you change an organisation’s level or remove it (cross). The contract can also be chosen from the **Tickets** tab of the account record, in the CRM.

### How the contract applies

- For the priorities it sets, the contract grid takes precedence over the service’s. Business hours remain those of the ticket’s service.
- The minimum priority is a floor. A ticket filed or linked below it is raised to the floor, and a requalification below it is refused, with a message that names the contract (for example “The Premium contract requires at least the High priority.”).
- Changing a level, or an organisation’s level, never moves a deadline already announced: like a service grid, it applies to the following tickets.
- A deactivated level no longer applies. A level given to an organisation, or that has set the deadlines of a ticket, cannot be deleted: deactivate it.

## What the timeline says

The ticket timeline keeps each step: the link (automatic, or by whom, and how), the contract applied with the raised priority, and the recalculated deadlines.

![Ticket timeline: link by domain, Premium contract applied with the raised priority, deadlines recalculated](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-crm-03.en_.png?resize=800%2C244&quality=80&ssl=1)
The link in the timeline

The link and the contract are internal events. The requester only sees their new deadline, never the name of the contract.

## The CRM Tickets tab

CRM **Account** and **Contact** records have a **Tickets** tab when the help desk is active.

![Tickets tab of a CRM account: open, resolved or closed tickets, satisfaction, support contract and ticket list](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/centre-assistance-crm-05.en_.png?resize=800%2C314&quality=80&ssl=1)
An account’s Tickets tab

- Anyone who reads the record sees the figures: **Open**, **Resolved or closed** and the average **Satisfaction**, with the number of answers.
- The list only shows the tickets you read as an agent of the service (or an escalation reader): number, subject, status, deadline soon or missed, priority, service, filing date and rating. The others are only counted.
- On an account, the **Support contract** line gives the organisation’s contract; the help desk administrator can choose it there.

## Workflows and reporting

- In help desk workflows, the **Organisation contract among** condition routes a ticket according to its organisation’s contract (see [Workflows and ticket approval](https://illizeo.com/en/centre-aide/help-desk-workflows-and-approval/)).
- The **Help desk tickets** report and the **Tickets** tab of **Help desk › Performance** have the **Organisation** and **Customer contract** columns, and can be broken down by **Customer contract** to track how each contract’s commitments are met (see [Help desk satisfaction and reporting](https://illizeo.com/en/centre-aide/help-desk-satisfaction-and-reporting/)).

## Good to know

- Uninstalling the CRM deletes no ticket and undoes no link: the requester stays linked to their organisation, which keeps its contract. Only the link to the CRM contact is put to sleep; it comes back with the CRM.
- Deleting the CRM account of an organisation that tickets refer to does not delete the organisation: it stays, with its tickets.
- When two contacts or two organisations are merged in the CRM, tickets and requesters follow the record that is kept. The merged-away organisation’s contract moves to the kept organisation if it has none; if it already has its own, it keeps it, and the merge preview warns that the other one will not move over.
- Erasing an external person’s data (GDPR) removes their link to the CRM contact; their tickets keep the organisation, for reporting.

### *Similaire*
