Help desk — HR, IT and external tickets

A help desk for every request. Internal and external, handled on time.

Illizeo’s help desk is a ticketing tool built into the HRIS. Your employees and outside contacts submit their requests; your HR, IT or facilities teams handle them within committed times, with a knowledge base, AI assistance and satisfaction tracking.

Public portal, no account needed Times in business hours Queue as a list or Kanban Knowledge base and AI

Employees · Candidates · Customers · Suppliers · Email per service · Website widget · Microsoft Teams · Mobile app · Service catalogue · Major incidents · API and webhooks

One request comes by email, another on Teams, a third in a hallway. Nobody knows where they stand.

Without a shared tool, every team makes up its own method: a shared mailbox, a spreadsheet, private messages. Requests get lost, response times go unmeasured and the same questions come back every week. The requester has no visibility, so they chase, and the queue grows.

No shared queue

Requests sit in personal mailboxes and chats. One person is away, and nobody knows what is still waiting for an answer.

No measured times

Nobody knows how long an answer takes, or which requests are late. Urgent cases surface when the requester chases.

No memory

Answers are written down nowhere. Each agent answers the same questions from memory, and every newcomer has to learn it all again.

The Illizeo solution

A help desk built into the HRIS, for all your services.

HR, IT, facilities, purchasing: each service has its own queue, agents and response times. Requests from employees and outside people arrive through the channel of their choice, and follow the same cycle until they are closed.

  • A numbered ticket for every request, tracked until it is closed
  • Employees and outside people, with no account needed for the latter
  • Employee space, public portal, email, widget, Teams and mobile app
  • A queue per service, as a list or a Kanban board
  • First response and resolution times in business hours
  • Internal notes, canned responses, merging duplicates, followers
  • Automations and macros, manager approval when needed
  • A knowledge base suggested before the request is sent
  • Satisfaction survey and reporting dashboard per service
0
account required from outside requesters

6
statuses, from submission to closure

4
priorities, each with its own times
6 ways in

A request becomes a ticket, whatever its channel.

Requesters write from wherever they are; the ticket lands in the right service’s queue, with its full history.

Employee space and app

A guided form per request type, with knowledge base articles suggested before sending.

Public portal

Candidates, customers or suppliers submit and follow their requests without an account, through a sign-in link sent by email. In your colours, on your domain.

Email per service

Each message creates a ticket, or adds to the one it replies to. Replies can be sent from your own Microsoft 365 address.

Widget for your website

A help button on your pages, shown only on the domains you allow.

Microsoft Teams

Submit and follow a request without leaving Teams. New tickets appear in the service team’s channel.

Service catalogue

Standard requests, such as a new hire, that trigger the tasks of several services in order.

Ticket lifecycle

6 statuses. Every step recorded in the ticket’s timeline.

Requester and agent read the same status, in the same words. Each change is dated and logged, with the resolution note when the agent gives one.

1
New
Ticket submitted
Acknowledgement sent
2
In progress
Agent assigned
Clock running
3
Waiting for the requester
Question asked
Clock paused
4
Waiting for a third party
Supplier, other team
Pause if the service chooses
5
Resolved
Resolution note
Satisfaction survey
6
Closed
Automatic closure
7 days by default

4 priorities: low · normal · high · critical. The requester can reopen a resolved ticket; time spent in “Resolved” does not count against the team.

Receive. Handle. Measure.

3 pillars for a service that answers on time.

The service’s rules do the sorting, agents focus on answers, and response times measure themselves.

1. Sort and assign

Each ticket lands in its service’s queue. Help desk rules sort it, assign it or reply to it, in the order you set.

  • Assignment to the service lead or the agent who takes it
  • Transfer from one service to another
  • Automations and macros
  • Manager approval before handling, when needed

2. Reply

A single thread with the requester, internal notes between agents and all the context on the ticket.

  • Canned responses and attachments
  • Internal notes, never seen by the requester
  • Merging duplicates, linking tickets
  • Followers and people in copy

3. Meet the deadlines

Commitments by priority, counted in business hours using the service’s schedule, time zone and public holidays.

  • First response and resolution
  • Reminder before the deadline
  • Escalation once the deadline is missed
  • Paused while waiting for the requester
Example: an IT request

An outage reported by email, resolved in 6 steps.

A typical scenario, with an IT service’s settings: first response within 1 business hour and resolution within 8 business hours for high priority.

Example · high priority · times met

Cannot reach the VPN · IT service

An employee on the road can no longer connect. They write to the IT service’s address. The ticket is created, AI suggests a triage, an agent replies with a canned response, then resolves it. The employee rates the service.

Service commitment: first response within 1 business hour · resolution within 8 business hours · clock paused while waiting

Timeline · 6 steps

1
9:12 am · Email received
Ticket AST-000142 created, acknowledgement sent
New
2
9:13 am · AI suggests a triage
IT service, high priority
New
3
9:31 am · Taken
Canned response: reset the access
In progress
4
9:40 am · Question to the employee
Resolution clock paused
Waiting
5
11:05 am · Resolved
Resolution note, survey sent
Resolved
6
7 days later · Closed
Automatic closure, rated 5 out of 5
Closed
Service quality

