Skip to content

Tickets

Shared inbox, forms and automations for customer requests.

Open Tickets
Checked against the dashboard on November 18, 2026

Tickets is the one desk of a workspace. Every request that reaches you lands in it: a form you publish, the profile contact form, your Public Assistant, the customer portal, the API, or a ticket you open yourself because someone phoned. They all get the same stages, topics and automation.

Each workspace has its own desk and its own plan.

Every ticket is about a real person

When a ticket is opened, the requester is saved as a contact against their email address, and the ticket also lands on their contact card. A ticket always sits next to the rest of that relationship.

Set up a desk

Pick a plan

Tickets opens on its plans until one is chosen. Free costs nothing and switches the desk on at once.

Add topics

Open Settings and go to Topics. A topic is what people write to you about, with sub topics under it. You can write them yourself with New topic, or let an AI draft a set with Suggest topics and keep the ones that fit.

A topic runs a workflow when a ticket arrives and again when its topic changes. Which workflow runs on a topic is set in Workflows.

Work the queue

Open a ticket from the page, answer it, and close it when it is done.

Work a ticket

Press a ticket's row, or its card on the board, to open the ticket window. The top says whose turn it is, and the clock beside it says how long the ticket has waited or when it is due. Under it is the conversation, and on the right are the facts about the ticket.

  • Reply or leave a note. The box writes either a reply to the customer or an internal note that only your team sees. A reply is emailed when the requester has an account.
  • Give it to someone. Open the Who has it fact and pick a person of the workspace team. They get a notification.
  • Change its priority, type or topic. Each is a fact on the right. Changing the topic can run that topic's workflow, and the window says so before you save.
  • Close it. Close ticket asks first, and says whether the requester gets a closing email. If the customer writes back within the reopen window, the ticket opens again.

When a ticket carries a request for a video call, the ticket window shows it. You can confirm the time, pick or propose other times from your free times, move a confirmed call or cancel it, and the customer is emailed each time.

Stages

A ticket is open or closed. While it is open it is also at one of four stages, which tell you whose turn it is.

Read the page

The Tickets page is the desk itself.

  • The say line tells you how many people are waiting on you and for how long. From 80 percent of the month's tickets it tells you how many are left instead, and when the count resets.
  • Switch between the grid and the board. The board has a lane for each stage, and dragging a ticket to a lane moves it.
  • Search the desk, and narrow it with Filters: by status, priority, type, assignee, topic, source, stage and more. Each filter becomes a chip you can change or remove.
  • Display sorts the tickets, chooses the grid's columns and exports the list to Excel.
  • Tick rows, and the foot of the page offers Set topic and Close for all of them at once. Closing asks first.
  • The page keeps itself current: it reads again every 40 seconds and when you come back to the window.

On the board, closing a ticket by dropping it on Closed waits a few seconds with an Undo before anything is sent, because the closing email cannot be called back.

Book tickets to people

The Dispatcher books the desk's open tickets to the people of a contact group, at a time. Each person is a column with their day and their busy times, and you drag a ticket onto a column. Make a dispatcher in its setup first.

What runs by itself

  • Workflows. A topic's workflow runs the moment a ticket arrives or its topic is set. It can hand the ticket to a person, set a due date, email the customer and put an AI agent on it.
  • AI agents. An agent on a ticket can draft a reply for a person to send, reply itself, or reply and mark the ticket resolved. It never closes a ticket. How far it may go is set for each ticket, and your plan decides the highest level.
  • Closing quiet tickets. The Closing tab holds a rule that warns the customer and then closes a ticket that went quiet after the desk answered. The rule closes tickets only while Xuda's closing run is switched on. While it is off the tab says Not running yet, and nothing closes by itself, so close quiet tickets by hand or from the selection bar.

Where next

How is this guide?

Last updated on November 18, 2026