A product by

Customer support managed in one place

kDesk gathers customer requests into tidy tickets: emails come in on their own, you can see who is handling what and response times stay under control — no request lost in the inbox of someone on holiday.

Request a demo

Requests come from everywhere — and some slip through

Different mailboxes, forwards between colleagues, replies in CC: without a single place to collect requests, something always falls through the cracks and no one knows where things stand.

Without kDesk

  • Requests scattered across different mailboxes and manual forwards
  • No one knows who handles what, or where it stands
  • Fragmented history, lost or duplicated replies

With kDesk

  • Every request becomes a trackable ticket
  • Clear assignee, status and priority on every ticket
  • The full conversation history in one place

Support requests, handled the way they should be

kDesk turns support emails into tidy tickets: every request has a status, a priority and an owner, and the whole conversation with the customer stays in one place. The team takes tickets on, replies or leaves internal notes with @mentions and invites the colleagues who need to stay informed — no more requests lost between mailboxes.

From ticket to resolution, without losing the thread

Every request comes in as a ticket, gets assigned to the right person and follows its status through to closure — with the whole conversation in a single thread.

  1. 1 Open the ticket The request becomes a ticket with priority, category and history.
  2. 2 Assign and follow A colleague takes it on; anyone invited onto the ticket stays updated even without being assigned.
  3. 3 Resolve and archive The status moves through to Resolved and the conversation stays available.
A thread for every ticket All the correspondence in order, in one place.

Order underneath, your brand up front

Sort requests by category, set the right priority and invite onto the ticket whoever needs to stay informed. The request portal and the forms carry your company’s logo and colour.

  • Categories

    Technical, administrative, sales: every request in the right place.

  • Priorities

    Urgent, high, normal, low: you see what comes first at a glance.

  • Invited colleagues

    Whoever needs to stay informed gets updates, even without being the assignee.

Your company’s brand Your logo and colour on the request portal and forms, and a single sign-in across the whole Kamzan ecosystem.

Everything you need for customer support

  • Requests come in by themselves

    Connect your support mailboxes and every email becomes a ticket, with the client’s replies attached to the same thread. Receipt confirmation in 7 languages and public web forms.

  • Request area for clients

    A page with your branding where the client signs in with just their email and a code, sees where their requests stand, replies, opens new ones and leaves a rating. No password.

  • Working a ticket

    Every ticket has someone following it, a clear status and the whole exchange on one page: taking ownership, invited colleagues, internal notes with @mentions, replies with attachments.

  • Areas, mailboxes and categories

    Organise support the way your team works: areas that decide who sees which tickets, mailboxes tied to an organisation, multi-level categories, two user types with clear privileges.

  • Response times (SLA)

    Set how soon you reply and how soon you close, per priority too, counting working hours only. Every ticket is born with its deadlines and an outcome: Met or Missed.

  • Reminders, closure and satisfaction

    Personal and automatic reminders on stalled tickets, resolved tickets that close on their own, and one-click feedback from the customer, with a “Not resolved” button that reopens the request.

  • List, board and trends

    The same tickets seen four ways: a list with search and filters, a drag-and-drop board, a morning summary and trends over 7, 30 or 90 days. Plus actions on many tickets at once.

  • Customers, documents and senders

    A customer list that builds itself, a library of always up-to-date documents to attach, and recognition of who is writing, with AI giving a hint on unknown senders only if you have chosen it.

Frequently asked questions about kDesk

Does kDesk turn emails into tickets?

Yes: connect your support mailboxes over IMAP and SMTP and every email becomes a tracked ticket.

Can I assign tickets to the team?

Yes: an agent takes the ticket with “Assign to me”, or you reassign it to a colleague and add a co-assignee; anyone who just needs to stay informed can be invited onto the ticket.

Can I leave notes visible only to the team?

Yes: on each ticket you choose whether to reply to the customer by email or leave an internal note, visible only to agents.

Where is ticket data stored?

kDesk is part of the Kamzan ecosystem and runs on servers in Europe; you sign in with your single Kamzan account and each agent only sees the tickets of their own areas.