Helpdesk · 1st / 2nd / 3rd line support
Helpdesk system for business — every request has an owner
Debesis helpdesk software turns email, calls and forms into cases with an owner, priority, status and SLA deadline. It covers first, second and third-line support in one interface, with a customer portal and KPI reports. Requests can also be classified automatically — AI sets the category and priority as soon as they arrive.
We send your login the same day. An empty account for 7 days, no credit card.
Requests · first-line support queue
| No. | Subject | Status | To SLA |
|---|---|---|---|
| #4471 | Missing item in order 24187 | In progress | 0:42 |
| #4492 | I cannot sign in | New | 3:18 |
| #4468 | Request for a corrected invoice | Waiting | 6:05 |
| #4455 | Device complaint — second line | Escalation | −0:12 |
of requests were closed within the SLA deadline — in a dataset of 3.72 million requests from ten live deployments.
Problem
An inbox does not track deadlines
With a dozen requests a day, a shared inbox is enough. With several hundred it breaks down — and usually not because the team is doing worse.
A message in an inbox has no owner. Two people answer the same request — or nobody does, because each thinks the other will. There is no deadline either: a three-day-old case looks like one from three hours ago until someone scrolls through the list.
The contact history is scattered. The customer called on Monday and wrote on Wednesday; whoever handles Wednesday’s message knows nothing about Monday’s call and asks the same question again.
The manager has nothing to report on. They do not know how many cases are waiting, which are overdue or who is overloaded — an inbox measures nothing but unread messages.
How it works
From the customer’s message to a resolved case
A helpdesk system turns a message into a numbered request and takes it through a defined process. Eight steps that happen in Debesis for every case.
- The customer emails, calls or fills in a form in the portal.
- Debesis creates a request with a unique number and saves the content.
- The system recognises the customer and fetches their data from connected systems.
- It sets the category and priority according to the rules for that case type.
- It routes the request to the right queue or straight to an agent.
- It starts the SLA clock and tracks first-response and resolution deadlines.
- The agent replies with the customer’s full contact history in view.
- The case is closed and its times feed into reporting.
Inbound channels
Case handling
Queue, owner, status, priority
Every request in a helpdesk system has four things a message in an inbox lacks: a number, an owner, a status and a deadline. The rest of the team’s work is organised around these four.
Automatic assignment
Rules route the case by request type, customer, channel or content. Agents do not pick requests from a list — they get the ones they are responsible for.
Priorities and categories
The team sees what to do first without reading the whole queue. Priority can depend on the customer, the case type or the time left.
Owner and status
It is clear who owns the case and how far along it is. A handover to second line leaves a trail instead of disappearing in a forwarded email.
Full history
Email, phone, SMS and agent actions stay on one request. Whoever takes over next does not need to ask what happened before.
Requests · first-line support queue
| No. | Subject | Customer | Owner | Status | To SLA |
|---|---|---|---|---|---|
| #4471 | Missing item in order 24187 | Emma de Jong | Sanne de Boer | In progress | 0:42 |
| #4492 | I cannot sign in | Groen Handel B.V. | Jan Visser | New | 3:18 |
| #4468 | Request for a corrected invoice | Oost Groothandel B.V. | Lotte Bakker | Waiting | 6:05 |
| #4455 | Device complaint — second line | Patisserie Malva | Jan Visser | Escalation | −0:12 |
| #4450 | Change of delivery address | Bakery Dageraad | Sanne de Boer | In progress | 11:47 |
SLA
SLA under control before the customer chases
An SLA in a helpdesk system is the agreed time within which the team must respond to and resolve a request. Debesis counts that time from the first second and acts before the deadline passes — not after.
Time to first response and to resolution
Two separate clocks on every request, visible in the case and in the list. The order of work follows the deadlines, not the arrival date.
Alerts before the deadline
The alert comes before the deadline passes. An approaching deadline raises the priority and moves the request to the top of the queue.
Escalation path
If the case stalls, it moves up a level — to second line or to the manager. The rule sets after how long and to whom.
of requests were closed within the SLA deadline. In the dataset, 3,636,833 cases were closed before the deadline and 69,246 after.
Debesis Report 2026 — analysis of 3.72 million requests from ten deployments (PL) ›
In the same dataset, the median time to first response was under two hours in nine of the twelve periods analysed. In the last two it was higher — because of one project with complex complaints that require consultation with the manufacturer. That is a feature of the process, not a delay by the team; we show the figure with the explanation instead of leaving it out.
Request #4471 · SLA first response 4 h
Automation
Rules that take over what is done by hand today
Helpdesk automation is a set of rules applied to every request: assignment, status changes, notifications and closing cases that need no reply. The rules always run the same way, however busy the team is.
Assignment rules
Case type, customer, channel and keywords decide which queue and person the request goes to.
Reply templates and knowledge base
Recurring replies with one click, with customer data and case number filled in.
Statuses and notifications
A status change sends a message to the customer and adds an entry to the history. Nobody has to remember to keep the customer informed.
of closures are carried out by automation. In the dataset the system performed 2,352,204 of 3,878,653 closures and agents the remaining 1,526,449.
Debesis Report 2026 — analysis of 3.72 million requests from ten deployments (PL) ›
How much of the work can automation take over?
In our analysis of 3.7 million requests from ten Debesis deployments, the system performed 60.6% of closures. The share does not grow indefinitely: it starts at 65–72% in the first months and settles at around 52–59%. The reason is not falling effectiveness but a changing mix of cases — the system takes the simple, recurring ones and agents keep those that need a decision.
Does automation come at the cost of quality?
The most common objection to automatic closing is that the system closes requests it has not solved and the customer comes back. In the dataset 87,834 requests were reopened, i.e. 2.4% of those closed — with sixty per cent closed automatically. Of every hundred closed cases, just under two and a half come back.
Channels
Four channels, one case
Channels cost different amounts, so routing them into one shared inbox is not enough. In ten high-volume deployments, 92.5% of requests came by email and 6.3% by phone — while the phone produced over 1.5 million calls. It brings few cases but costs a lot of time; so you automate email and organise the phone with queues and call-backs.
A message in the support inbox becomes a numbered request. Replies and attachments stay in the case history, not in a personal inbox.
…and lands in the same casePhone
The call is saved and linked to the customer with a recording and note. Even a missed call leaves an entry for a call-back.
…and lands in the same caseSMS
Inbound and outbound messages in one thread. Status updates go out automatically.
…and lands in the same caseForm and portal
The case type chosen by the customer sets the priority and routes the request to the right team without human intervention.
…and lands in the same caseof requests arrive by email. The phone accounts for 6.3% of cases but over 1.5 million calls in the period analysed.
Debesis Report 2026 — analysis of 3.72 million requests from ten deployments (PL) ›
Customer 360
Agents do not ask what the company already knows
The case shows not just the message but everything the company holds about this customer in other systems. Agents do not switch applications or ask for data they already have.
- Customer and company data — who is asking, from which organisation and on what terms they are served.
- Contact history — calls, emails and SMS in one timeline, whatever the channel.
- CRM data — the relationship status and the responsible person in the company.
- E-commerce orders — what the customer bought, when and at what price.
- Courier shipment status — fetched automatically and visible in the case.
- Earlier requests — what they were about and how they were resolved, so the same problem is not investigated twice.
- Call recordings — playable right in the case, with the agent’s note.
In practice
A customer writes that their device is not working. The agent sees the order number, purchase date and two earlier requests from this customer with their resolution — before writing the first sentence.
Request #4471
Missing item in order 24187
Hello, an item is missing from order 24187. I would like to know what happens next.
Customer view
Customer portal
Customers check the status themselves instead of calling
The customer portal is the part of the helpdesk that requesters use: they create cases, follow progress and reply without contacting an agent. Every status question customers answer themselves costs the team no time.
Submit and view requests
The customer submits a request with a category and sees its number, status, deadline and all correspondence in one place.
Knowledge base and self-service
Answers to recurring questions without creating a case. Some requests never arise because the customer finds the solution first.
Integrations
Data from the systems you already use
Debesis replaces neither your CRM nor your store. It fetches data from them and shows it to the agent when needed — in the case, not in a separate tab.
Salesforce
Customer data and relationship history from the CRM load into the case.
If you use a system that is not on the list, we build the connection via the API — both ways, so Debesis can fetch and pass on data. That is the difference between a platform you have to adapt to and a system that adapts to your environment. See all integrations →
Reports and KPIs
What management wants to see on Monday morning
Helpdesk reports answer three questions: how many cases are waiting, how fast the team responds and whether it meets deadlines. All figures come from actual traffic in the system, not from a spreadsheet kept by hand.
Operational metrics
Time to first response, resolution time, open and closed cases, backlog and workload per agent.
SLA compliance
Deadline compliance by queue and channel, with the list of overdue cases and the reason for the delay.
average handling time in team working hours versus calendar time including nights and weekends. The customer waits more than twice as long as the team works on their case.
Debesis Report 2026 — analysis of 3.72 million requests from ten deployments (PL) ›
This difference only becomes visible when the system measures both times separately. Otherwise the team judges itself by its working pace and the customer by the calendar — and both are right.
Reports · last 30 days · test data
How it works in practice
Two everyday situations for first and second line
On the left, the helpdesk view; on the right, what the requester receives at the same time. Click a scenario to play it.
—
Form
—
Case summary —
—
—
—
—
Fault report — service form
Calls
| Status | Number | IVR choice | Wait time | Time |
|---|
—
Subject: —
Active requests
| Status | Number | Title | Created |
|---|
Request details
History
—
——
Customers
— Email addresses —Who answers
What the customer sees
—
Evidence
Numbers from projects, not promises
requests analysed
of closures carried out by automation
of requests closed within the SLA deadline
of closed cases were reopened
Ten high-volume live deployments, twelve months of operation. The full methodology is in the Debesis Report 2026 (PL).
requests closed automatically — about 80% of all cases. 43% of replies went out within 15 minutes.
Sellpoint · e-commerce helpdesk (Poland)
Read the case study →service requests handled in the first three months after go-live, with no downtime and no lost messages.
Dedra-Exim · after-sales service (Poland)
Read the case study →of cases handled within an hour; over 70% of messages close automatically without an agent.
Schronisko Bukowina · ticketing and telephony (Poland)
Read the case study →Terms
Helpdesk, service desk and helpdesk software — how they differ
Three terms often used interchangeably although they mean different things: a function in the company, its extended scope and the tool you run it in.
Helpdesk
The point of contact for problem reports — from customers or staff. It takes the case, resolves it and informs the requester. The scope is narrow and reactive: something does not work, someone fixes it.
Service desk
The broader approach that besides problem solving also covers service requests, changes, access and asset management. The service desk includes the helpdesk and adds processes.
Helpdesk software
The tool in which both run: it captures requests, assigns owners, tracks deadlines and reports results. Debesis belongs in this category and covers both — the narrower helpdesk and the broader service desk.
Rollout and security
Rollout around your process, hosting in Poland
You do not get an empty interface and a manual. We start with how your support works today and set up queues, rules and deadlines around that process.
Vendor
The system is developed in Poland and billed in euro. The people who develop the product work in the same time zone as your team — no support window on another continent.
Hosting in Poland
Hosting and databases are in Poland, within the EEA, under the GDPR, with backups, role-based access control and logging. AI features are processed in the EU. Details for your IT team are on the GDPR page.
Support directly from the vendor
Set-up is done by the Debesis team, not a reseller. After go-live you change queues, rules and templates yourself or ask us — without a paid consultant for every tweak. Support is in English and Polish.
Integrations that fit your environment
Instead of a list of ready-made add-ons: a connection to the systems you actually use, via the API and tailored to your process.
Questions and answers about the helpdesk system
Is a helpdesk system suitable for a small company?
Is it a SaaS ticketing system?
Can the helpdesk connect to other systems?
Does it support SLAs and escalations?
What do helpdesk reports and KPIs look like?
Is the helpdesk GDPR-compliant and secure?
How does the service desk differ from the helpdesk in Debesis?
Does Debesis support ITIL processes?
Let’s talk about your support process
We show the system on your case — on the channels you use and the requests you actually receive.
Platform
Debesis can also
The helpdesk is one of the platform modules. Start with what you need now and add the rest later.
Helpdesk in your industry: E-commerce · Healthcare · Field service
Next step
Let’s look at your support process live
We show the system on your case — on the channels you actually use and the requests you actually receive. The demo takes fifteen minutes and needs no preparation on your side.
In the meeting
We walk through one of your cases from first contact to closure and show what the agent sees, what the customer receives and what stays in the system afterwards. No slides.