Help desk

A help desk consolidates incoming requests from every channel you offer, typically email, a contact form, chat, and sometimes phone or social, into a single queue. Everyone works from that queue instead of from their own mailbox, and the system tracks each request's status, owner, and full history so the next person to touch it can see what already happened.

Four things separate a help desk from a mailbox with a shared password, and they are the only four that matter on day one. Every request has a status, so you can tell what is still open. Every request has an owner, so two people do not answer it and nobody assumes the other did. Every request keeps its history in one place, including the internal discussion about it. And the whole thing is searchable, so "what did we tell this customer in March" takes ten seconds. Everything else a help desk sells you is built on top of those four.

Help desks sit on a spectrum. At the light end is a shared inbox with statuses and assignment. In the middle is what most small companies actually need: the four basics plus internal notes, a knowledge base, and enough reporting to see volume and speed. At the heavy end are platforms with routing rules, SLA timers and breach alerts, tiered escalation, workforce scheduling, custom fields, and a marketplace of integrations. The heavy end is designed for support organizations with a manager who does not answer tickets, and it is priced and configured accordingly.

Here is the arithmetic a team of two to ten should run before buying at the heavy end. Most of those platforms bill per agent, so a six-person team on a mid tier at 25 dollars per seat is 150 dollars a month, or 1,800 dollars a year, and there is a real second cost in the day or two someone spends configuring rules that six people talking to each other could handle with a sentence. If, after a month, your team uses four features of the forty you are paying for, you bought the wrong size. The tell is not the price, it is the number of settings screens nobody on the team has opened.

"Help desk" and "ticketing system" are used interchangeably most of the time, and arguing about it is not worth anyone's afternoon. Where people do draw a line, ticketing system names the narrow mechanism of turning requests into tracked records, while help desk names the wider setup around it, including the agents, the queue, the knowledge base, and the reporting. IT teams also use help desk for internal employee support, which is the same software pointed at staff rather than customers.

AcornReply is a help desk at the light end of that spectrum, and is specific about which end. It gives you one queue across email, a contact form, live chat, and its REST API, with statuses of open, snoozed, resolved, and spam, assignment with an optional auto-assign, priority, internal notes with mentions that customers can never see, full-text search over every past conversation, a timeline of what happened to each one, and a knowledge base that doubles as a public help center. Every conversation also arrives with an AI draft written from that knowledge base in your workspace voice, which by default a person edits and sends.

What it deliberately does not have is the heavy end: no routing rules, no SLA timers or breach alerts, no tiered escalation, and no ticket numbers, since conversations are threads rather than numbered records. Pricing is flat per organization rather than per seat, 20 dollars a month on Pro for the whole account with a free tier to start, so adding the fourth and fifth person does not change the bill. If you need workload routing across dozens of agents or contractual SLA reporting, buy a platform built for that instead.