Business

Every issue, tracked to resolved.

Tickets with priority, department and an SLA target, a knowledge base for the answers you give every week, and returns handled from the same desk.

A customer raises an issue — by email, from KardoSpace, or at the counter. It becomes a ticket with an owner and a clock. Quick replies handle the common ones, the knowledge base answers the rest before they are asked, and a return is a ticket with a parcel attached.

Get started All of Business
  • Tickets with priority, owner and SLA
  • Quick replies and a knowledge base
  • Returns and RMA from the same desk

The helpdesk home

What is open, what is breaching, and who has nothing assigned.

Open tickets

Everything unresolved, with the oldest and the most urgent at the top.

SLA breached

Tickets past their target hours, before the customer tells you.

Unassigned

Raised but not owned. The list that should be empty.

Queues

By department, so billing sees billing and the workshop sees the workshop.

Everything inside Helpdesk

Start with tickets. Add departments, SLAs and the knowledge base as the volume grows.

Tickets

Subject, description, customer, priority. Photos and video attached where the words are not enough.

Priority

Urgent, high, normal, low. The queue sorts on it, and the SLA clock runs faster for the urgent ones.

Departments

What each department handles, and an inbound email address per department so the ticket lands in the right queue.

Routing and SLA

An SLA target in hours to resolve, per department or per priority. Breaches are flagged, not discovered.

Public and internal

A reply the customer sees, or an internal note only your team reads. Both on the same thread.

Quick replies

Macros for the answers you give every week. Use one as the reply, then edit the specifics.

Knowledge base

Articles, public or internal. The public ones answer the question before a ticket is raised.

Tags

Label tickets by what they are about, so the recurring problem is visible as a count, not a feeling.

From KardoSpace

Requests customers raise from the app arrive as tickets, with the customer already attached.

Returns and RMA

A return is a ticket with a parcel. Track it back, restock or write off, and refund or credit from the same record.

Assign and resolve

Pick an owner, work it, mark it resolved with a note. The customer is told.

The org chart

Open the team from the desk to see who is in which department and who is free.

Raised to resolved

A ticket in three moves.

A ticket queue panel with priority flags, a headset, a knowledge-base panel and an SLA timer chip.
  1. It arrives. By email, from KardoSpace or typed at the desk. It lands in a department queue with a priority and an SLA clock.
  2. Someone owns it. Assigned, replied to with a quick reply or a full one, with internal notes the customer never sees.
  3. It is resolved. Marked resolved with a note. If it was a return, the parcel, the restock and the refund are on the same record.

Where the work happens

Three of the places you will spend time in Helpdesk.

An open ticket card with a priority flag, an assignee avatar and reply chips
The ticket — priority, owner, replies
A shelf of article cards with a search bar and a public or internal toggle
The knowledge base
A parcel with a return arrow, an RMA card and a resolved tick
Returns and RMA

Works with

Around the desk.

ContactsThe customer on the ticket SalesThe order a return refunds InventoryWhere a returned item goes back HRThe departments and the people in them

Free to start. Friendly to scale.

Start with what you need today and switch the rest on when you grow.

Get Started