Kontext Encyclopedia

Help Desk

/helpdesk · version 3.54 · 2026-11-19

Capabilities

Help Desk (/helpdesk) is Kontext's support desk for people who use the platform. You file a ticket, and the Kontext team answers it in a thread. This screen is Kontext's help for you. Your own customers use your Support Desk (below), which is a separate, owner-run desk on the same screen. Guests cannot file; you need to be signed in with a workspace. The OS dock does not show Help Desk; open it from the module switcher or /helpdesk.

What is Help Desk?

The screen opens on the title bar Help Desk with New ticket on the right. Below it: four counts (Total tickets, Open, In progress, Resolved; pressing one filters the list to that status), tabs Issues, Feature requests, Assistance and Analytics, a search box (subject, description or tag), status and priority filters, and tag chips. Tickets show as cards; the coloured edge of a card is its priority (red critical, orange high, amber medium, grey low).

A ticket is stored in the workspace of the person who raised it. Kontext staff read it from there.

Filing a ticket

New ticket opens a form. Pick the Type (Issue, Feature or Assistance; it starts on the tab you were on), then subject and description (both required), category, priority and tags. After it is created, open it to add files.

Inside a ticket

Status, priority, type, category and assignee sit under the subject. Copy link copies /helpdesk?ticket=<number>&uc=<workspace>. Then the description, the Updates thread and the comment box (type @ to mention someone, Attach file to add a file). If a ticket's workspace has not taken the latest update, the screen says That workspace needs its update to show the full thread rather than showing an empty thread.

The person who raised a ticket can edit it, comment, attach files, watch it, mark it Resolved or Closed, Reopen it, and delete it.

Kontext staff (admins and the Kontext team)

Staff see All tickets / My tickets (with All of my tickets, Created by me, Assigned to me). On a ticket they can Assign it (search by handle; the person is notified), set any status, post an Internal note that only staff see, track time (Start timer / Stop timer, Add manual time), and Create Projects task from the ticket. A ticket with a task shows Linked task #N and Open Projects. The person a ticket is assigned to can work it the same way, including from a notification link.

Analytics counts the tickets loaded on the screen with the current filters (it says so): status counts, priority distribution and the top categories. It is not a report over every ticket, and there are no response-time or resolution-time averages.

Not in Help Desk: response templates, SLAs or SLA clocks, attachments on the create form, and searching by ticket number.

Docs, Forum, Talk, ticket

Talk (/os) is where you reach Kontext: an answer, a guide page, or an action on your account. Talk can file a Help Desk ticket from a message menu; that ticket lands here. Documentation (/documentation) is the product book Talk looks up. Kontext Docs (/docs) is for making a document. Forum (/forum) is public threads. Messenger (/messages) is people. Say which one you mean rather than "open Help".

Support Desk (your own customers). On the Pro plan your Help Desk screen has a Your Support Desk tab. Your customers file requests at kontext.network/support/ followed by your handle (it can also be embedded in an app), strangers included. Only you and your team can read them; Kontext staff cannot. Replies are public by default and emailed from your business's own sender; a Private note is for your team. A request is matched to a contact by email, or creates a new lead marked as coming from support. A Business employee with the Support desk assistant focus can draft replies, as private notes you approve. The public form stays closed until you turn it on. Several parts are live but have not been tried end to end with a real customer ticket, and SMS replies from the desk are not built.

User journeys

HD-01. File a ticket

Path: Module switcher → Help Desk (or /helpdesk) → New ticket

You do:

  1. Sign in to Kontext and open /helpdesk.
  2. Press New ticket.
  3. Pick the Type: Issue, Feature or Assistance.
  4. Enter a subject and a description of what happened and what you expected.
  5. Choose a category and a priority, and add tags if they help.
  6. Press Create ticket.

Result: The ticket is created as Open with a number, and appears under the tab for its type.

HD-02. Follow your tickets

Path: /helpdesk

You do:

  1. Open /helpdesk. The list shows Open tickets of the current tab.
  2. Press a count, or use the status filter, to see In progress, Resolved, Closed or All statuses.
  3. Search by subject, description or tag, or press a tag chip.
  4. Press a card to open the ticket and read its thread.

Result: You can see where each request stands.

HD-03. Reply and add files

Path: /helpdesk → a ticket

You do:

  1. Open the ticket.
  2. Type in Add comment; type @ and pick a handle to mention someone.
  3. Press Attach file to add a screenshot or log (large files upload in pieces, with a percentage).
  4. Press Add comment.

Result: Your comment joins the thread; mentioned people are notified. Files are listed on the ticket and can be downloaded.

HD-04. Resolve, close or reopen

Path: /helpdesk → a ticket → Update status / Reopen

You do:

  1. Open the ticket.
  2. Press Update status and pick Resolved or Closed (the change applies straight away).
  3. If the problem returns, open the ticket and press Reopen.

Result: The ticket keeps its number and its whole thread.

HD-05. Share or open one ticket by link

Path: a ticket → Copy link

You do:

  1. Open the ticket and press Copy link.
  2. Paste it where it is needed. Notifications about a ticket use the same link.

Result: Anyone who may see the ticket opens it directly. Anyone else sees that it could not be opened.

HD-06. Work the queue (Kontext staff)

Path: /helpdesk as an admin or Kontext team member

You do:

  1. Choose All tickets or My tickets.
  2. Open a ticket and press Assign to give it to yourself or a teammate.
  3. Set In progress or Waiting for customer with Update status.
  4. Reply in the thread; tick Internal note for a note only staff see.
  5. Track time with Start timer / Stop timer or Add manual time.
  6. Press Create Projects task to turn the ticket into a task in a project.
  7. Mark it Resolved when it is fixed.

Result: The person who raised it sees every public reply; internal notes stay with staff.

HD-07. Open your support page to customers

Path: Help Desk → Your Support Desk · /helpdesk

You do:

  1. Make sure you are on the Pro plan.
  2. Turn on the public form.
  3. Share kontext.network/support/@yourhandle, or embed it in your app.

Result: Customers file requests with a spam check. Each request lands in your desk. If your plan lapses, intake closes with a message and your data is kept.

HD-08. Answer a customer request

Path: Help Desk → Your Support Desk

You do:

  1. Open a request and write a reply.
  2. Leave it public to email the customer from your business sender, or tick Private note for your team only.

Result: The screen says whether the email went. Customer replies show as "name (customer)". The request also appears on the contact's timeline in Business.

HD-09. Let an employee draft replies

Path: Business → Employees → template Support desk assistant

You do:

  1. Create the employee with the Support desk assistant focus.
  2. Review the drafts, which are private notes, and send the ones you approve.

Result: It drafts replies to requests waiting on you, at most five per run. Nothing is sent without your approval.

How it works

A ticket and its thread live in the requester's workspace (user canister). The platform canister keeps an index of tickets, which is what the staff list reads. Opening a ticket asks the ticket's own workspace for the ticket and its thread in one read (staffTicketView); a workspace on an older version answers with the older reads and the screen says so.

Benefits

Who it's for

Everyone signed in with a workspace: file and follow tickets. Kontext staff (admins and team): work the queue.