# Before you buy help desk software, do this first Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-01 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Before you buy help desk software, do this first Meta Description: Help desk software organizes conversations, it does not reduce them. Sort your inbox into three piles, answer the repeats in public, then buy smaller. URL: https://forumcat.com/blog/before-you-buy-help-desk-software Help desk software sorts your customer conversations. It gives each one an owner, a status, and a history. It does not make the conversations fewer. So if your inbox hurts because the same ten questions keep arriving, a new tool will hold that pain in a tidier place, at a price per agent per month. Do one thing first. Answer the repeat questions once, in public, where people can find them without emailing you. Wait two weeks. Then buy the help desk, sized for the work that is left. Most small teams do end up buying one. Just a smaller one than the full inbox suggests. ## What help desk software is actually for A help desk is built for work that belongs to one customer and one agent. Where is my order. My account shows the wrong plan. Please refund this charge. Each of those needs a private thread, a clear owner, and a record you can look up six months later. Four things earn the money. Assignment, so every message has a name on it. Status, so you can see what is open and what is waiting. History, so you know what this person was told last time. Accountability, so nothing sits for four days without someone noticing. A shared mailbox does some of that badly. A help desk does all of it well. The real sign you need one is dropped work, not volume. If two people reply to the same email, or a customer has to ask twice because the first message got buried, you have outgrown the mailbox. If the mailbox is just full and nothing is falling through, volume is the problem, and a queue does not shrink volume. ## Sort your last 100 emails into three piles Before you compare vendors, look at what is filling the inbox. Open your mail, take the last 100 customer messages, and drop each one into a pile. Pile one is repeat questions. How do I change my plan. Do you ship to Canada. What file types do you take. Anyone on the team could answer these, the answer is the same every time, and it does not depend on who is asking. Pile two is account-specific issues. Real problems, but you need this person's order, invoice, or settings open in front of you to answer. Pile three is bugs and escalations. Something is broken, and it may need an engineer. Piles two and three need a ticket queue. Pile one does not. Pile one needs a page. Count the piles instead of guessing at them, because the count is what tells you how big a help desk to buy. ## Answer the repeat pile once, in public Take pile one and write each answer one time, somewhere a customer can read it without an account and without emailing you. Public matters for two reasons. Your customers can search it at 11pm on a Sunday. And search engines can index it, so the next person with that question may land on the answer and never reach your inbox at all. Two shapes work here. Articles you write ahead of time, which is the classic [help center software](https://forumcat.com/help-center-software) approach. Or questions your customers ask in public, with your team answering underneath, which is a [support forum](https://forumcat.com/support-forum). The second shape has one quiet advantage. You never have to guess the wording, because the question arrives in the customer's own words, and those are the words the next person will type into Google. Forumcat is one way to run that public layer: [a hosted self-service Q&A portal](https://forumcat.com/customer-self-service) on your own domain or a subdomain, live in about five minutes, readable and searchable without an account. Whatever you pick, the job is the same. Every answer you have sent twice becomes a page you send once. ## Wait two weeks, then count again Give the public answers time to get found, then run the same count on a fresh 100 emails. The gap between the two counts is the number you take shopping. ![Forumcat dashboard analytics showing questions and views over time](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/10-analytics-light-1788188142296-compressed.png) _Watch what the inbox loses after answers go public._ Here is the arithmetic, with made-up numbers you should replace with yours. Say 200 customer emails arrive each month, and 80 of them are repeats. At six minutes each, the repeat pile alone is eight hours of typing a month. Say your shortlisted help desk costs $25 per agent per month, and today four people live in the inbox, so the bill would be $100 a month, or $1,200 a year. Now say the public answers take 60 of those 200 emails away. Three people can hold what is left, so the same tool costs $75 a month. You saved $300 a year on software and got most of a working week back on top. The software saving is the small half of that. The hours are the big half. There is a second effect. Smaller queues make the cheap tier survivable. Plenty of teams buy the middle plan because the volume scares them, then find the extra features sit untouched for a year. ## Where each tool sits The public layer catches how-do-I questions. The help desk handles the private, specific, one-to-one work. Neither one replaces the other, and a team of five will usually run both without strain. There is a rough test for where a message belongs. If the answer would help a stranger, it belongs in public. If the answer needs someone's account open, it belongs in the queue. Answers in the public layer stay useful for years, while a ticket is finished the moment it closes. ![A Forumcat support portal filtered to solved questions](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/01-home-sort-solved-1788188145446-compressed.png) _The repeat pile, answered once, in public._ Public answers do need to look official, which is why staff replies in Forumcat show the person's role next to their name, and one reply gets marked as the accepted answer so readers stop reading there. Starting is $9 one time on a Forumcat subdomain, which is small enough that you can test the idea before your help desk trial even ends. ## A short checklist for picking the help desk Once you know what remains, the buying part is short. Work through these questions with your real numbers. - Do you need a full help desk, or a shared inbox tool? Shared inbox tools cost less and do assignment, notes, and saved replies. Many small teams never need more. - What counts as an agent? Ask whether part-time helpers, a founder who dips in, or a person who only reads need a paid seat. This is where quotes grow. - Can you live on the entry tier for a year? If the answer is no, ask which single feature forces the upgrade, and whether you use it weekly. - Does it keep your support address? You want mail to your own domain, not a vendor address your customers have to learn. - Which features do you actually touch? For most small teams that is assignment, saved replies, a simple status, search over old threads, and one weekly number. Rules engines, deep automation, and chat widgets can wait. - Can you get your data out? Ask what an export looks like before you have three years of history inside. - Trial it with real mail for two weeks, not with test messages. Every help desk feels fine when it is empty. Buy the smallest thing that fixes dropped work. You can always move up a tier in month four, and by then you will know exactly which feature made you do it. Keep reading: [how a self-service forum cuts support tickets](https://forumcat.com/blog/cut-support-tickets-self-service-forum) and [knowledge base versus community forum](https://forumcat.com/blog/knowledge-base-vs-community-forum), and [running a customer community in 15 minutes a day](https://forumcat.com/blog/running-a-customer-community), and [a forum software requirements checklist](https://forumcat.com/blog/forum-software-requirements-checklist), and [what a support ticket really costs](https://forumcat.com/blog/cost-of-a-support-ticket), and [a support forum for an early-stage startup](https://forumcat.com/blog/support-forum-for-startups). ## FAQs Q: Does a small business need help desk software? A: Usually yes, once support is more than one person's side job. The trigger is dropped or duplicated work, not the size of the inbox. If a single person handles every message and nothing gets lost, a mailbox with a few labels can carry you for a while longer. Q: What should a small team pay for a help desk? A: Price by seats you truly need after you have cleared the repeat questions, and start on the entry tier. Count who needs to reply, not who needs to look. If a quote feels large, the usual cause is paying for seats that read and for features nobody opens. Q: Can I use a shared inbox instead of a help desk? A: Yes, for a small team with steady volume. Shared inbox tools give you assignment, internal notes, and saved replies at a lower price. You will feel the limits when you need reporting, service targets, or a customer history that spans several years. Q: What is ticket deflection? A: Ticket deflection means answering a question so well in public that the customer never has to write in. You publish the answers people ask for most and make them easy to find and search. Repeat email then drops on its own. Your support address stays where it is, in plain sight. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. ---