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.
Employees · Candidates · Customers · Suppliers · Email per service · Website widget · Microsoft Teams · Mobile app · Service catalogue · Major incidents · API and webhooks
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.
Requests sit in personal mailboxes and chats. One person is away, and nobody knows what is still waiting for an answer.
Nobody knows how long an answer takes, or which requests are late. Urgent cases surface when the requester chases.
Answers are written down nowhere. Each agent answers the same questions from memory, and every newcomer has to learn it all again.
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.
Requesters write from wherever they are; the ticket lands in the right service’s queue, with its full history.
A guided form per request type, with knowledge base articles suggested before sending.
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.
Each message creates a ticket, or adds to the one it replies to. Replies can be sent from your own Microsoft 365 address.
A help button on your pages, shown only on the domains you allow.
Submit and follow a request without leaving Teams. New tickets appear in the service team’s channel.
Standard requests, such as a new hire, that trigger the tasks of several services in order.
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.
4 priorities: low · normal · high · critical. The requester can reopen a resolved ticket; time spent in “Resolved” does not count against the team.
The service’s rules do the sorting, agents focus on answers, and response times measure themselves.
Each ticket lands in its service’s queue. Help desk rules sort it, assign it or reply to it, in the order you set.
A single thread with the requester, internal notes between agents and all the context on the ticket.
Commitments by priority, counted in business hours using the service’s schedule, time zone and public holidays.
A typical scenario, with an IT service’s settings: first response within 1 business hour and resolution within 8 business hours for high priority.
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.
Commitments, major incidents and requester feedback read in one place, by service, by agent and by period.
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.
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.
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.
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.
The help desk builds on the employees, permissions, workflows and CRM already in Illizeo. Full documentation is in the help center.
Open requests move into the help desk, along with the history of closed ones. See the HR requests module.
An external ticket links to the customer’s contact, account and contract, and the CRM record shows its tickets. See the CRM.
Help desk automations are Illizeo workflows: triggers, conditions, actions and approval circuit. See workflows.
Employees submit and follow their requests, agents handle their tickets, with notifications. See the mobile app.
Emails can be sent from your Microsoft 365 support address. In Teams, people submit and follow requests, and each service has its channel.
Create tickets and reply to them from your tools through the public API, and receive every public event by webhook.
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.
Articles for employees only or published on the portal, with their versions and images.
Useful articles appear as the request is written. Requests avoided this way are counted.
Each reader says whether the article helped: you know what to rewrite.
A request close to another open one from the same requester is flagged to the agent.
On arrival, AI suggests the service and the priority. The agent confirms or corrects.
Built from your articles and the answers the service has already sent, in the requester’s language.
To pick up a long or transferred ticket: where the request stands, what was done, what is left to do.
From a resolved ticket, AI drafts an article with no personal data. The editor reviews it before publishing.
Billed per agent, meaning per person who handles tickets. Requesters, whether employees or outside people, are not billed.
Internal and external tickets, six ways in, times in business hours, knowledge base, AI and reporting, in your HRIS.
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