Customer Support Software, Without the Category Soup

Help desk, ticketing system, service desk, customer support platform. Mostly the same thing with different marketing, and here is where they genuinely differ.

The categories, decoded

Help desk / ticketing system. The core. Requests become tickets with owners and clocks. Zendesk, Freshdesk, Zoho Desk, Help Scout.
Service desk. A help desk plus ITSM process for internal IT. Freshservice, Jira Service Management, ServiceNow.
Shared inbox. A lighter take where customers experience plain email. Help Scout, Front.
Messaging platform. Support built around in-product chat, often doubling as a growth tool. Intercom.
CRM-native support. Support inside the same record as sales and marketing. HubSpot Service Hub, Salesforce Service Cloud.

Most buying mistakes are category mistakes rather than vendor mistakes: picking a messaging platform for an email-first queue, or a service desk for customer support.

What a support stack usually needs

A ticketing core

One queue, owners, statuses, clocks. Everything else attaches to this.

Self-service

A help centre that answers the questions you answer forty times a week.

Measurement

Response time, resolution time, CSAT, backlog age. Enough to know whether you are improving.

Automation

Routing, escalation, chasers and auto-close. The difference between a team of eight and a team of twelve.

AI, used narrowly

Drafting replies and surfacing articles works well. Fully autonomous resolution works in a narrower band than the demos suggest.

Duplicate control

The piece nobody sells you, and the one that quietly consumes a tenth of your capacity.

Questions that separate a demo from a decision

Show me routing for a ticket that needs two teams.
Show me the report for first reply time by channel, last month, excluding weekends.
What happens when a customer replies to a ticket closed three weeks ago?
How do I merge five tickets about one problem?
How does the system know two tickets are the same request?

The last two are where the answers get vague, and they are the ones that cost you every single week after go-live.

Frequently asked questions

Does merging in your helpdesk lose the customer replies?+

No. Ticket Merger uses the native your helpdesk merge, so the conversation, attachments and audit history move onto the surviving ticket. The duplicate is closed with a note pointing at the original.

Can I review merges before they happen?+

Yes. Start in suggest-only mode: Ticket Merger flags the pairs it believes are duplicates and leaves the decision to an agent. Most teams run that way for a week, check the hit rate, then let the confident matches merge on their own.

What stops it merging two tickets that are not the same?+

Rules you set. Match on requester, subject similarity, body similarity and a time window, and exclude anything you want left alone, like tickets from a specific form, group or tag. Anything below your confidence threshold gets suggested rather than merged.

How long does setup take?+

About five minutes to connect, and the first scan of your open queue runs immediately after. Onboarding help is included on every plan.

The line item missing from every buyer guide

Duplicate tickets. Between 8% and 20% of your queue, on every product in every category above.

Start free trial

14-day free trial. No credit card required.