Service desk overview

Run support on one queue — boards, email-to-ticket, SLAs, time tracking, and automations — so every request gets tracked and answered.

Updated 2 min read

The Service Desk (Tickets) module turns every customer request into a tracked ticket on a shared queue. Tickets can come in by email or be created by your team, and each one carries its full conversation, tasks, time, and history in one place — so nothing slips, and anyone can pick up where a colleague left off.

The ticket queue

Tickets is a toggleable module; an administrator turns it on under System → Features.

Boards are your queues#

The top organizing unit is the board — think of a board as a queue for a particular kind of work: Support, Website Requests, IT Helpdesk. Each board has its own:

  • statuses, priorities, types, tags, and sources,
  • mailbox and forwarding address (so it can receive and send email as itself),
  • customer emails, automations, and happiness survey,
  • and access list.

You can have as many boards as you need, and the ticket list can show one board or All Boards at once.

What's on a ticket#

A ticket has a number (like #0042), a subject, and a board, plus its status, priority, type, source, the company and contacts involved, an assignee, tags, and a due date. Its heart is the conversation — the back-and-forth with the customer, mixed with internal notes. See The ticket record.

The list#

Open Tickets for the list. The header shows quick tiles — Open, Unread, Overdue, Closed — and a board switcher, search, filters, and a New Ticket button. You can save views, sort, and run bulk actions. See Views & bulk actions.

If no boards exist yet, you're prompted to create your first one (administrators) or to ask an administrator to set one up.

What's in this section#

Bring your whole services business together

Stop stitching together five tools. Run sales, delivery, support, and billing from one organization — with an AI assistant on every page.