← Helpdesk

Helpdesk · Request types & forms

Ask the right questions, and finish the job properly

Request types turn “I need something” into a short form that says what happens next. Behind them, one list of categories and sub-categories, custom fields per team, reusable checklists and Before you solve rules keep every ticket complete.

Get started Read the docs

Before you solve asks only for what’s missing, in one dialog.

The problem

Messy data in, messy reports out.

× “VPN”, “vpn” and “Remote access” as three categories in one report.

× Every team needs a field the tool doesn’t have.

× Tickets closed with steps skipped and no root cause recorded.

→ Shared lists, your own fields and a finish line every ticket has to cross.

What it does

Structure, without the overhead.

Request types and forms

Each type has a form that says what happens next, names the approver from the directory and prefills answers. It can start a workflow, add checklists, or put the request on the calendar.

Categories and sub-categories

One managed list: add, rename, reorder, archive, merge and delete. A rename or merge updates tickets, request types, automations, saved views and report filters. Nothing invents a category.

Custom fields

Short text, long text, pick one, yes / no, date, date and time, number or a person, per team or for all teams. Mark each Agent only or Public; public fields show read-only to the requester.

Checklists

Reusable steps with required items, an owner team and due dates in business days. Add one by hand, or have a request type or workflow task add it. Requesters never see them.

Before you solve

Say what a ticket needs before it can be solved: an owner, a category, a linked asset, time logged, a reply sent, and closing fields such as a resolution code or root cause.

The same rule everywhere

Solve, the e key, macros, bulk edits, the API, automations and the Claude connector all meet the same requirements. Answers show on the ticket as Solve details.

How it works

Set the shape once, keep it everywhere.

All under Desk settings → Forms and fields.

Build the lists

Categories and sub-categories, and the custom fields each team needs.

Write request types

A form per kind of request, with its workflow, checklists and calendar setting.

Add checklists

The steps routine jobs must follow, with the required ones marked.

Set Before you solve

Per team or request type: what must be on a ticket, and the closing fields agents fill in.

Frequently asked

Can Claude change my categories or checklists?

It can draft them. Category changes and checklists from Claude wait as drafts until someone with the right to manage them publishes or discards them; Claude never deletes or merges a category.

Do custom fields work in filters and the API?

Yes. Filter the queue and saved views by any custom field, export them as CSV columns, and read or set them through the REST API, webhooks and the Claude connector.

Related: Workflows & approvals · Reports & export · Automations & macros · Event calendar · Docs

More in the helpdesk

A helpdesk without another tool to buy

Self-host CompassDocs with one Docker command. The helpdesk is part of CompassDocs Enterprise, with 3 agents included (extra agents $125/year each), alongside SSO, SCIM, directory sync, read confirmations and training.

Buying for a team? Get a formal quote to print for approval, or order by invoice with your PO number.