Response times, incidents, satisfaction: all measured.

Commitments, major incidents and requester feedback read in one place, by service, by agent and by period.

Commitments by priority and by contract

Each service sets its first response and resolution times by priority, in business hours. A customer under contract follows the grid of their service level. Times are fixed on submission: changing the policy never moves a deadline already announced.

Reminders and escalation

A reminder goes out once part of the time has elapsed, to the agent holding the ticket or to the service’s agents. Once the deadline is missed, the ticket is escalated to the service’s escalation group or its leads.

Major incidents and problems

When an outage affects many people, tickets are attached to an incident: a banner warns requesters, a single message informs them all, then the cause is tracked as a problem.

Satisfaction and reporting

On resolution, the requester rates the service from 1 to 5. A low rating alerts the leads. The dashboard tracks incoming tickets, median response times, times met and requests avoided thanks to the knowledge base, with an export.

Connected to the rest of Illizeo

A module of your HRIS, not one more tool.

The help desk builds on the employees, permissions, workflows and CRM already in Illizeo. Full documentation is in the help center.

Illizeo module

HR requests

Open requests move into the help desk, along with the history of closed ones. See the HR requests module.

Illizeo module

CRM

An external ticket links to the customer’s contact, account and contract, and the CRM record shows its tickets. See the CRM.

Illizeo module

Workflows

Help desk automations are Illizeo workflows: triggers, conditions, actions and approval circuit. See workflows.

Mobile

Illizeo app

Employees submit and follow their requests, agents handle their tickets, with notifications. See the mobile app.

Microsoft

Microsoft 365 and Teams

Emails can be sent from your Microsoft 365 support address. In Teams, people submit and follow requests, and each service has its channel.

Integrations

API and webhooks

Create tickets and reply to them from your tools through the public API, and receive every public event by webhook.

Knowledge base and AI

Fewer tickets, faster answers.

The knowledge base answers before a request is even sent; AI prepares the agent’s work, and the agent always reviews before sending. Requesters’ names and addresses are masked before anything is sent to the AI.

Knowledge base

Articles for employees only or published on the portal, with their versions and images.

Suggestions while typing

Useful articles appear as the request is written. Requests avoided this way are counted.

Reader feedback

Each reader says whether the article helped: you know what to rewrite.

Duplicates flagged

A request close to another open one from the same requester is flagged to the agent.

AI-suggested triage

On arrival, AI suggests the service and the priority. The agent confirms or corrects.

Suggested reply

Built from your articles and the answers the service has already sent, in the requester’s language.

Thread summary

To pick up a long or transferred ticket: where the request stands, what was done, what is left to do.

Suggested article

From a resolved ticket, AI drafts an article with no personal data. The editor reviews it before publishing.

A module that adds to your Illizeo subscription.

Billed per agent, meaning per person who handles tickets. Requesters, whether employees or outside people, are not billed.

Help desk module · billed per agent

All your requests, one tool

Internal and external tickets, six ways in, times in business hours, knowledge base, AI and reporting, in your HRIS.

Internal and external tickets
Public portal in your colours
Email address per service
Widget for your website
Submit and follow in Microsoft Teams
Service catalogue
Queue as a list or Kanban
Internal notes and canned responses
Merge, links, followers, copies
Automations and macros
Business-hour times, escalation
Major incidents and problems
Knowledge base
AI: triage, reply, summary, article
Satisfaction and reporting dashboard
Mobile app, API and webhooks
Request a quote

Frequently asked questions

What is a help desk?
A tool where every request becomes a ticket tracked until it is resolved: who raised it, who handles it, within what time and with what answer. Illizeo’s help desk serves HR, IT and facilities teams, and requests from outside the company.
How is it different from the HR requests module?
HR requests handles employees’ requests to HR. The help desk is open to every service and to outside people, with business-hour response times, a knowledge base, AI and reporting. Your HR requests can be moved into it.
Do external people need an account?
No. They submit their request on the public portal, by email or through your website’s widget, and follow their ticket through a sign-in link sent by email.
How are response times calculated?
In business hours, using the service’s schedule, time zone and public holidays. Each priority has its own first response and resolution time; a customer under contract follows the grid of their service level. The resolution clock stops while the ticket waits for the requester.
What happens to our HR requests?
They can be moved into the help desk: open requests are carried over automatically, and so is the history of closed ones.
How is AI used?
It suggests a triage on arrival, a reply, a thread summary or a draft article. The agent confirms every suggestion, and requesters’ names and addresses are masked before sending. Automatic triage on arrival can be turned off.
Does the help desk work on mobile?
Yes. Employees submit and follow their requests in the Illizeo app, and agents handle their tickets there, with notifications.
How is the help desk billed?
Per agent, meaning per person who handles tickets. Requesters are not billed. For a quote, book a meeting with our team.

All your requests, one tool, deadlines met.

Internal and external tickets, business-hour response times, knowledge base and AI, in your HRIS. Let’s talk about your services and your requests.

Book a meeting
Hosted in Switzerland
GDPR · Swiss FADP
Built into your HRIS