The team, the process and the software that turn incoming requests into resolved ones.
Help desk. A help desk is the combination of people, process and software a company uses to receive, track and resolve support requests. A help desk gives every request an owner and a status, so nothing depends on one person remembering it. The term covers customer-facing support desks and internal IT desks alike.
Requests arrive through whatever channels the company offers — an email address, a chat widget, a contact form. The help desk converts each one into a tracked item, assigns it to a person, and moves it through a small set of states: new, in progress, waiting on the customer, resolved. Replies to the customer and discussion inside the team both attach to the same record, so the full history stays in one place. Over time, the answers a help desk produces feed back into documentation, so the same question costs less to answer next time.
The non-obvious part: a help desk is a discipline before it is a product. A three-person team with a plain shared mailbox and a firm ownership rule is closer to a real help desk than a large team running expensive software nobody triages. The software makes the discipline cheaper to keep — it cannot supply the discipline itself.
Without a help desk, requests live in personal inboxes. Two people answer the same customer with different answers, a third request gets no answer at all, and when someone goes on holiday their open cases go with them. None of it is measurable, so none of it is fixable — you cannot see how long customers wait, which questions repeat, or where work piles up.
The cost is quiet. Customers rarely complain about a lost email; they follow up once, then leave. A help desk exists so that the failure mode is a visible queue instead of an invisible silence.
The trigger point is simple: the moment two or more people answer the same address, you need help desk mechanics — even informal ones. Decide where requests come in, and close the side doors (personal addresses, DMs) by redirecting them to the front door. Agree on one ownership rule: every conversation has exactly one owner, and ownership is taken explicitly, never assumed. Pick a small status vocabulary and use it honestly — three states everyone respects beat ten states nobody updates.
Then measure two things before anything else: how long a customer waits for the first reply, and how long until the request is actually resolved. Write down the escalation path — who takes a case when the owner is stuck — before you need it. Only after the process holds should tooling questions matter; buy software to keep a working process cheap, not to conjure one.
A help desk sits on top of more specific ideas: the software that tracks requests, the front door most teams start with, and the routines that move work through it.
Give your customers faster answers and your team their evenings back.
Desktop and mobile. Free for solo.