Loading
Every help desk has queues, macros and an SLA field. What differs is what an agent can see when they open a ticket, and how long it takes them to see it.
These features are arranged around that minute: who this is, what they are owed, what we are delivering for them, and what has already been tried.
Every entry below names the products it is joined to. Those joins are the specification, not a footnote.
Ownership decided before the first reply, with the customer, project and contract already on the ticket.
Driven by entitlement rather than goodwill, and visible to the account team before the customer has to chase.
What this customer actually bought, checked at the moment of the request rather than argued about afterwards.
Templates that pull real values from the record, so a fast reply is still an accurate one.
Volume, breaches and repeat causes visible to the people who sold and delivered the thing being asked about.
Public articles and internal answers, with the failed searches that show what is missing.
Draft replies for agents and answers for customers, both grounded in the account's own history, inside limits you set.
Catalogue, assets, incidents, problems and changes for teams running IT rather than a mailbox.
Routing gives a ticket an owner from the first minute. Entitlement decides the clock it runs against. The clock escalates before it breaches rather than after. And where the answer is not support's to give, escalation makes a real task rather than forwarding an email.
Knowledge sits underneath all of it. Articles are written from tickets, failed searches are the writing queue, and the AI answers only from what is written — which is what makes it safe to put in front of a customer.
None of this is a tier. Field-level permissions, the audit trail, the API and multi-brand behave the same on the smallest plan.
Open a ticket and the organisation underneath is the one Flow sold to and Books bills. Their entitlement, their open project and their arrears are already there, because none of it was ever exported into support.
Not add-ons and not an enterprise tier. These behave the same whether you run one product or all seven.
If you are moving off a shared inbox, read queues and routing. Ownership from the first minute is the change that stops duplicate replies, and it is worth more than any other feature here.
If you already run a help desk, read entitlement and escalation. Those are the two joins a standalone tool cannot have, and they are where the arguments with customers actually come from.
Yes. Every feature listed here works with Desk alone. Where one says it joins another product, that join simply waits — switching the other product on later needs no migration, because the record it wants is already there.
No. Custom fields, permissions, automations, the audit trail and the API behave the same on the smallest plan as on the largest. The list on this page is the whole list.
Work backwards from the handover that costs you most. The feature that removes a manual step between two teams is worth more than the one with the longest description.
Fourteen days, every module, no card. Or half an hour with someone who will use your own numbers.