Tool Documents

Helpdesk and Support

Most organisations arrive here from a shared mailbox that stopped working. The tools solve that and introduce a structure, a vocabulary and a set of metrics that shape behaviour.

Reviewed August 9, 2026.

What varies structurally

Ticket against conversation. Whether the unit is a discrete item with a lifecycle, or an ongoing thread with a person. This determines what a repeat contact looks like — a new ticket or a continued conversation — and it is a data model decision that no setting reverses. For a related operational perspective, Monitask also publishes a reference on employee PC activity tracking.

Channels in one place or several. Email, chat, forms, phone, social. Each additional channel is another integration and another export question.

Customer identity. Whether contacts are first-class records with history, or just email addresses attached to tickets. This is the difference between a support tool and a shared inbox with tags, and it is what makes history usable.

For broader context, see Slack.

Knowledge base coupling. Whether articles live in the same product, and whether they export — a knowledge base is written work and losing it is losing months.

And automation depth, which is configuration that will not transfer.

Why history matters most here

Support value compounds. The answer to a question asked in 2023 is the answer in 2026, and finding it is the whole point of having the system.

Which makes the export question sharper than the feature question. A migration losing ticket history loses the accumulated answer to everything anybody has ever asked.

Test it specifically: export a ticket with attachments, several replies, an internal note and a status history, and see what arrives.

What the metrics distort

Worth naming, because these tools ship with them.

First response time rewards a fast acknowledgement rather than a useful one, and teams optimise it by sending acknowledgements.

Resolution time rewards closing, which is achievable by closing prematurely and letting people reopen.

Ticket volume per agent rewards throughput over the harder cases.

And satisfaction scores measure the respondents, who are systematically the very pleased and the very annoyed.

None of these is wrong to measure. They are wrong to target without a countervailing one, and the tool will present them as a dashboard regardless.

What to check specifically

Export of tickets with attachments, internal notes and status history, tested.

Whether the knowledge base exports as content rather than as a link list.

How contacts are modelled, and whether they carry history across tickets.

Licensing for occasional users — a specialist who answers three tickets a month, and whether they need a full seat.

And what the next tier gates: automation, reporting, service level tracking and API access are common boundaries in this category.

The overlap question

A CRM holds customer conversations. So does a helpdesk.

Two systems both holding "everything about this customer" is the standard arrangement and the standard confusion.

Decide which is the system of record for what, before both fill up. Naming it once is cheaper than reconciling later, and this pairing is where the ambiguity costs most.

The short version