Tickets: the center of gravity, and what actually happens in there

If the workspace has a center of gravity, this is it. Tickets are where customer work lands, and every other module eventually hands something to them — a call, a chat, a form, an email. So let me walk you through what actually happens in here, including the parts teams usually discover three weeks in.

The shape of a ticket

A ticket carries a requester — which resolves to a real contact record, not a free-text email — a status, a priority, an assignee, and a timeline. The timeline is append-only: every state change writes an event, so "what happened to this one" is history you can read, not memory you reconstruct. The requester's other tickets sit on the same detail page, newest first, because the context you need is usually one glance away.

Getting it to the right person

Assignment can be manual or ruled. The rules run in three strategies: round-robin with a cursor that survives the team list changing, least-active for load balancing, and a skill filter when the pool needs specific hands. If a rule's candidate pool comes up empty, the ticket stays put rather than erroring into the void. An assignment pings the assignee. Above that, saved views are per-person filter presets — name them once, click them forever.

The clock

Priorities carry SLA targets, and they tier: a specific company's policy beats the org-wide default. Deadlines that would land outside business hours roll forward to the next open moment instead of firing at 3am. Change a ticket's priority later and the target re-resolves — the deadline follows the ticket, not whatever was stamped at creation. A breach isn't silent — side effects fire, notifications go out (there's a setting), and an optional escalation can flag the ticket for Tier 2. Snooze is the pressure valve: park a ticket as pending until a future moment, and the sweep wakes it back up.

The parts agents touch daily

Macros drop canned responses into the composer with the variables filled — customer name, ticket number, your own name — and an unknown placeholder survives visibly instead of vanishing into an empty string. Time tracking is manual entries with a running total on the side of the ticket; there's no auto-timer, deliberately. Need a teammate's eyes? @mention them in a comment and they'll get a notification — and you'll never get pinged by your own mention, because the author is exempt. Attachments ride the same storage seam as everything else in the workspace, size-capped and type-checked before they land on the timeline. And when another agent already has the ticket open, an amber "Also viewing" banner appears — advisory, never a lock.

Where tickets come from

Email is the big one. Inbound mail threads onto the existing ticket by message headers, idempotently — a replayed delivery doesn't duplicate anything — and your public replies go out through your own SMTP, with delivery recorded per comment so a failed send is visible, not assumed. Conversations from live chat and calls from voice arrive as tickets too, so the queue genuinely is everything. And when a new ticket looks familiar, I'll suggest a guided flow that has answered it before.

How this compares

Help desks are one of the oldest software categories there is. Zendesk is the incumbent; Freshdesk and Help Scout are respected, capable products — if you want a large, configurable help desk, they earned their reputations honestly. What a standalone desk doesn't share is the rest of your operation: the ticket's requester is a row in some CRM (or nowhere), the phone calls live in the phone system, the SLA clock has never heard of your business hours, and the knowledge base that should be answering tickets is a separate subscription.

Here the ticket is the spine everything already attaches to. The requester is a CRM contact — the same record your invoices bill and your appointments book. Chat and voice create tickets natively, so "omnichannel" isn't an integration you pay for. The SLA clock reads the org's own business-hours schedule. The knowledge base the bot quotes is the one your customers read. And I'm not a desk add-on — the assistant suggesting flows on tickets is the same one answering chats and summarizing tickets. One record, one clock, one assistant: most desks can't say that, because they're one tool among several.

Try it

Tickets is in the main sidebar — it's core, there's no toggle. Email your inbound address, watch it thread onto a ticket, let a rule assign it, snooze it until Thursday, and then read the timeline back. The boring parts are the good parts.