Service Desk

Every request has a number, an owner and a due time.

Staff ask IT, HR, finance or the office through one portal. The request lands in the department's queue, someone takes it, and the reporter knows where it stands without chasing anyone.

The department queue of the Service Desk: open requests with their number, status, priority, assignee and due time.
Screens of the real system on made-up data.

How it goes today

Requests travel by e-mail, chat and the corridor

  • A request sent to one person waits while that person is on leave.
  • Nobody can say what is waiting, what is late and who has it.
  • The same questions come back every time: which laptop, which room, which cost centre.
  • After a month nobody remembers who agreed to what and when.

The Service Desk puts every request in one place, in the queue of the department that handles it, with a due time counted from its priority.

From asking to done

One path for every request

The same four steps whether it is a new monitor, a certificate from HR or a refund from finance.

  1. File

    The employee picks a tile on the portal, answers its questions and sends. The request gets a number like IT-2026-00042.

  2. Queue

    It lands in the department's queue with a priority and a due time: 168, 72, 24 or 4 hours.

  3. Work

    An agent takes it or the lead assigns it. Questions, files and status changes stay on the request.

  4. Done

    Resolved or rejected with a reason. The reporter gets an e-mail at every important step.

The portal

Staff pick what they need, not whom to write to

Tiles grouped by category, with a search. Each tile asks only what the department needs to act.

  • Questions of seven kinds: text, number, date, a choice from a list and more
  • An incident's priority computed from impact and urgency
  • Answers stored with the request and never changed afterwards
  • "My requests" shows the employee where each of theirs stands
  • The portal can have an address of its own, e.g. desk.yourcompany
The Service Desk portal: tiles of request types grouped by category, with a search field.
The portal: an employee picks a request type instead of writing an e-mail.

The department's queue

One queue per department, sorted by what is due

The department sees everything filed to it - what is free, what is late, who works on what.

  • Filters for status, priority, unassigned and overdue, kept in the address
  • Search by number or title
  • "Take it" in one click, or the lead assigns to anyone in the department
  • A request filed to the wrong department is transferred and keeps its number
The department queue: a table of requests with status, priority, reporter, assignee and due time, overdue ones in red.
The IT queue: open requests, their priority and how much time is left.

My tasks

Everybody sees what is theirs - from any screen

Counters in the top bar tell an agent what needs them now, wherever they are in the system.

  • Overdue requests assigned to me
  • Requests due within 12 hours
  • Unassigned requests in my departments' queues
  • One click on a counter opens exactly that list
The list of my requests with the counters of overdue, due soon and unassigned requests in the top bar.
My requests, with the counters in the top bar.

The request

The conversation, the files and the history in one place

Everything about a request is on the request - not in someone's inbox.

  • Comments in Markdown; a private one is seen only by its author and the reporter
  • Attachments, web links and related requests
  • Status: new, in progress, waiting for information, resolved, rejected, closed
  • A rejection always comes with a reason
  • The history of every change, with names as they were at the time
A request in the Service Desk: the description, comments and the box for a new comment.
A request with its conversation and details.
The history tab of a request: every change with its date and author.
The history: who changed what and when.

Your departments, your request types

Set up without a developer

Departments come from your org chart; IT and the administrator set up the portal themselves.

  • A starter kit of departments, request types and portal tiles from the first day
  • Your own request types, tiles, questions and options
  • Nothing is deleted - only switched off, so old requests keep their meaning
  • The company's important links in one place, and per-department links as an add-on
  • Branches as an add-on: a field on the request and a filter in the queue
The Service Desk configuration: departments, request types and portal tiles.
The configuration: request types and portal tiles.

The report

See whether the queues keep up

How many requests came in, how many were resolved, rejected or closed, and what waits now - per department.

  • Requests per month and per department
  • What is open and overdue right now
  • The daily series on the dashboard
The Service Desk report: requests filed, resolved and closed per department.
The report: filed, resolved and waiting, per department.

Who uses it

Not just IT

IT

Equipment, accounts and access, broken printers and phishing reports - with the incident's priority set by impact and urgency.

HR

Certificates, leave balance questions, onboarding of a new person - without HR's phone ringing all day.

Finance

Expense questions, invoice corrections, cost centres - every answer on record for the audit.

Office and administration

Keys, parking, business cards, supplies - small things that used to get lost in chat.

Said plainly

What it does not do yet

We would rather you knew before the demo than after it.

  • No e-mail to request: a request is filed on the portal or in the panel, not by writing to an address.
  • No confidential requests visible only to selected people.
  • No due times per request type or approval paths - the due time follows the priority.
  • No filing on somebody else's behalf, no mentions and no subtasks.

Questions

Before you ask

Do we have to have an org chart?

The departments are units of your org chart with a code (IT, HR, FIN...). The starter kit creates the usual ones, and you can add your own. A code is set once and never changes, so request numbers stay valid.

Does every employee need an account?

Yes - a request is filed by a signed-in person, so the department knows who asks and the reporter sees the answer. The portal is simple enough for people who use nothing else in the system.

Who gets e-mails?

The reporter, when the request is filed and when it waits for information, is resolved or rejected; the assignee, when a request is given to them; and both about new comments - never the comment's own author. The texts come from the module's settings.

How long does it take to start?

The starter kit gives departments, request types and portal tiles from the first day. Adjusting the tiles to your company takes an afternoon, without a developer.

See it working on real screens

The demo has a company with a living Service Desk: file a request, take it from the queue and resolve it.