Ticketing

Email-to-ticket intake

A mailbox is polled automatically, and new messages become tickets; replies thread onto the right existing ticket instead of spawning duplicates.

Inbound email addresses can route to specific ticket categories, and mailbox connections are test-checked from the settings screen.

Public ticket submission form

Customers can open a ticket with no login, no account required.

Every ticket email carries a signed, permanent link a customer can open to see status and history without logging in.

Custom, tenant-defined statuses, priorities, and categories

Not a fixed list — configure the workflow that matches how your team actually works.

SLA policies

Response and resolution targets, calculated against real configurable business hours, with automatic breach detection.

Reusable ticket templates for common request types.

Per-ticket checklists, billable time entries, and file attachments — including anything attached to the original email.

Internal notes vs. public replies

Technicians collaborate on a ticket without the customer ever seeing it.

Contact auto-matching on new tickets, plus one-click quick actions like close and reassign.

Bulk delete across the ticket list.

Saved custom views

Filter by any combination of status, priority, category, or assignment, save it with a name, mark one as your personal default, and optionally share it with the whole team.

Full ticket activity history, plus a ticket-creation endpoint for API access.