Pro free for 30 days.No card.Start free →

The question that does not get lost in someone’s inbox

A ticket with a status, a priority and an owner, sitting on the same list toolbar as every other module. Replies stay on the record instead of scattered across email threads.

Included from Pro upwards
Start free

Free for up to 5 users. Pro free for 30 days. No card.

See pricing

Why this exists

  • A support request arrives by email and quietly dies in one person’s personal inbox.
  • Nobody can say at a glance whether a ticket is open, being worked on, or simply forgotten.
  • A customer complaint and the reply that resolved it live in two different places within a week.

What it does

What it does

  1. 01Log a ticket in seconds

    A subject, an optional category (General, Bug, Feature Request, Billing, Access, Other), a priority and a description are all it takes to raise one.

  2. 02Track it through a real lifecycle

    Open, In progress, Waiting, Resolved and Closed, grouped and filterable on the same list toolbar, columns and CSV export every other module uses.

  3. 03Give control to the right person

    An owner or admin sets the status, priority and assignee from the ticket’s detail view. The person who raised it can close their own ticket at any time while it is open.

  4. 04Keep the conversation on the record

    Replies form a threaded conversation on the ticket itself, each one timestamped and attributed, visible to the requester and to staff.

  5. 05See what needs attention today

    KPI cards for Open, In progress, Resolved and Total sit above the list, with an attention bar that flags tickets still waiting on a first response.

  6. 06Let an AI agent help triage

    A support-domain agent can read the queue and propose replies or actions, approve-first: a person still clicks approve before anything is sent.

The honest part

What it does not do

The part you would otherwise find out in week three. If one of these is central to how you work, raise it before you buy rather than after.

Questions

Questions, answered

Who can see and reply to a ticket?

The ticket’s requester and any owner or admin. Admin controls (status, priority, assignee) are limited to owners and admins; the requester can only close their own ticket.

Does raising a ticket trigger an automation?

Not today. Ticket events are not yet part of the Automations trigger library, so you cannot wire a rule to fire the moment one is created or its status changes.

Can I limit who works the desk?

Yes. The standard Support Agent role template scopes a person to this page rather than the whole workspace.

Is there a public help centre customers log into?

No. Tickets are read and replied to from inside your workspace. There is no separate customer portal today.

The full product documentation for this module is at /docs/modules.

Try it on your own data

Every module is in the same workspace, so nothing needs connecting to anything.

Free for up to 5 users. Pro free for 30 days. No card.