# About Name: Forumcat Description: Notes and guides from Forumcat on customer questions, self-serve support, and running a public Q&A forum your customers actually use. URL: https://forumcat.com/blog # Navigation Menu - Home: https://forumcat.superblog.click/ - Search: https://forumcat.superblog.click/search - Try Forumcat: https://forumcat.com # Blog Posts ## Why public answers beat private email support Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Why public answers beat private email support Meta Description: An email answer helps one person once. A public answer helps every later reader. The objections, answered, and the questions that must stay private. URL: https://forumcat.com/blog/public-answers-beat-private-email A private email answer helps one person once. A public answer helps everyone with the same problem, including the people who never write in. Email support is still needed for anything about one customer's account. Most teams should do both. Keep email for the private half of the work. Move the repeating half into public. This post covers how that works, the objections worth taking seriously, and the line for what must never be public. ## The arithmetic of one answer Here is an example. The numbers are made up, and they are only there to show the shape. Say 30 emails a week ask the same thing. Say each reply takes ten minutes. That is five hours a week, every week, for as long as the question keeps arriving. Nothing piles up from it. Next week you type the same answer again. Now write that answer once in public. Say it takes twenty minutes, because you are careful with it. After that, the page does the work. Someone searches, finds it, and reads it, and you typed nothing that day. Those figures are an example, not a measurement, and your own numbers will differ. Read back through your last week of email and mark the questions that repeat. If you want to put a cost on each one, [what a support ticket costs](https://forumcat.com/blog/cost-of-a-support-ticket) walks through it. ## What email support does better Email is better at several real things. Those come first here, so the rest of this post is easier to trust. One customer's account belongs in email. Their plan, their invoice, their data, their sign-in trouble. None of that helps a stranger, and some of it should never be visible to a stranger at all. Refunds belong in email. So does anything under a contract, where the answer depends on terms you agreed with that one customer. An angry escalation belongs in email. An escalation is a complaint that has moved above normal support. A person who is upset usually wants a private room. Long conversations belong in email too. Some problems take eight or nine turns to work out. A forum thread can carry that, but email carries it better. So keep the inbox. The question is which answers should also exist somewhere a stranger can find them. ## Four things a public answer does that email cannot The first thing is that the next person searching can find it. Someone types their problem into a search engine at eleven at night. Your page comes up. They read it and carry on with their day. Nobody was on shift, and no email was ever sent. The second is that another customer can correct or extend it. A member replies with the version that worked on their setup. You get a better answer than the one you wrote, and you did not have to write it. The third is that a prospect can read it before buying. A prospect is a person thinking about buying from you. They can see how your questions get answered, and how fast. That builds more confidence than a page of claims does. ![A solved question in a Forumcat portal as a signed-out visitor sees it, with the accepted answer pinned under the question](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/40-anon-thread-solved-1788501905836-compressed.png) _The answer is on the page before anyone signs in._ The fourth is that your own team can link to it instead of retyping it. The next time the question arrives by email, the reply is one line and a link. Nobody writes the same paragraph from memory, so everyone sends the same answer. All four follow from the answer being on a page that anyone can open. ## What builds up over time An inbox is a stack that empties. A forum is a shelf that fills. The same typing produces a different thing at the end of the year. The work feels identical while you are doing it. You read a question, you think, and you write a careful reply. In one case the reply goes to one address and is gone. In the other it goes onto a page with a web address, and the page stays. ![Search results in a Forumcat portal for the query webhook, listing solved questions](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/03-search-webhook-1788188135310-compressed.png) _The shelf that fills, one answered question at a time._ After six months of this you have something you can use. New staff read the old threads to learn the product. You find out which parts of the product confuse people. You send links instead of paragraphs. If you want that stack of answers to actually cut your email volume, [a self-service forum that reduces support tickets](https://forumcat.com/blog/cut-support-tickets-self-service-forum) covers how to get there. ## The objections, one at a time Our complaints will be public. They already exist. Customers write them to you, to their colleagues, and sometimes to social media. Publishing your answer is the part that changes the impression. A complaint with a clear, quick, honest answer under it reads better than the same complaint with silence under it. Competitors will read it. They will read it either way, and they can sign up for your product today. What a competitor mostly learns from your forum is that you answer people, which is not a secret you were keeping. Our answers are wrong sometimes. Then they are wrong in public, where a customer or a colleague notices and says so. In an inbox, a wrong answer goes to one person and nobody else ever sees it. A public mistake gets fixed. A private one sits there. Customers want privacy. Some do, for some questions. That is a real objection, and it is the next section. ## The line between public and private Here is a rule you can apply today. If the answer would help a stranger, it belongs in public. If the answer needs their account details, it belongs in private. Most questions split down the middle. Someone asks why their invoice looks wrong. Half of that answer is how invoices are calculated, which helps everyone. The other half is what happened on invoice 4471, which helps one person. Answer the general half in public and send the account detail privately. Some things should never be public at all: account numbers, invoices, home and billing addresses, security reports until the hole is fixed, and anything about a named individual, staff or customer. Those never go on an open page. Clarity about that line makes a public forum comfortable to run. [Private versus public customer communities](https://forumcat.com/blog/private-vs-public-community) goes deeper into the trade if you are still deciding. ## How to move without breaking anything Keep the email address. Do not remove it, do not hide it, and do not announce a migration. Nobody likes being told that the way they reached you has changed. Instead, change what you do with the repeats. When a question arrives that you have answered before, write the answer in public first. Then reply to the email with a short note and the link. The customer gets the same answer at the same speed. The difference is that the answer now exists somewhere. Do not force customers to post in public. Some will keep emailing forever, and that is fine. Over time, more people find the page before they write to you, because searching is faster than waiting for a reply. The forum grows because it is quicker for them. Give it a few months before you judge it. The first twenty threads feel like extra work. They are the ones the next hundred answers link to. ## Where Forumcat fits, and where it does not Forumcat is a hosted [customer questions and answers portal](https://forumcat.com/customer-questions-and-answers). Customers read and search it without an account, so the answers work for the people who never write in. Asking a question needs a sign-in, by magic link, six-digit email code, or Google. A magic link is a sign-in link sent to email, so nobody has to invent a password. A question can be made private, so only the asker and staff see it. That is where the account half of a split question goes. Every answered public question ships QAPage structured data. Structured data is a small block of machine-readable detail in the page, and QAPage tells a search engine that the page is a question with an accepted answer. Forumcat does not receive email. It does not connect to your help desk and it does not replace one. It is the public half, sitting beside whatever inbox you already run. [A hosted support forum](https://forumcat.com/support-forum) on a Forumcat subdomain is $9 one time, with a 7-day free trial and no card. Keep reading: [how a self-service forum cuts support tickets](https://forumcat.com/blog/cut-support-tickets-self-service-forum) and [what a customer portal is](https://forumcat.com/blog/what-is-a-customer-portal). ## FAQs Q: Should customer support be public or private? A: Both, split by the kind of question. Answers that would help a stranger, such as setup steps, error messages, billing rules, and product limits, work better in public. Answers that need one customer's account details belong in private. Most teams keep an email address and move the repeating questions to a public page. Q: What are the risks of a public support forum? A: Complaints are visible, competitors can read it, and a rushed answer is on a page anyone can find. Those are real, and worth counting. The counter is that the complaints exist either way, and a public complaint with a good answer under it usually reads better than silence. The larger risk is posting something that should have stayed private, so the line needs to be clear before you start. Q: Will competitors read our support answers? A: Yes, and they would have found the same information another way. They can sign up for your product, read your docs, and ask your sales team. What they learn from a forum is mostly that you answer customers properly. That is not information you were protecting. Q: What questions should stay in email? A: Anything about one customer's account, plan, invoice, or data. Refunds and anything governed by a contract. Angry escalations, where a private room is the decent thing to offer. Conversations that will take many turns to sort out. Security reports stay private until the problem is fixed. Q: Can you run a forum and email support together? A: Yes, and most teams should. Keep the email address exactly as it is. When a repeat question comes in, write the answer in the forum first, then reply to the email with the link. Over time the questions that repeat live on public pages, and the inbox handles the cases that are about one person. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## Support forums for SaaS: answer once, deflect while you sleep Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Support forums for SaaS: answer once, deflect always Meta Description: Which SaaS questions belong in public and which stay in the inbox, the rhythm after each release, and how answered threads keep working overnight. URL: https://forumcat.com/blog/support-forum-for-saas A support forum works for a SaaS product for two reasons. Your questions repeat, and your customers are awake when your team is not. So publish the questions that repeat, and keep anything tied to one account in the inbox. That is the sorting rule. A public answer then keeps working overnight and in other time zones, without anyone on shift. A support forum here is a set of public pages. One page holds one question and its replies. Anyone can read and search those pages without an account. The rest of this post is how to run one next to the tools you already pay for. ## Why this fits SaaS in particular Three things about software products make public answers pay off. The first is release speed. You change the product every week or two. Questions arrive in clusters right after a change, and the same cluster hits many customers at once. Answer it once and you have covered the whole cluster. The second is time zones. Software sells everywhere from day one. A customer in Sydney gets stuck while your team in London is asleep. An email waits nine hours. A public page does not. The third is that people search you before they write to you. Someone evaluating your product will read your public answers. So will a customer deciding whether to renew. A good public answer is read by buyers as well as by users. ## The sorting rule: public or inbox Put a question in public if the answer would help a stranger. That covers how a feature works, why an error message appears, what a setting does, whether something is possible at all, and the steps for setup or migration. None of those need the customer's data. Any reader with the same question gets the same answer. Keep a question in the inbox if the answer needs their data. Billing on one account, a refund, a password reset, a bug tied to one workspace, and anything covered by a contract or an NDA all belong there. An NDA is an agreement not to share what a customer told you. Some questions start public and turn private halfway through. A customer asks how billing proration works, then pastes an invoice number. Answer the general part in public. Move the account part to email. On Forumcat you can also mark a question private, so only the asker and staff can see it. ## How one thread answers at two in the morning The mechanism is plain. A customer hits a problem at two in the morning. They search your site or they search Google. They find a solved thread that matches. They fix the problem and close the tab. No ticket is filed, so nobody has to reply to it in the morning. That only works if the thread is findable and clearly finished. Findable means the title uses the words a customer would type. Finished means one reply is marked as the accepted answer, so a later reader knows which reply to trust. Here is the arithmetic, with made-up numbers you should replace with your own. Say thirty questions a week ask the same handful of things. Say each one costs ten minutes to answer. That is five hours a week. One good public thread does that job after you write it once. ![A solved question in a Forumcat portal with the accepted answer pinned under the question](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/06-thread-solved-1788188139254-compressed.png) _The thread that answers at 2am without anyone on shift._ Those numbers are an example, not a measurement. Count your own repeats for two weeks before you trust any of it. ## Where the forum sits next to your other tools The forum sits beside your help desk. It does not replace it. Account-specific work still goes to the inbox, and the forum handles the questions that repeat. It is also a different thing from a shared inbox, live chat, a status page, or a roadmap tool. Those four tools each answer a different need. A status page says whether the service is up. A roadmap tool collects feature requests. You may already own some of them, and a forum does not make any of them redundant. The overlap that matters is with your help center. A help center holds articles your team writes. A forum holds questions your customers asked, in their own words. Both can live on the same site, and many teams run both. ## What to publish first Start with the questions you already answer, in this order. Take the top ten questions from your inbox over the last month. Then add the questions sales hears every week during demos. Then the questions your last three releases caused. Then the errors your team explains most often, one thread per error message. Write each one as a question in the customer's words, with your answer under it. Mark your reply as the accepted answer. Ten to twenty solved threads is enough to open with. Our post on [how to seed a new forum](https://forumcat.com/blog/seed-a-new-forum) covers the writing part in detail. Do not wait for customers to post first. An empty forum looks abandoned, and nobody wants to be the first person asking into silence. ## The release rhythm This is the habit that keeps a SaaS forum alive. After each release, post the two or three questions the release will cause. Answer them yourself, before anyone asks. You already know what the questions will be. The team argued about the change in review, and support flagged the confusing part. Write those down as threads on release day. Then link the thread from your release notes and your in-app changelog. The customer who is confused by the change finds the answer in the same place they read about the change. This takes about twenty minutes per release. It is the cheapest support work in the cycle, because you are writing while the change is fresh. ## What goes wrong, and the fix Three things go wrong for SaaS teams. All three are fixable, and all three get worse if you ignore them. Threads go unanswered during a busy sprint. A visitor sees a question from three weeks ago with no reply and decides that writing to you is pointless. The fix is one owner and one daily check of the unanswered list, even during a crunch. Answers go stale after a UI change. Your thread says click Settings, then Billing. The button moved two releases ago, so the answer is now wrong. This is the main maintenance cost of a public forum. The fix is a line in your release checklist: after a UI change, search the forum for the old label and update what you find. An outage thread gets abandoned. Customers post during an incident, someone replies "looking into it", and nobody comes back. The fix is to close the loop on the same thread once the incident ends, with one short note on what happened. ## What to measure Keep the measurement short. Three numbers tell you enough. Count repeats this month that were already answered in public. That number should fall. Count searches on your portal that returned nothing, because those are the threads you have not written yet. Count how many support replies included a link to a public thread, because that habit is what makes the forum grow. ![The analytics page in a Forumcat dashboard showing question and view counts](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/10-analytics-light-1788188142296-compressed.png) _Views on old threads are the overnight work, made visible._ Views on old threads matter too. A thread you wrote in March that still gets read in September is doing the quiet work. For the arithmetic behind all of this, see the [ticket deflection page](https://forumcat.com/use-cases/ticket-deflection) and our post on [cutting support tickets with a self-service forum](https://forumcat.com/blog/cut-support-tickets-self-service-forum). Forumcat is one way to run this. A portal is live in about five minutes and there is nothing to install. Customers read and search without an account, and sign-in for asking is a magic link, a six-digit email code, or Google. The asker or staff marks one reply as the accepted answer, and it pins under the question. Every answered public question ships QAPage structured data, which lets search engines read the page as a question with an accepted answer. A [hosted support forum](https://forumcat.com/support-forum) on a Forumcat subdomain is $9 one time. A custom domain and higher caps are $99 a month. The trial runs 7 days with no card. Forumcat has no integrations and no webhooks. It cannot import your existing help center articles, and it does not sync with Slack or your help desk. You seed it by writing threads, and you link to it from the tools you already use. Keep reading: [cutting support tickets with a self-service forum](https://forumcat.com/blog/cut-support-tickets-self-service-forum) and [how to seed a new forum](https://forumcat.com/blog/seed-a-new-forum). ## FAQs Q: Does a SaaS company need a support forum? A: You need one when the same questions keep arriving and your customers are spread across time zones. If your support volume is a few emails a week, a good help center page is enough. Once you are answering the same thing thirty times a week, public answers save real hours. Q: What questions should go on a public forum instead of the inbox? A: Publish anything whose answer would help a stranger: how a feature works, why an error appears, what a setting does, and how to set up or migrate. Keep anything that needs the customer's own data in the inbox. That means billing on one account, refunds, password resets, and bugs tied to one workspace. Q: Is a forum better than a help center for SaaS? A: They do different jobs, so most teams run both. A help center holds the articles your team decided to write. A forum holds the questions customers actually asked, in their own words, which is usually what the next person types into a search box. Q: How do I keep forum answers from going stale? A: Add one line to your release checklist. After a UI change, search the forum for the old button or menu name and update the threads you find. Fix the accepted answer first, since that is the reply people read. Old threads with wrong steps cost you more trust than no thread at all. Q: Can a forum replace my help desk? A: No. A forum handles the questions that repeat and helps people who would rather not write in at all. Account-specific work still needs a mailbox or a help desk behind it. The forum sits beside that, as the self-serve layer. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## Customer advocates: how a public forum creates them Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Customer advocates: how a public forum creates them Meta Description: Advocates are the few customers who answer for you. The four forum moments that create one, how to recognise them, and how to keep them, honestly. URL: https://forumcat.com/blog/customer-advocates Customer advocates are made in two steps. You help someone well in public, and then you credit them in public. A forum creates advocates because both steps happen on the same page, where other people can see them. You cannot recruit an advocate before you have helped one. On a support forum, an advocate is a customer who answers other customers without being asked. This post covers the moments that create that person, how to spot the two or three you already have, and what to do with them. ## What a customer advocate is here An advocate is a customer who answers other customers, recommends you without being asked, and corrects wrong claims about you in public. That is a different thing from a customer advocate inside a company. In many companies, customer advocate is a job title for a support agent. Search results mix the two. This post is only about the customer version, the person who does not work for you. Nobody is hired for this and nobody signs up for it. The behavior appears after the person has been helped. An advocate is someone who answers the next person's question. ## Why advocates only appear in public A private answer ends when the thread ends. Nobody becomes an advocate in your inbox. Two things happen on a public page that cannot happen in email. Other people arrive at the answer later, through search or a link. The person who asked can see that their question helped strangers. That second part is what changes someone. They asked because they were stuck. A month later the page they started is still helping people, and they can see it. Public work is also visible to the next person deciding whether to post. They see that questions get answered here. More on that in [why public answers beat private email](https://forumcat.com/blog/public-answers-beat-private-email). ## The four moments that make one Four ordinary moments do most of the work. Each one is something you can do this week, inside [a customer community](https://forumcat.com/customer-community) you already run. 1. You answered fast and completely while they were stuck. Give the actual steps, in the thread, on the same day. A link to a doc page does less of this work. 2. You marked their reply as the accepted answer, in front of everyone. The accepted answer is the one reply later readers should trust. It pins under the question. 3. You said in public that they were right and you were wrong. A correction accepted in the open is worth more than any thank-you note. 4. You shipped something they asked for, and said whose idea it was. Name the person in the release note or the thread. The second one does most of the work, and it costs nothing. Marking a customer's reply as the accepted answer takes a few seconds. It puts their words at the top of a page that strangers will read for years. ![The solution badge on an accepted answer in a Forumcat thread](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/13b-solution-badge-1788501917214-compressed.png) _Public credit, at the moment it means something._ ## How to spot your early advocates Read your own forum for three signals. Look for people who reply to threads that are not theirs. Look for people who correct a small detail politely. Look for people who come back after you helped them once. You will find two or three names. Maybe five on a busy forum. That is what this looks like at a small company, and it is normal. A handful of regulars is the outcome. Write the names down somewhere. You will use the list when you need an opinion before you ship. ![A member profile in a Forumcat portal listing the replies that person has written](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/07-profile-member-replies-1788502813280-compressed.png) _The regulars are visible on one page, before you ever ask them anything._ ## What to do with them, in order Start with the cheapest thing and stop when it stops being useful. The order matters more than the effort. 1. Reply to their answers. A short staff note saying the steps are correct tells them, and the reader, that the answer holds. 2. Credit them. Mark their reply as accepted. Say thank you in the thread, where other people can see it. 3. Answer their questions first when you have a queue. They are already spending their time on your customers. 4. Ask their opinion before you ship something. A short question in a thread is enough. 5. Tell them when you used it. Without this step, the next question you ask is not worth their time. A badge or a title comes last, if at all. Some people do not want to be visible, and a public label can make them stop. Ask before you name anyone publicly. ## The limits Three limits apply, and it is better to say them early. Most customers will never advocate. They have a problem, they find an answer, and they leave. That is a good outcome, and it is what most of your traffic is. Advocates are not free support. They answer questions you would have answered anyway. What changes is who the answer came from, and how the next reader reads it. An advocate who gives a wrong answer is now a public wrong answer. Staff still read every thread. Correct the detail gently, in the open, and mark the reply that is actually right. ## What kills advocacy Four things undo the work above. A thread ignored for a week. The person learns that posting here does nothing. A support reply that contradicts a member without acknowledging them. It reads as a correction of the person, not of the detail. A forum that goes quiet when something breaks. People remember which places went silent during an outage. Taking credit for their idea. Once is enough to end it. Here is the arithmetic, as an example rather than a measurement. Say you have five regulars, and each answers two questions a week. That is about 40 answers a month you did not write. Count who wrote them, rather than the hours it saved you. Those 40 answers came from customers, in a place where the next customer can read them. Forumcat is built around that public credit. The asker or a staff member marks one reply as the accepted answer, and it pins under the question. Member profiles list the questions and replies a person has written, so a regular's contribution sits on one page. Staff replies show a role next to the name, so official answers stay easy to tell apart from member answers. There are no badges, points, reputation scores, or leaderboards, so recognition here is a person saying thank you in public. A [hosted support forum](https://forumcat.com/support-forum) on a Forumcat subdomain is $9 one time, with a 7-day free trial and no card. Keep reading: [the daily routine for running a customer community](https://forumcat.com/blog/running-a-customer-community) and [how to build a customer community](https://forumcat.com/blog/build-a-customer-community). ## FAQs Q: What is a customer advocate? A: On a support forum, a customer advocate is a customer who answers other customers, recommends you without being asked, and corrects wrong claims about you. They do not work for you and nobody assigned them the job. The same phrase is also a job title inside some companies, where it means a support agent. Those are two different roles that share a name. Q: How do you turn customers into advocates? A: Help them well in public, then credit them in public. Answer fast and completely while they are stuck. Mark their reply as the accepted answer when they help someone else. Say so in the open when they were right and you were wrong, and name them when you ship their idea. Q: Do you need a customer advocacy program? A: Not at a small company. A program is a named set of rewards and titles for your best contributors, and it needs a crowd to work. Start by answering well, marking accepted answers, and thanking people in the thread. A program can come later, if you ever have enough regulars for it to mean something. Q: How many advocates does a forum get? A: Two or three names on a small forum, maybe five on a busy one. Most customers read an answer and leave, and that is the normal case. A handful of regulars who answer other people is a good result. Anyone promising a movement is describing something else. Q: What is the difference between an advocate and a moderator? A: A moderator has staff rights. They can hide posts, close threads, and suspend members, and you gave them those rights. An advocate has no rights at all and answers because they want to. Some advocates later become moderators, if they want the job and you trust their answers. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## How to write welcome posts and onboarding for new forum members Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Welcome posts and onboarding for new members Meta Description: A welcome post that tells people how to ask, plus the two touches teams skip: the ask-form copy and the first staff reply. Templates included. URL: https://forumcat.com/blog/welcome-posts-for-new-members A welcome post on a support forum should do three things. It should say what the forum is for, show how to ask a question that gets answered, and say when staff reply. Staff means the people on your team who answer. Warmth is fine. A greeting by itself does not change how people post. A welcome post is the first message a new member sees. Pin it at the top of the list. Pinning means the post stays at the top while new threads appear below it. A thread is one question with its replies. People also call this a community welcome message. Here is a short version you can paste and edit. It does the three jobs above. Welcome. This board is for questions about the product. Search first, then ask one question per thread, and write the title the way you would search it. Staff reply on weekdays within one working day. Mark the reply that solved it so the next person can find it. ## Why a friendly welcome post usually fails Most welcome posts come from social groups. They say hello. They ask people to introduce themselves. On a social group, people often joined to talk, so a hello post can fit. On a support forum, people joined because they need an answer. Something is stuck, and they have a deadline. An introduction is extra work with no payoff in that room. The person already has to explain the problem. A second post about themselves is another task, and many will skip it. Start with the problem they came to solve. Tell them how to ask it so someone can answer. You can be warm when you reply on their thread. ## Write the pinned welcome post in five parts Keep the whole post under 300 words. People skim, so a short post gets read. Write it once and pin it. ### What this forum is for Say what belongs here, and say what should go to email instead. Paste the next three sentences and add your product name. This forum is for questions about \[product name\]. Anyone can read the answers, including people who are not customers. For anything about your own account, your bill, or a security issue, email support instead. A [community help center](https://forumcat.com/community-help-center) needs the same split. Public how-to questions stay on the board. Personal account questions go to email. ### How to ask so you get answered Five rules cover it: search first, one question per thread, a title in plain words, what they already tried, and their plan or product version. A plan is the product level they pay for. Tell them never to include an account number. Search the forum before you post. Your question may already have an answer. Ask one question per thread. If you have two problems, open two threads. Write the title in the words you would type into search. Say what you already tried, include your plan or version, and never include your account number, invoice number, or password. "The save button does nothing on the billing page" is a title people can find later. "Help please" is not a title people can find. ### What happens next Say who replies, roughly how fast, and what the accepted answer means. The accepted answer is the one reply later readers should trust. A staff member replies on weekdays, usually within one working day. You, or a staff member, will mark one reply as the accepted answer. That reply sits under the question. The thread then shows as solved, so the next person can trust it. Change the time window to match what you can keep. If you answer within two days, write two days. A promise you miss teaches people to email instead. ### The link to the guidelines Guidelines are the posting rules. Do not paste the whole rules page into the welcome post. Link to it instead. The posting rules are here: \[link\]. Please read them before you post. If you do not have that page yet, start from a [community guidelines template](https://forumcat.com/blog/community-guidelines-template). One short page is enough. ### What gets removed One line is enough. Name the things you will take down. We remove spam, insults, and posts that share private data such as account numbers. The guidelines page can hold the rest. ![The home page of a Forumcat portal listing questions, with the Ask button highlighted](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/00-home-ask-hover-1788188154841-compressed.png) _The welcome post sits above this list, and points at that button._ In the welcome post, name the Ask button so a new member knows the next click. That is the button they will use to post. ## The first reply a new member gets The first reply from staff matters more than the pinned post. Many people never read the pin. Everyone who asked reads the reply on their own question. Give the reply three parts. Thank them, answer the question, and mention one thing they can do next. Thanks for writing this up so clearly. The setting sits under Settings, then Billing, then Payment method. Once it is changed, mark this reply as the accepted answer so later readers see it first. Skip stock phrases. A stock phrase is a line you paste into every reply, such as "welcome to the community." Answer the thing they asked, then give one next step. If their question belongs in email, still thank them. Answer the part you can in public. Then say to email support for the account details. This first reply is part of the daily pass. The daily pass is the short review you do each day. [Running a customer community in 15 minutes a day](https://forumcat.com/blog/running-a-customer-community) covers that order of work. ## Onboarding is three touches Onboarding means the first instructions a new member gets. It is three touches. Skip a long series of welcome emails. Touch one is the pinned welcome post. Some people read it. Many do not. Touch two is the empty-state text on the ask form. Empty-state text is the helper text on a blank form, before anyone types. The ask form is the page where a customer writes a new question. Everyone who asks reads that text. It is the only onboarding copy that reaches every new poster. Touch three is the first staff reply. Most teams write the pinned post and skip the other two. That order is backwards. Write the form text first. Then write how you will answer. Then write the pin, as a short backup for people who scroll the home page. [A community manager's first 30 days](https://forumcat.com/blog/community-manager-first-30-days) are for reading and answering, not for extra programs. ## What to write on the ask form Write three short lines. Write them as commands. A command tells the person what to do. Search the forum before you post. Write the title the way you would search it. Leave out account numbers, invoices, and passwords. No copy on the forum does more work. The person is about to post, and they are looking at the box. A three-line reminder at that moment beats a long pin they already scrolled past. ![A customer typing a question title in a Forumcat portal, with existing related questions suggested below the field](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/10c-ask-related-questions-1788501894974-compressed.png) _Onboarding that happens at the moment it matters._ The title field is where a person can still find an existing answer. If a matching thread already exists, they can open it and stop. ## What to skip, and when to rewrite Skip automated welcome direct messages. A direct message is a private note sent to one person. An automated message is one the software sends by itself. That note does not answer the problem they came in with. Skip introduction threads, member-of-the-week posts, and a tour of every page. A member-of-the-week post names one person and asks the room to notice them. A tour is a walk through the forum's screens. Those things cost attention. They return little until the forum is already busy. If the board is still thin, [seed it with real questions](https://forumcat.com/blog/seed-a-new-forum) before you add extra posts. Rewrite the welcome post when you answer the same process question twice. A process question is a question about how the forum itself works, such as where to put billing questions. Rewrite when you add a category. A category is a named group of threads on one topic. Rewrite when reply times change, so the promise stays true. Put a date at the bottom. Use a line like "Last updated 4 September 2026". Readers can then see the post is current. On a Forumcat portal, a new member can read and search before signing in. Sign-in uses a magic link, a six-digit email code, or Google. A magic link is a sign-in link sent to email. A six-digit email code is a short number sent to the same address. There is no password to invent, so your welcome post does not need a password section. While someone types a question title, existing threads that already answer it are suggested. Those suggested threads do more onboarding work than a pinned post. There are no automated welcome messages and no onboarding emails. The three touches above are written once, by hand, even on a [hosted support forum](https://forumcat.com/support-forum). Keep reading: [how to seed a new forum so it does not look empty](https://forumcat.com/blog/seed-a-new-forum) and [running a customer community in 15 minutes a day](https://forumcat.com/blog/running-a-customer-community). ## FAQs Q: What should a community welcome post say? A: Say what the forum is for, how to ask a question that gets answered, and when staff reply. Add a link to the guidelines. Add one line on what gets removed. Keep the whole post under 300 words. Q: Do welcome posts actually work? A: A greeting that asks people to introduce themselves does little on a support forum. People came with a problem. A welcome post that teaches them how to ask, plus helper text on the ask form, plus a clear first reply, does the job. The pinned post alone is the weakest of those three. Q: How long should a welcome message be? A: Keep it under 300 words. If it is longer, people skip it. If a rule needs more detail, link to the guidelines page. Date the post so readers can see it is current. Q: Should new members introduce themselves? A: They should not introduce themselves on a support forum. An introduction is extra work with no payoff for someone who came to fix a problem. They can say who they are inside the question if it helps, such as their plan or version. Do not make a separate introduction thread. Q: What should the ask form say? A: Write three short commands. Search first. Title the question the way you would search it. Leave out account numbers. That helper text is read by everyone who asks, which is more than the pinned post reaches. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## A community manager's first 30 days: a checklist Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: A community manager's first 30 days Meta Description: A week-by-week checklist for a new community manager: what to read, seed, answer, and measure in the first month, and what to leave alone. URL: https://forumcat.com/blog/community-manager-first-30-days Spend week one reading. Spend week two answering. Spend week three fixing the small things you found. Spend week four writing down the routine and the numbers you will report. Change nothing structural in the first two weeks. A structural change is a change to the shape of the forum, such as new categories or a new look. You do not yet know which parts hold the place up. The rest of this post is that month, week by week, with a list of work to leave alone until day 30. This plan is for the person who now owns a customer forum. You may have been hired for it. You may have inherited it from someone who left. Either way, the plan assumes a small forum and a person with other duties. It is written for someone who runs [a customer community](https://forumcat.com/customer-community) alongside another job. ## Week one, read before you change anything Week one is reading. You are learning the forum, not repairing it. Do these six things, in this order. 1. Read the last 200 threads. A thread is one question with its replies. Read them the way a customer would. 2. Read the guidelines page. Guidelines are the rules for posting. Note whether anything on the site links to that page. 3. Read the last month of support mail. The support inbox is the mailbox where customers write when they need help. 4. List the ten questions that come up most. Write them in the customer's words, not in internal words. 5. Note every thread with no reply, and every thread with no accepted answer. The accepted answer is the one reply later readers should trust. 6. Find out who has staff rights, and why. Staff rights let a person edit, delete, or moderate posts. Some of those names will be from years ago. Do not post an announcement this week. Do not reorganize the categories. A category is a named group of threads on one topic. Redesigning in week one is the mistake to avoid. An odd category may exist because one large customer asked for it. A quiet board may be quiet because the product shipped a fix. You cannot yet see which mess is load bearing. Load bearing means it holds weight, even when it looks untidy. ## Week one, meet three people Reading tells you what happened on the forum. Three short talks tell you why. Meet whoever answers support mail. Meet whoever owns the product. Meet one customer who posts often. Twenty minutes each is enough. Ask all three the same thing. Ask what this forum gets wrong. Write down the answers as they say them. Do not defend the forum in these talks. You did not build it. One complaint will come up in all three conversations, and that one is real. ## Week two, answer what is waiting Week two is answering. Clear the unanswered threads, oldest first. Answer in public, on the thread, where the next reader will find it. A short correct answer today beats a long one next week. If you need to check something, say on the thread that you are checking. Come back the same day when you can. Then mark the reply that solved the problem. The asker or a staff member marks one reply as the accepted answer. It pins under the question, and the thread shows as solved. A solved thread is a page the next customer can follow without reading everything. This is also the fastest way to learn the product. You will hit the same gaps your customers hit. Members learn your name at the same time, because your name is now on the answers. Time yourself while you do it. Write down how many minutes an average answer takes. That number sets what you can promise later. If ten answers took two hours, you know what a daily 15 minutes will cover. ![The questions list in a Forumcat dashboard, showing each question with its status](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/11-questions-light-1788188151847-compressed.png) _Week two is this list, oldest first, until it is empty._ ## Week three, fix the small things Week three is for changes that cost nothing and break nothing. 1. Rewrite bad thread titles. A title should use the words a customer would type into search. A title like "Billing issue 3" helps nobody. 2. Merge or hide categories nobody uses. An empty category tells visitors that the place is unused. 3. Link the guidelines page from somewhere people actually look, such as the forum header or the posting page. 4. Write the five questions from your week-one list that still have no public answer. Those five answers are the real work of the week. Post each question in the customer's words. Write the answer. Mark it accepted. That is the same method as [seeding a new forum with your own questions](https://forumcat.com/blog/seed-a-new-forum), used on a forum that already exists. If new members currently arrive to nothing, a short greeting thread is another cheap fix. There is more on [what to put in a welcome post for new members](https://forumcat.com/blog/welcome-posts-for-new-members) once the answers are done. ![The categories and tags admin page in a Forumcat dashboard](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/13-taxonomy-light-1788501914288-compressed.png) _Tidy the categories in week three, not week one._ ## Week four, write down the routine and the numbers Week four turns the first three weeks into something repeatable. Start with the routine. The routine is what you do each day, in what order, and how long it takes. Write down who covers it when you are away. A small forum needs about 15 minutes a day, and [the daily routine for a customer community](https://forumcat.com/blog/running-a-customer-community) sets out that order. If the forum is a side duty for you, [how to moderate a forum part time](https://forumcat.com/blog/moderate-a-forum-part-time) covers the same work in less time. Then pick four numbers and record them. How many threads have no reply. How long a first reply takes. How many questions were asked this month. How many support replies linked to a public thread. Call this month your baseline. A baseline is the first measurement, the one later months are compared against. Write the four numbers on one page with today's date. A number you can compare next month is worth more than a longer report nobody reads. If you use Forumcat, three screens cover most of that. The questions list shows every question with its status. The members list shows who has posted. The analytics page shows question and view counts for a period. Five roles exist (owner, admin, agent, finance, member), so a new manager can get moderation rights without billing access. There is no reporting export and no connection to your analytics tool, so the baseline is a number you copy onto your own page by hand. A [hosted support forum](https://forumcat.com/support-forum) on a Forumcat subdomain is $9 one time, with a 7-day free trial and no card. ## What to leave until day 30 Some work is good work, later. None of it helps a forum that still has unanswered threads. Leave a rebrand. New colors do not answer a question, and the redesign will eat the month. Leave gamification. Gamification means points and badges for posting. Rewards need a crowd, and you do not have a crowd yet. Leave a member program. A member program names your best contributors, and in week two you do not know who they are. Leave an events calendar. An event needs people who already show up, so it comes after the answering habit. Leave a platform move. Moving tools in month one breaks the links you have, before you know what is actually missing. Leave the strategy document. Write it in month two, when your four numbers are real. ## How to tell month one went well A good first month looks quiet. Nothing dramatic happens. Every thread has a reply. You know the top ten questions by heart. Three regulars know your name and you know theirs. Four numbers sit on a page with a date on it. Nothing was rebranded. No categories were rebuilt. No one launched a program. That restraint is the result of the month. If one of those is missing, it is the first job of month two. Then compare the same four numbers at the end of it. Keep reading: [the daily routine for running a customer community](https://forumcat.com/blog/running-a-customer-community) and [how to build a customer community](https://forumcat.com/blog/build-a-customer-community). ## FAQs Q: What should a new community manager do first? A: Read. Spend week one on the last 200 threads, the guidelines page, and the last month of support mail. List the ten most repeated questions and every unanswered thread. Meet the support team, the product owner, and one frequent poster. Change nothing structural until you have done that. Q: What does a community manager do day to day? A: Most days it is answering new questions, marking the reply that solved the problem, and closing finished threads. After that comes checking searches that found nothing, so you know which answer to write next. On a small forum this fits in about 15 minutes. The larger jobs, such as programs and events, sit on top of that daily pass. Q: How long before a new community manager changes things? A: Wait two weeks before any structural change. Small fixes can start in week three: thread titles, unused categories, missing links, and the answers that do not exist yet. Bigger moves, such as a rebrand or a new platform, belong after day 30. By then you know which parts of the mess were holding something up. Q: What metrics should a community manager track first? A: Four are enough at the start. Unanswered threads, time to first reply, questions asked this month, and how many support replies linked to a public thread. Record them at the end of week four and call that your baseline. Compare the same four numbers each month. Q: Do I need a community strategy in month one? A: No. A strategy written before you know the top ten questions is a guess. Answer the backlog first, then write down the routine and the numbers. Month two is early enough for a plan, and by then it can point at something you measured. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## A support forum for an early-stage startup with a one-person support team Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: A support forum for an early-stage startup Meta Description: The one-person support playbook: what to set up first, what to skip until a trigger fires, and how a public forum keeps answers working while you build. URL: https://forumcat.com/blog/support-forum-for-startups Customer support for an early-stage startup needs three things. One address customers write to. One public place where answers live. One habit of answering repeat questions in public. That is the whole system at this stage. Skip the help desk, the chat widget, the saved replies, and the staffing plan until the volume forces them on you. A help desk is a tool that turns customer emails into tickets and assigns them. You do not need one yet. The rest of this post is the order to do things in, and what each step costs. ## Why one person changes the plan The person answering support is also building the product. Every minute spent typing the same answer twice is a minute not spent shipping. That is the argument for writing answers in public. The gain is where your hours go this week, more than any percentage of tickets avoided. Here is the arithmetic, with example numbers you should replace with your own. Say support takes eight hours a week today. Say half of those hours go to questions you have already answered for someone else. That is four hours a week. Four hours a week is a full working day every fortnight. Publishing the repeats is how you get that day back. The first customer to ask still costs you the ten minutes. The next twenty cost you a link. The numbers above are an example, not a measurement. Run yours for two weeks before you trust them. ## Step one, one address Every support channel points at one address. One mailbox, one place to look. Do not open live chat yet. Do not publish a phone number. Do not open a shared Slack channel per customer, which is a private chat room you and one customer share. Five channels with one person means four of them get ignored. An ignored channel is worse than a missing one, because the customer waited in it. Someone who cannot find chat will email you. Someone waiting in chat thinks you are rude. Put that one address on the site, in the app, and in your footer. Use a shared address like support at your domain, not your personal mail. Changing it later is annoying, and personal mail cannot be handed to a second person. ## Step two, answer everything within a day At this stage speed is the entire quality bar. A short correct answer today beats a polished one next week. Answer badly if you have to. "Yes, that is a bug, I am fixing it this week" is a good answer. So is "I do not know yet, I will write back Thursday." Both tell the customer where they stand. You can improve the wording later, when the same question comes back and you publish it. The first reply just needs to be correct and fast. Early customers forgive rough answers. They do not forgive silence. A four-day gap is what makes a small company feel unsafe to buy from. ## Step three, keep a tally of the repeats Every time you answer something for the second time, write the question down in the customer's words. Their words, not yours. If they wrote "how do I stop the emails", do not file it as "notification preferences". The customer's phrasing is what the next person will type into a search box. A text file is enough. Add a tally mark each time the question comes back. After two weeks you have a ranked list of what to publish. Do not hand this job to anyone else. The tally is product research. Five people asking how to cancel is a support fact. Five people asking where their data went is a product problem, and you want to read that list yourself. ## Step four, open a public place for the answers Open the public place once the tally has ten questions on it. Do not open it before then, and do not wait much longer. The place is a set of public pages, one per question, that anyone can read and search without an account. Customers ask in the open. You answer in the open. Each answered question stays up as a page the next person can find. Seed it with your tally. Seeding means writing those first threads yourself, from questions your inbox already answered. Ten to twenty solved threads and three to five categories is enough to go live. A category is a named group of threads, such as billing or getting started. Our post on [how to seed a new forum](https://forumcat.com/blog/seed-a-new-forum) walks through the writing part. ![The create a forum form in the Forumcat dashboard, filled in with a forum name and web address](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/03b-new-forum-filled-1788188160710-compressed.png) _Setup is the small part. The tally in step three is the work._ Mark the reply that solved each question as the accepted answer. The accepted answer is the one later readers should trust. It pins under the question, and the thread shows as solved. That is what makes a page usable by someone who was not in the conversation. ## Step five, route the repeats Routing means you point a repeat question at a public page instead of answering it only in email. When a repeat arrives, answer it in public first. Then reply to the person with the link and a line of context. You still helped them, and you left a page behind for the next one. Put the link where people already look. Your site menu, your email signature, and the auto-reply your mailbox sends when someone writes in. This habit takes about a week to build and it is the part that compounds. Answering in email only is where the four hours go. Answering in public is the same work with a page at the end of it. This is the whole idea behind [customer self-service](https://forumcat.com/customer-self-service). ## What to skip until later Skip anything whose job is coordination. You are one person, so there is nothing to coordinate yet. Skip the help desk until two people answer support, or until you lose track of a thread and a customer has to chase you. Those are the two triggers. When one of them happens, read [what to check before you buy help desk software](https://forumcat.com/blog/before-you-buy-help-desk-software) first. Skip live chat until someone is reliably online during posted hours. Chat sets an expectation of minutes. Breaking it costs you more than never offering it. Skip saved replies until you send the same answer daily. Below that, writing the reply fresh is faster than finding the template. Skip the status page until you have had a second outage. A status page is a public page showing whether your service is up. One outage is an email to the affected customers. Skip the chatbot. At your volume it will answer worse than you do, and the questions it fails on still land in your inbox. ## What breaks first as you grow The first thing that breaks is an unanswered question sitting in public. A forum with old unanswered threads reads worse than no forum. A visitor sees a question from March with no reply. They conclude that writing to you is pointless, and they leave. Answer everything, or do not open the place. If you go on holiday, say so in a pinned post. If a question needs a week, reply and say a week. Keep one view of unanswered threads and check it daily. On a one-person team that check takes a couple of minutes, and it is the only recurring duty the forum adds. ![A Forumcat portal filtered to solved questions, showing a short list of answered threads](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/01-home-sort-solved-1788188145446-compressed.png) _Twenty solved threads is enough to open with._ Forumcat is one way to run that public place. A portal is live in about five minutes and there is nothing to install. It costs $9 one time on a Forumcat subdomain, which is an address like yourcompany.myforumcat.com. A custom domain and higher caps are $99 a month, and the trial runs 7 days with no card. Customers read and search without an account, and sign-in is a magic link, a six-digit email code, or Google. The setup for [a hosted support forum](https://forumcat.com/support-forum) is close to the same for a SaaS product, and there is a separate post on [a support forum for SaaS](https://forumcat.com/blog/support-forum-for-saas). Forumcat does not do two things. It is not a ticketing system, and it does not take email in, so customer emails still land in your inbox as they do today. It sits beside whatever mailbox you use rather than replacing it. Keep reading: [how to seed a new forum](https://forumcat.com/blog/seed-a-new-forum) and [what to check before you buy help desk software](https://forumcat.com/blog/before-you-buy-help-desk-software). ## FAQs Q: Do I need a help desk as a startup? A: Not while one person answers everything. A mailbox handles it, and a help desk mostly adds routing and assignment you do not need yet. Buy one when a second person joins support, or when a thread slips and a customer has to chase you. Q: When should a startup open a support forum? A: Open it when the same ten questions have arrived twice each. Before that you have nothing to seed it with, and an empty forum looks abandoned. Ten to twenty solved threads is enough to go live. Q: How should an early-stage startup handle customer support? A: Use one address for everything, answer within a day, and keep a tally of the questions you answer twice. After two weeks, publish that tally as public answers and send repeat askers the link. That system holds until two people are answering support. Q: How much time does support take for a one-person team? A: It varies by product, so measure your own for two weeks. Count the hours, then count how many of them went to questions you had answered before. That second number is the part publishing answers can give back to you. Q: What support tools should a startup skip? A: Skip live chat until someone is reliably online, saved replies until you send the same answer daily, and a status page until your second outage. Skip the chatbot at this size. Each one adds a promise you then have to keep. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## Forum vs FAQ page: which one scales support Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Forum vs FAQ page: which one scales support Meta Description: A FAQ page answers the ten questions you predicted. A forum answers the ones you did not. The signs you have outgrown the page, and how both coexist. URL: https://forumcat.com/blog/forum-vs-faq-page An FAQ page is faster to build and easier to keep tidy. A forum scales further, because customers add the questions you did not think of. Keep the FAQ page for the ten questions every buyer asks. Use a forum for everything else. Most sites need both. FAQ means frequently asked questions. A forum is a set of question pages with public replies. This post covers what each one is good at, the signs that one page is no longer enough, and how the two work side by side. ## What each one is An FAQ page is one page you write. A forum is many pages your customers start. An FAQ page lives at a single web address. You pick the questions. You write the answers. You choose the order they appear in. Nothing shows up on it unless you put it there. A forum works the other way. A customer posts a question in their own words. Your team posts the answer in public. Each question gets its own page, called a thread. A thread is one question with its replies under it. The difference is who writes the question. Most of what follows comes from that one difference. ## What an FAQ page is good at An FAQ page is the fastest way to answer the questions a buyer asks before paying. You can publish one in an afternoon. It is a page on the site you already have. There is nothing to set up and nobody to invite. It is also easy to control. Every answer sits in one place. You can read the page top to bottom and fix the wording in one sitting. When a price changes, you edit one page and you are done. It fits well next to a pricing table. Buyers there have a short list of worries. Refunds, contract length, what happens when the trial ends. Six answers under the price handle those, and the reader never leaves the page. A short FAQ page is a good part of a site. The trouble starts when it is the only place answers live. ## Five signs you have outgrown one FAQ page You have outgrown the page when finding an answer on it is harder than emailing you. 1. The page is past about twenty questions. People scroll instead of scanning. 2. Customers still email you things the page answers. They could not find them. 3. You use the browser find command to edit it. That is Ctrl+F, and you are using it on your own content. 4. Two people on the team disagree about what belongs on the page. It has no clear edge any more. 5. Questions arrive that you would never have predicted. One page has no room for the rare ones. One or two of these is normal. Four or five means the page is doing a job it was not built for. ## One page is one web address One page is one web address, so twenty questions have to share it. A web address is the location of a single page. Your FAQ page has one. It has one page title, one main heading, and one place in search results. All twenty questions share that. A search engine reads the page as one thing. Someone searching for their exact problem lands at the top of a page about many topics. Then they have to hunt. Twenty threads are twenty pages. Each one has its own title, in the words the customer used. Each one can match a different search. Nobody has to scroll past nineteen other answers to reach the one they came for. This is also why the two grow differently. A forum can hold two thousand threads and still work, because nobody reads it as a list. An FAQ page has to be pruned to stay readable. Every answer you add makes the others a little harder to find. ![Search results in a Forumcat portal for the query webhook, listing several solved questions](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/03-search-webhook-1788188135310-compressed.png) _Twenty threads are twenty pages, each with its own title._ ## A forum collects the questions an FAQ page has to guess A forum hands you the real list of questions, written in the customer's words. When you write an FAQ page, you are guessing. You sit down and try to remember what people ask. Your team knows the product too well to guess accurately. You write the questions you wish people asked. A forum removes the guessing. Every posted question came from a real person with a real problem. The wording is theirs. It is close to what they would type into a search engine. You also get the questions nobody on your team would think to write down. Odd setups. Two features used together in a way you did not plan for. Problems that only appear after a month of use. That list is worth having outside support too. Five people confused by the same screen is a note for whoever builds the screen. Forumcat helps here in a small way. While a customer types a new question title, the portal suggests existing threads that already answer it. The long tail grows without the same question being posted five times. ![Related questions listed beside a thread in a Forumcat support portal](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/06-thread-related-questions-1788188148911-compressed.png) _The forum collects the questions an FAQ page has to guess._ ## What a forum costs that an FAQ page does not A forum needs a person, most working days. An FAQ page does not. Someone has to answer new questions within a day. A public question with no reply reads worse than no page at all. Visitors see it and decide nobody is home. Someone has to keep the titles readable. Customers write titles like "it broke" or "help please". Rewriting that into plain words takes a few seconds, and it is what makes the thread findable later. The first weeks look quiet. An empty forum helps nobody, so you seed it. Seeding means writing the first ten to twenty threads yourself, from questions your inbox already answers. None of that is heavy work. It is a daily habit rather than a project, and habits are the part teams underestimate. ## How to run both together Keep the FAQ page for the ten questions every buyer asks, and let the forum hold the rest. 1. Cut the FAQ page down to about ten questions. Pick the ones a buyer asks before paying, and the ones you would say out loud on a call. 2. Add a plain link at the bottom of the FAQ page to the forum. Say what is over there, in a sentence. 3. Promote a thread when it has been asked for the fifth time. That question is now common, so it belongs on the FAQ page. 4. Retire an FAQ entry when it stops being asked. Take it off the page and leave the answer in the forum, where search can still find it. The FAQ page stays short. The forum keeps growing. Neither one has to do the other's job. If you want the forum side to carry weight in search, look at how the answers are published. In a Forumcat portal, every answered public question ships QAPage structured data. That is extra code telling a search engine the page is a question with an accepted answer under it. Search covers every question and answer, which is what keeps the long tail usable as it grows. You can see the shape of that on the page for [a hosted support forum](https://forumcat.com/support-forum). Two limits. Forumcat does not replace your FAQ page, and we would not suggest deleting it. There is also no widget to embed a thread inside your page, so the connection between the two is a plain link you add yourself. ## Where a knowledge base fits A knowledge base sits between the two. It is a set of articles your team writes, one page per topic, filed under categories. It has the control of an FAQ page and the room of a forum. It also carries the cost of both, because your team writes every page. That comparison has its own post, so we will not repeat it here. Read [knowledge base vs community forum](https://forumcat.com/blog/knowledge-base-vs-community-forum) for the full version, and the page on [alternatives to knowledge base software](https://forumcat.com/alternatives/knowledge-base-software) if you are picking a tool this week. Keep reading: [how a self-serve forum cuts support tickets](https://forumcat.com/blog/cut-support-tickets-self-service-forum) and [how to reduce repeat questions](https://forumcat.com/blog/reduce-repeat-questions). ## FAQs Q: How many questions belong on an FAQ page? A: About ten, and rarely more than twenty. Past that, readers scroll and stop finding things. Use the count as a prompt to move the rare questions somewhere with more room. Q: Can an FAQ page and a forum work together? A: Yes, and that is the usual setup. The FAQ page answers the common questions and links into the forum at the bottom. The forum holds the long tail. Questions move up to the FAQ page when they get common, and back down when they go quiet. Q: Should I have an FAQ page or a forum? A: Have both, in most cases. Keep the FAQ page short and aimed at buyers, with the ten questions that come up before someone pays. Put everything else in the forum, where each question gets its own page. If you can only run one this month, run the one you can keep current. Q: When should I move my FAQ to a forum? A: Move when the page is past about twenty questions, or when people still email you things it answers. Do not move the whole page. Keep the ten questions everyone asks where they are, and let the rest live as threads. Q: Are FAQ pages good for SEO? A: An FAQ page can rank, and a short one on a pricing page is useful. The limit is structural. One page holds one title and one place in search results, so it cannot match many different searches at once. Separate pages, each titled in the words someone searched, cover more ground. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## Anonymous questions in a customer forum: when to allow them Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Anonymous questions in a customer forum Meta Description: When anonymous questions help, when they hurt, and the middle option most support teams want: a signed-in asker with a private thread. URL: https://forumcat.com/blog/anonymous-questions-in-forums Allow anonymous questions in a customer forum when the topic is embarrassing or risky for the person asking. Require a name on every other question. A customer forum is a public question-and-answer site on your website. Customers ask, and your team answers. For most support forums, use a private question instead. A private question is a thread only the asker and your team can read. The person signs in to post it. Other customers never see it. ## Anonymous, a made-up name, and private are three different things People mix these up. They use "anonymous" for all three. Fully anonymous means no account and no name. An account is a sign-in tied to an email address. Nobody on your team knows who asked. The person can leave, and you cannot write back. A made-up display name is different. A display name is the name shown next to a post. The person has an account and picks a name that is not their real name. You still have their email, so you can follow up. Other customers see the made-up name, not the email. A private question uses a real account, and the thread stays hidden from other customers. A thread is one question with its replies. Only the asker and staff can read it. Staff means the people on your team who answer. You know who asked. The rest of the board never sees the post. Most people who ask for an anonymous forum want this private option. They want the question kept off the public list. They are less worried about your team knowing who they are. A [customer portal](https://forumcat.com/blog/what-is-a-customer-portal) can offer public threads and private ones. Public means anyone can read. Private means only the asker and staff can read. ## What anonymous asking buys Some questions are hard to ask under a real name. People ask about billing trouble, a mistake they made, a security worry, or a question that sounds too simple. Those are real questions. Other customers often have the same one. A clear public answer can help many readers. If the person will not ask when their name is on the post, you never get that answer written. Embarrassment is the usual reason. The customer thinks the question makes them look careless. They may not want coworkers to see it. They may worry that a public post will stay tied to their name. That fear is reasonable. A public [support forum](https://forumcat.com/support-forum) is visible. Google can find it. A later employer can find it. A teammate can find it. ## What anonymous asking costs Spam and abuse arrive with no cost to the sender. Spam is junk posts. Abuse is insults, threats, or posts meant to hurt someone. When posting takes no account, sending junk is easy. Someone can post again from a new browser in a minute. You cannot follow up. There is no email to write to. If you need a screenshot or a log, you have no way to ask. You cannot check whether the person is a customer. A customer is someone who pays you or uses your product. An anonymous post can come from anyone, including a rival or a person with no account. You cannot mark the thread solved in a useful way. Solved means the question has an accepted answer. The accepted answer is the one reply later readers should trust. The asker or staff marks it. A thread with no asker rarely gets that mark, so later readers have to guess which reply to follow. Moderation work goes up. Moderation is the work of checking posts and removing the bad ones. Anonymous rooms need more of that work. ## Why a support answer often cannot go to an anonymous asker Support answers often need account detail. Account detail means facts that belong to one person, such as a plan name, an invoice, a login, or a shipping address. You should not put those facts on a public page. You also should not put them in a thread when you do not know who is reading. An anonymous asker cannot receive that kind of answer safely. You have no proof it is them. You have no private way back to them from that thread. The reply is often "please contact us." That outcome is worse than the email they skipped. They still have to write in. You still have to answer in private. The forum thread did not help them, and later readers learn that the forum cannot finish this kind of question. If the question is general, a public answer still works. "How do I change the card on file" does not need a name. "Why was I charged $40 on March 3" does. Keep the general how-to public. Move the personal case to a signed-in private thread, or to your help desk. A help desk is the private ticket tool your team already uses. The forum sits beside it. [Q&A software](https://forumcat.com/qa-software) is built so one public answer can help the next person. It does not replace the help desk for one person's account. ## Where anonymous posting does fit Anonymous posting fits some rooms that are not customer support. An internal employee forum is one of those rooms. People at the company may need to raise a problem without putting their name on it. Health and safety topics also fit. Health and safety means injuries, near misses, or unsafe gear at work. A whistleblower channel is a place to report serious wrongdoing without using your name. Research and feedback collection can use anonymous replies too, so people speak more freely about a product or a process. Those are different products from a customer support forum. The job, the risk, and the follow-up are all different. Do not copy their rules onto a public customer board and expect the same result. If you need a confession board or a student vent space, pick a tool built for that. A customer forum is for questions about your product. Your team answers. The next customer can find the page. ## Sign in, then keep the thread private Most people who ask to post with no name want two things. They do not want a hard sign-in. They do not want other customers to read the post. You can do both of those and still know who asked. Require a sign-in that is quick to finish. A magic link is a sign-in link sent to email. A six-digit email code is a short number sent to the same address. Google sign-in uses the Google account they already have. None of these ask the person to invent a new password. A password is a secret word they would have to create and remember. That removes most of the reason people ask to be anonymous. They are usually trying to skip the extra work and to keep other customers from seeing the post. Your team knowing who asked is a smaller part of what they want. ![The Forumcat sign-in page offering a magic link, a six-digit email code, and Google](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/40-anon-signin-page-1788501908388-compressed.png) _Signing in without inventing a password removes most of the reason people ask to be anonymous._ When the content is personal, let the thread be private. Personal means it names an account, a payment, a bug in one workspace, or a mistake the asker does not want on the public board. The person still signs in. Only they and staff see the thread. You can follow up, check they are a customer, and mark an accepted answer. The rest of the board stays public, so general how-to questions stay findable. That split is the usual design in a [private vs public community](https://forumcat.com/blog/private-vs-public-community) for support. ![The ask form in a Forumcat portal with the note explaining that a question can be made private](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/10f-ask-category-private-note-1788501897492-compressed.png) _Most askers want a private thread, and they can have one._ Forumcat does not have anonymous posting. Anyone can read and search without an account. Asking needs a sign-in by magic link, six-digit email code, or Google. There are no passwords. A question can be marked private so only the asker and staff see it. If you need true anonymous posting, Forumcat is not the tool. ## Five rules if you still allow anonymous questions Some teams still want a true anonymous option. If your tool allows it, write these rules down and use them. Hold new anonymous posts for review. Review means a staff member reads the post before other people can see it. Do this every time. Anonymous posts are easy to send in large numbers, so a person should look at each one. Never accept account changes from an anonymous thread. Account changes include a new email, a password reset, a refund, a plan change, or a deletion. You cannot prove who is asking. Send those requests to a signed-in private thread, or to your help desk. Publish what anonymous means on your forum. Put a short note near the ask form. Say whether staff can see an email, whether the post is public, and whether you can write back. People use the word "anonymous" for all three kinds above. Tell them which kind you offer. Keep a rate limit. A rate limit is a cap on how many posts one person can send in a short time. It will not stop a determined abuser. It will stop a casual flood. Say that abuse ends the option for everyone. If anonymous posting is used to harass, spam, or post other people's private data, turn it off. Write that in the same note. Then do it if you have to. Keep reading: [what a customer portal is](https://forumcat.com/blog/what-is-a-customer-portal) and [how to run a customer community](https://forumcat.com/blog/running-a-customer-community). ## FAQs Q: Should customers be able to ask questions anonymously? A: Allow it when the topic is embarrassing or risky for the asker. Require a name on other questions. For most customer support forums, use a private question. The asker signs in, and only they and staff see the thread. Q: What is the difference between anonymous and private questions? A: An anonymous question has no account and no name. Nobody on your team knows who asked. A private question has a signed-in asker. Only that person and staff can read the thread. Other customers cannot see it. Most people who ask for anonymity want a private question. Q: Do anonymous forums get more spam? A: They make spam and abuse easier to send, because the sender needs no account. You also cannot follow up, and you cannot check that the person is a customer. Moderation work goes up. A rate limit and review before a post goes live cut some of that. They do not remove it. Q: Can you give a support answer to an anonymous user? A: You can give a general how-to. You should not give account detail, because you cannot prove who is reading. Threads like that often end with "please contact us," which sends the person back to email. Use a signed-in private thread when the answer needs their account. Q: What is a low-friction way to sign in? A: Low-friction means the person can finish sign-in without much work. Send a magic link or a six-digit code to email, or let the person use Google. None of those need a new password. Pair it with a private-thread option so the question stays off the public board. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## How to reduce repeat questions with a searchable answer base Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: How to reduce repeat customer questions Meta Description: Find the questions you answer twice, write each answer once, put it where people search, and route the next asker to it. A loop, not a project. URL: https://forumcat.com/blog/reduce-repeat-questions Find the questions you answer more than twice. Write each one as a public page, in the customer's words. Make those pages searchable. Link to them when the same question arrives again. The same question over and over stops when the answer is easier to find than it is to ask for. You do not need a research team. You need last month's support mail, a notepad, and a place the next person can search. ## What an answer base is An answer base is a set of public pages. Each page answers one real question. Anyone can search those pages without an account. A help center is a set of articles grouped by topic. The unit in an answer base is a question, like "card declined". People type those words into search. They find pages that start with the same words. The pages have to be public. If a later customer cannot open them, you will type the same answer again. Reading and search should not require a login. Sign-in can wait until someone wants to post. Those public pages are [customer questions and answers](https://forumcat.com/customer-questions-and-answers) living where later people can find them. Each thread is one question on one page, with one trusted reply. ## Find the questions that repeat Open last month's support mail. Support mail is every message customers sent to your help address. Walk through it with a notepad. Mark each question you answered more than twice. Twenty minutes with a notepad is enough for this step. You already know the repeats. This pass is only to write them down. Write each line in the customer's words, not your product's words. Write "card declined". Do not write "payment method update failure". People type the first phrase, and they do not type the second. Group near-matches on one line when the answer is the same. "My card was declined", "payment failed", and "charge did not go through" are one group. Keep the wording that showed up most. Stop when you have a list. Ten lines is plenty for a first pass. You will add more later from searches that found nothing. ## Count what each repeat costs Pick one line on the list. Count how many times it arrived in a week. Multiply by the minutes you spend on one reply. Say 30 mails a week ask the same thing, and each reply takes ten minutes. That is 300 minutes a week, which is five hours for one question. Do this for each line. Rank the list by that number. Do not rank by how annoying the question feels. A short, polite question that arrives 30 times costs more than a long, rare one. Write the hours next to each line. That number tells you what to write first. Start at the top. ## Write the answer once Take the highest line. Turn it into a public page. Title it in the words a customer would type. "How do I fix a declined card" is a title. "Payment troubleshooting" is a filing label. People search for the first one. Write two or three sentences as the question body. State the problem the way the customer stated it. Then write the full answer in plain steps. Name the buttons and the screens, and say what success looks like. Mark one reply as the accepted answer. The accepted answer is the one reply later readers should trust. It pins under the question, and the thread then shows as solved. A solved thread is a page a later customer can follow without guessing. Strip account numbers, names, and emails before you publish. The next reader needs the steps. They do not need someone else's details. If the case is only about one account, keep it private. A private question is visible to the asker and staff only. Public pages are for answers that help the next person too. ## Make the pages findable Writing the page is not enough. If nobody can find it, the next customer will ask you the same question. Three things make a page findable. The title uses the customer's words. The page is public, so search engines can read it. The search box on your own site covers it. Search engines are the tools, such as Google, that people use before they write to you. If the page is locked, those tools cannot show it. If the title uses your internal name for the problem, the search will miss it. The search box on your site has to cover every question and every answer. A title-only search misses the useful words that live in the reply. ![Search results in a Forumcat portal for the query webhook, listing solved questions](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/03-search-webhook-1788188135310-compressed.png) _Search has to reach every answer, not only the titles._ If you already run [a hosted support forum](https://forumcat.com/support-forum), this is the job it is for. Each answered thread is a page, and search has to reach it. ## Send people to the page, then write what search missed When the same question arrives again, answer it in public first, then send the person the link. You still helped them. You also left the page in front of the next person. Put the link in your auto-reply. An auto-reply is the automatic message your mail tool sends when someone writes in. One line is enough. Tell them they can search past answers at that address, and that the accepted reply is the one that worked. Put the same link in your email signature, and in the help menu on your site. Those are the three places customers already look. Do this every time the question comes back. The habit is what turns pages into deflection. Deflection means the person finds the answer and does not open a new ticket. A page with no link in front of it will sit unused. This is the same work as [cutting support tickets with a self-service forum](https://forumcat.com/blog/cut-support-tickets-self-service-forum). The public page holds the answer. Sending the link is what makes people use it. After you have a few pages, watch the searches that return nothing. Those are empty searches. An empty search is a query that found no useful thread. The person already typed the words they use. Write that question next, in those words. Then write the answer and mark it solved. This research costs nothing. You do not guess what to document. The failed search tells you exactly what to write next. If your tool does not show empty searches, keep a running note. Add a line when you or a teammate cannot find an answer. That list is the same signal. Say three people a week search for "change the card on file" and find nothing. Each then emails you, and each reply takes ten minutes. That is 30 minutes a week on one missing page. One public thread, titled in those words, does that job after you write it once. ## What does not cut the repeats A longer FAQ page does not cut the repeats. An FAQ page is one long list of questions on a single web address. People cannot search one item on that list. Search engines treat the whole page as one document. A canned reply does not cut the repeats either. A canned reply is a saved snippet you paste into email. Some teams call this a macro. A canned reply makes each repeat cheaper to answer. It does not make the repeat rarer. You still receive the mail, open it, and paste the snippet. A knowledge base article that nobody links to has the same problem. A knowledge base is a set of help articles your team wrote. The article can be correct. If customers cannot find it, and you never send the link, the mail still arrives. The longer split between articles and threads is in the [knowledge base vs community forum](https://forumcat.com/blog/knowledge-base-vs-community-forum) comparison. A public searchable thread avoids those traps only if people can find it. Forumcat is a hosted Q&A portal on your domain. Search covers every question and every answer. While a customer types a new question title, the portal suggests existing threads that already answer it. That helps stop a duplicate before it is posted. A duplicate is a second copy of a question you already answered. ![A customer typing a question title in a Forumcat portal, with existing related questions suggested below the field](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/10c-ask-related-questions-1788501894974-compressed.png) _The duplicate is stopped before it is posted._ The asker or a staff member marks one reply as the accepted answer, and it pins under the question. Forumcat does not import your existing help articles. Import here means copying old articles in automatically. The first pass of writing is manual. There is no AI that writes the answers for you. AI here means software that tries to draft the reply. You still write the first answers. After that, the pages answer the next person who searches. Keep reading: [how a self-service forum cuts support tickets](https://forumcat.com/blog/cut-support-tickets-self-service-forum), the [knowledge base vs community forum](https://forumcat.com/blog/knowledge-base-vs-community-forum) comparison, and [forum vs FAQ page](https://forumcat.com/blog/forum-vs-faq-page). ## FAQs Q: How do I stop answering the same question over and over? A: Write the question as a public page in the customer's words. Make the page searchable. When the question arrives again, send the link. People stop asking you once finding the answer is easier than writing in. Q: What is an answer base? A: An answer base is a set of public pages. Each page answers one real question. Anyone can search them without an account. The unit is a question, not a topic. Q: How many repeat questions should I write up first? A: Start with the ones you already answered more than twice last month. Five to ten is enough. Rank them by hours spent, and write the top of the list first. Add more from empty searches after that. Q: Do canned replies reduce repeat questions? A: No, a canned reply makes each repeat faster to answer. It does not stop the mail from arriving. The question still lands in your inbox. A public, findable page is what cuts the count. Q: How do I know which questions repeat most? A: Open last month's support mail. Tally every question you answered more than twice. Write the tally in the customer's words. Rank by how many times it arrived, times the minutes per reply. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## Types of online communities, and which one cuts support tickets Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Types of online communities, and which cuts tickets Meta Description: The common types of online community, what each is for, and why only a public question-and-answer space cuts support tickets, even when others are busy. URL: https://forumcat.com/blog/types-of-online-communities Six types cover almost every online community: support and Q&A, product feedback, learning, brand and fan, professional networking, and peer discussion. Only one of them lowers your support volume. That is the support and Q&A type, where customers ask questions in public and the answers stay up as pages people can find later. The other five produce real value. None of it is fewer support emails. This post describes each type in the same shape, then explains why only one of them cuts tickets, and how to pick in one pass. ## The six types Each type below gets four lines: what it is, who it is for, what a good one looks like, and what it costs you to run. Running cost here means staff hours per week, not software price. ### Support and Q&A Customers ask questions in public, staff and other customers answer, and the answers stay up. It is for companies whose inbox gets the same questions every month. A good one looks like a list of question titles, each one a page, with one reply marked as the answer to trust. Running it costs the time you already spend answering, moved onto public pages, plus a few minutes a day of review. ### Product feedback People post ideas and vote on them, and the product team reads the list. It is for teams deciding what to build next. A good one looks like a short, sorted list where the team replies with a yes, a no, or a not now. Running it costs product time, because a feedback board with no replies stops collecting feedback. ### Learning Courses, lessons, and groups of people going through material together. It is for anyone teaching a skill, including companies teaching their own product. A good one runs on a schedule, with a start date and a finish. Running it costs the most of the six, because someone has to teach. ### Brand and fan People who like the thing talk to each other about it. It is for products with an identity people enjoy being seen with. A good one has regulars who post without being asked. Running it costs steady presence from someone on your team, most days, for a long time. ### Professional networking Peers in one field who want to meet each other. It is for industries where introductions carry value, such as recruiting or specialist services. A good one looks like a member directory plus conversations that lead to direct messages. Running it costs membership work: approving people, making introductions, and keeping the standard high. ### Peer discussion General conversation around a topic or an industry, not tied to one company's product. It is for the person who wants a gathering place rather than an answer desk. A good one has a few threads a day and regulars who set the tone. Running it costs moderation, which means reading new posts and removing what does not belong. ## Archive or conversation, the dividing line The useful split is what a community leaves behind. Some produce a searchable archive. Some produce conversation that expires. An archive is a set of pages with titles, each holding one topic. A person can search it a year later and find a specific answer. Chat rooms and scrolling feeds do not leave that behind. The talk happens, it helps whoever was there, and it slides out of reach. A community that cuts tickets is one whose output is a findable page. That is the test to apply before you pick a type or a tool. ![The home page of a Forumcat portal listing questions, with the Ask button highlighted](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/00-home-ask-hover-1788188154841-compressed.png) _The support and Q&A type: a list of questions, each one a page._ ## Why the support and Q&A type cuts tickets This type lowers volume for three reasons, and all three come from the same place. The questions arriving are the same questions your inbox already gets. Nobody has to invent topics. The answers are written by people who know the product, so a reader can act on them. Each answered thread keeps answering after that, without anyone touching it again. Here is made-up arithmetic you can check against your own inbox. Say 30 emails a week ask the same thing. Say each reply takes ten minutes. That is 300 minutes a week, which is five hours. One public thread with that title does the same job after you write it once. Substitute your own two numbers. The count of repeat emails per week, and the minutes one reply takes. Multiply them, then divide by 60 for hours. That is the time one answered thread is working against. ## Why the other five do not lower support volume The other five types are worth running. They are worth running for other reasons. Feedback communities produce a roadmap, which is the list of what you plan to build. Learning communities produce completions, meaning people who finished the material. Brand communities produce affection, and people who like you tell other people. Networking communities produce introductions between members. Peer discussion communities produce a place people want to come back to. None of that is deflection. Deflection means a customer got their answer without writing to you. A busy feedback board can even raise your ticket count, because people who post ideas also ask questions. The type is doing a different job. ## Running one space with two jobs Most companies want more than one of these. That is fine, with one rule: one space has one job at a time. You can run a support and Q&A community and still take feedback in it. Keep them in separate categories, where a category is a named group of threads on one topic. Someone looking for how to change their card should not scroll past twelve feature ideas to reach it. Two jobs mixed into one list means neither list scans. A person scanning for an answer gives up quickly. A product manager scanning for ideas gives up too. Separate the shelves and both readers find what they came for. ![A Forumcat portal filtered to the billing category](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/02-home-category-applied-billing-1788188157700-compressed.png) _One space, one job, sorted by the words customers use._ The same rule applies to who can see what. Some companies run one public space for answers and one members-only space for deeper talk, which is covered in [public and private communities compared](https://forumcat.com/blog/private-vs-public-community). ## How to pick in one pass Pick by the outcome you want first, then shop for software. The type decides the tool, not the other way around. If your inbox has the same twenty questions every month, pick support and Q&A. If you want to know what to build next, pick product feedback. If you want people to meet each other, pick professional networking. If you are teaching something, pick learning. If you want a place people enjoy being, pick brand or peer discussion, and plan for the weekly presence that takes. Write the choice down in one sentence before you look at any [community platform](https://forumcat.com/community-platform). Then judge each tool against that sentence. Skip this step and a community can end up busy and useless at the same time. Forumcat is built for the first type only. It is a hosted public question and answer portal on your own domain or a Forumcat subdomain. Customers ask, staff answer, and the asker or a staff member marks one reply as the accepted answer, which pins under the question. Search covers every question and answer. Every answered public question ships QAPage structured data, which is extra code telling a search engine the page is a question with an accepted answer. Forumcat does not do chat, courses, or feedback boards. If you want a hangout, pick something else from the list above. If you want [a support forum](https://forumcat.com/support-forum) where repeat questions turn into pages, that is the job it does. A portal on a Forumcat subdomain is $9 one time, with a 7-day free trial and no card. Keep reading: [how to build a customer community](https://forumcat.com/blog/build-a-customer-community) and [a Discord alternative for customer communities](https://forumcat.com/blog/discord-alternative-for-customer-communities). ## FAQs Q: What are the main types of online communities? A: Six types cover almost everything: support and Q&A, product feedback, learning, brand and fan, professional networking, and peer discussion. Longer lists usually split these into narrower groups, such as event communities or advocacy communities. The names matter less than the outcome each one produces. Pick the outcome you want, and the type follows. Q: Which type of community reduces support tickets? A: The support and Q&A type. Customers ask real questions in public, staff answer them, and each answered thread stays up as a page people can search. The questions are the ones your inbox already gets, so no topic has to be invented. The other five types produce value of a different kind. Q: What is the difference between a support community and a brand community? A: A support community exists to answer questions, and its output is an archive of solved threads. A brand community exists so people who like the product can talk to each other, and its output is affection and word of mouth. Support communities are measured by what people find. Brand communities are measured by who keeps coming back. Q: Can one community do more than one job? A: Yes, if each job gets its own space. Run support questions in one set of categories and feature ideas in another. Mixing them into one list makes both harder to scan, so the person hunting for an answer and the person hunting for ideas both give up. One space, one job at a time. Q: How do I choose a community type? A: Look at what you want more of in six months. Fewer repeat emails points to support and Q&A. A clearer build order points to product feedback. Members who know each other points to networking. Write that sentence down before you compare software, because the type decides which features matter. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## What a support ticket really costs: the math Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: What a support ticket really costs: the math Meta Description: Work out your own cost per ticket in ten minutes: pay, minutes per ticket, tools, and the repeat questions nobody counts. Arithmetic you can check. URL: https://forumcat.com/blog/cost-of-a-support-ticket Cost per ticket is your fully loaded support cost for one month, divided by the tickets your team handled that month. Fully loaded means salary plus payroll costs plus tools. That is the whole formula. Your own number is the only one that belongs in your budget. Working it out takes about ten minutes, and this post shows every line so you can check it. Every figure below is a made-up example input. It is labelled as one. Swap in your own numbers as you read. ## Why this post uses no outside numbers Published cost-per-ticket ranges come from companies of different sizes, with different channels and different definitions of a ticket. A number built on someone else's definitions cannot be defended in your budget meeting. So there is no benchmark here and no industry average. There is a method, and the arithmetic is on the page. ## What counts as one ticket A ticket is one customer request that a person on your team has to handle. Count requests, not messages. An email thread with four replies is one ticket, not four. A phone call is one ticket. Two customers with the same problem are two tickets, because two people had to be helped. Write your definition down before you count. Then use the same definition every month. A number that moves because the definition moved is not useful. ## Step one, add up what support costs The top of the fraction is everything you spend to answer customers in one month. Add these four things: 1. The salary of everyone who answers customers, for that month. 2. Payroll costs on top of salary. Payroll costs are the extra amounts an employer pays per person, such as taxes, insurance, and benefits. 3. The tools the support team uses that month, such as your help desk and your phone system. 4. The share of an engineer's or a founder's month that goes to support. If someone spends half their month on support, count half their cost. If a developer loses one day a week to escalated questions, that is one fifth of their month. An escalated question is one a support agent has to hand to someone more technical. Include the founder's time even though it feels free. It is usually the most expensive hour in the company, because nobody else can do what that hour was meant for. ## Step two, count the tickets in the same month The bottom of the fraction is the number of tickets handled in the same month you just priced. If you run a help desk, the report is already there. A help desk is the tool that turns customer emails into tracked tickets. If you work from a shared mailbox, count the threads instead. Use the same month on both sides. A cost from March over a ticket count from June produces a number that means nothing. ## Step three, do the division Here is the example. One person answers support. They cost the company 5,000 for the month, including payroll costs and tools. They handled 500 tickets in that month. The arithmetic runs like this. - Support cost for the month: 5,000 - Tickets handled that month: 500 - 5,000 divided by 500 = 10 The cost per ticket in this example is 10, in whatever currency you pay people in. Put your own two numbers in those two lines and you have your figure. If two people answer support, add both of their costs on the top line. The method does not change. ## The cost of one minute The per-minute cost is more useful than the per-ticket cost, because it prices any single question. A full-time month is roughly 160 working hours. That is about 40 hours a week across four weeks. Keep using the same example numbers. - 5,000 divided by 160 hours = 31.25 per hour - 31.25 divided by 60 minutes = about 0.52 per minute - A ticket that takes 20 minutes: 20 times 0.52 = about 10.42 Now you can price a specific question instead of an average one. Time three real replies with a stopwatch. Multiply the minutes by your own per-minute figure. ## What your repeated questions cost Repeats are the line you can act on. Take your five most repeated questions. For each one, count how many tickets it caused last month. Then estimate the minutes one reply takes. Stay with the example. Say 40 tickets a month ask how to change the card on file. Say each reply takes 15 minutes. - 40 tickets times 15 minutes = 600 minutes - 600 divided by 60 = 10 hours - 10 hours times 31.25 per hour = 312.50 That is about 310 a month for one question. Over twelve months it is about 3,750. Repeat the calculation for the other four questions and you have the price of your top five repeats. ![The questions list in a Forumcat dashboard, showing each question with its status](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/11-questions-light-1788188151847-compressed.png) _The repeated questions are the ones worth pricing._ These are made-up inputs, and the method is the point. Your ticket counts and your minutes will be different. The shape of the answer usually is not. ## What the formula misses, and what lowers the number The formula prices staff time. It misses four costs that are real and hard to measure. The customer waiting is one. The answer nobody wrote down is another, because the next person has to work it out again. The third is the same reply written twice by two different people. The fourth is the sale that never happened, because someone could not find an answer at 11pm and closed the tab. No numbers go on those four. Naming them is enough for a budget conversation. The number falls when the ticket count falls. Cutting handle time works for a while and then stops, because a careful reply takes the minutes it takes. Answering a repeated question once, in public, has no such floor. The page you wrote in March is still answering in November, at no extra cost per reader. That is the case for [customer self-service](https://forumcat.com/customer-self-service), which means letting people find the answer themselves instead of writing to you. Forumcat is one way to do that. It is a hosted public question and answer portal on your own domain or a Forumcat subdomain. Customers ask in public, your team answers, and each answered thread becomes a page people can search and find. A portal on a Forumcat subdomain is $9 one time. A custom domain and higher caps are $99 per month. There is a 7-day free trial and no card. ![A solved question in a Forumcat portal with the accepted answer pinned under the question](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/06-thread-solved-1788188139254-compressed.png) _One answer, written once, at the top of the page for good._ Forumcat does not handle tickets and does not connect to your help desk. It does not measure your cost per ticket either. It works on the bottom of the fraction, by cutting how many tickets arrive. If you want the fuller version of that argument, see [how a self-service forum cuts support tickets](https://forumcat.com/blog/cut-support-tickets-self-service-forum), and the page on [running a support forum](https://forumcat.com/support-forum) for what the setup involves. The share of questions answered without a ticket has its own measure, covered in [how to measure ticket deflection rate](https://forumcat.com/blog/ticket-deflection-rate). Keep reading: [what to check before you buy help desk software](https://forumcat.com/blog/before-you-buy-help-desk-software) and [how to cut support tickets with a self-service forum](https://forumcat.com/blog/cut-support-tickets-self-service-forum). ## FAQs Q: How do you calculate cost per support ticket? A: Take your fully loaded support cost for one month and divide it by the tickets handled in that same month. Fully loaded means salary, payroll costs, tools, and the share of any engineer or founder time that went to support. Use the same month on both sides of the division. The result is your cost per ticket. Q: What should be included in support costs? A: Include salaries, payroll costs such as taxes and benefits, and the tools the support team uses. Include the fraction of an engineer's month spent on escalated questions. Include founder time, even though it feels free. Leaving those out gives you a number that looks good and cannot be defended. Q: Why do published cost-per-ticket numbers vary so much? A: They come from different company sizes, different channels, and different definitions of a ticket. One source counts an email thread as one ticket, another counts each reply. Some include tools and some do not. Ranges built on different definitions cannot be compared, which is why your own number is the one to use. Q: Does self-service lower cost per ticket? A: It lowers the total cost more reliably than it lowers the cost per ticket. Public answers cut the number of tickets that arrive, especially the repeated ones. Your cost per ticket may even rise, because the easy tickets are the ones that stop. Track total support cost and ticket count together, not the ratio alone. Q: What is a good cost per ticket? A: There is no single good number, and any figure quoted without your definitions attached is not comparable. Measure your own number, then watch which way it moves over six months. A falling ticket count on a steady cost is the sign worth chasing. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## Private vs public community: what you gain and lose Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Private vs public community: gains and losses Meta Description: What a private community gives you, what a public one gives you, and the middle option for support teams: public by default, private per question. URL: https://forumcat.com/blog/private-vs-public-community An online customer community can be public or private. A public one is readable by anyone, including search engines. A private one sits behind a login, so only members get in. For customer support, public usually wins, because one answer keeps helping the next person who has the same problem. Private wins when named members need to talk candidly. Most support teams want public threads with the option to make one question private. This post explains what each model gives you, what each one costs you, and how to pick. It is about software for customers, not about social networks. ## What public and private mean here Public means a visitor can read and search the community without an account. They arrive from a search engine or a link, open a thread, and read the answer. A thread is one question with its replies. No sign-up screen stands in the way. Private means every page requires a login. A person has to be invited, or approved, before they can read anything. Search engines see nothing, because a search engine cannot log in. Most communities still ask people to sign in before they post. That is normal in both models. The difference is reading, not posting. Put one test to any tool you look at. Check whether a stranger can read a thread without an account. ## What you gain with a public community A public answer keeps working after you write it. That is the whole case for public, and it is a strong one. One reply can serve hundreds of readers over a year. The customer who asked reads it once. Everyone with the same problem reads it later, at whatever hour they are stuck. You wrote it once, in office hours, and it answers people while you sleep. Public pages can be found in search. Somebody types their problem into a search engine and lands on your answer. They never open your contact form, because they did not need to. New customers can read before they buy. Someone deciding on your product can see how questions get answered and how fast. Prospects reading your support answers is a good thing. A prospect is a person thinking about buying from you. Honest answers in public build more confidence than a page of claims. ![A Forumcat portal as a signed-out visitor sees it, listing questions with a sign-in link in the corner](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/40-anon-home-1788501903071-compressed.png) _Public means this page loads before anyone logs in._ Public also lowers the cost of every future answer. Each solved thread is a page you can link the next time the question arrives. Over a year, that pile of pages does real work. The same argument applies to answering in [public instead of by private email](https://forumcat.com/blog/public-answers-beat-private-email). ## What you lose with a public community Public costs you privacy, and you should count that cost with open eyes. Nothing on the forum is confidential. Anything a customer pastes can be read by anyone, including detail they did not mean to share. Complaints are visible. An unhappy customer writes in public, and the thread sits there while you work on a fix. Your competitors read it. They will see your bugs, your gaps, and the questions your product raises most often. Bad answers are visible too. A wrong or rushed reply is on a page anyone can find. The honest counter is that a support inbox has the same complaints. They are just hidden from you and from everyone else. A public complaint with a good public answer often reads better than silence. You lose the ability to keep problems quiet. The problems were already there. ## What you gain with a private community Private buys you candor. Candor means people say what they really think, because the room is small and everyone in it is known. Behind a login, people share things they would never post to the open web. They paste account numbers, revenue figures, and screenshots of internal tools. They complain in front of peers instead of in front of search results. They ask questions they would be embarrassed to ask in public. That is worth a lot for specific groups. A beta group testing unreleased features needs to talk about things you have not announced. A beta is an early version given to a few customers. A paid member group, a partner program, and a customer advisory council all work the same way. An advisory council is a small set of customers who meet to give feedback on your plans. Those rooms have a real job. The job is trust among a named few. ## What you lose with a private community A private answer helps one room, once. It never builds up into anything. Nobody finds it in search, because search engines cannot log in. It does not lower your support volume, because the people who email you are not in the room. It dies when the member leaves, because the next customer with that question will never see it. There is an ongoing cost too. Someone has to create accounts, send invitations, and chase people who never accepted them. Someone has to review access, which means checking who still belongs there when jobs change and contracts end. That work is small each week and constant forever. ## The middle option most support teams want Public threads by default, with the ability to make one question private, covers almost every support case. Here is the split in practice. The question about how refunds work is public, because it helps everyone. The question about this customer's refund on invoice 4471 is private, because it is one person's business. Private at the thread level means visible to the asker and staff only. The rest of the forum stays open to the web. Nobody else sees the thread, and a search engine never indexes it. Index means a search engine stores the page and can show it in results. ![A private question in a Forumcat portal as a staff member sees it, marked private](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/06-thread-private-staff-1788501892480-compressed.png) _One thread can be private while the rest of the forum stays public._ Used well, this keeps the public side clean. Account detail leaves the open pages. The answers that help strangers stay where strangers can find them. Most teams choosing [a customer community platform](https://forumcat.com/community-platform) are really looking for this shape. ## How to choose, in three rules Three rules settle almost every case. If the answer would help a stranger, make it public. Billing rules, setup steps, error messages, and product limits all fit here. Write them once in the open. If the answer contains one customer's data, make it private. Account numbers, invoices, personal addresses, and anything about their specific plan belong out of public view. If almost every answer contains one customer's data, you want a help desk, not a forum. A help desk is a tool that handles private one-to-one cases through email or a portal. Some businesses genuinely have no repeatable public answers. Their questions really are all individual. A forum will stay empty for them, and that is a fair reason to skip it. ## Where Forumcat fits, and where it does not Forumcat is public by default. A portal is a public question-and-answer site on your own domain or a subdomain. Customers read and search it without an account. Asking a question needs a sign-in, by magic link, six-digit email code, or Google. A magic link is a sign-in link sent to email, so nobody invents a password. A question can be made private, so only the asker and staff can see it. That covers the account-specific case described above. Forumcat is not built for a fully closed member community. The public, searchable pages are the point of it. If you need every page gated to invited members, pick a different tool. If you want [a hosted support forum](https://forumcat.com/support-forum) that is public with private questions where they are needed, that is the shape Forumcat has. It is $9 one time on a Forumcat subdomain, with a 7-day free trial and no card. Keep reading: [how to build a customer community](https://forumcat.com/blog/build-a-customer-community) and [a Discord alternative for customer communities](https://forumcat.com/blog/discord-alternative-for-customer-communities). ## FAQs Q: What is the difference between a public and a private community? A: A public community can be read and searched by anyone, with no account. Search engines can find its pages and show them in results. A private community requires a login on every page, so only invited or approved members see anything. Both usually ask people to sign in before posting. Q: Should my customer community be public or private? A: For customer support, public is the better default. Answers you write once keep helping people who arrive later from search. Choose private when the point of the room is candid talk among a named few, such as a beta group or an advisory council. Many teams run public threads and mark individual questions private when they involve one customer's account. Q: Is a private community better for support? A: Usually not. Support questions repeat, and a private answer helps only the people already in the room. It never reduces the number of emails you get, because the people emailing you are outside. Private is better for confidential feedback, not for answering the same question many times. Q: Can a community be part public and part private? A: Yes, at the level of a single question. A thread can be visible to the asker and staff only, while the rest of the forum stays open to the web. That is different from a private area for a group of members, which is a separate feature that not every tool offers. Q: Do private communities help SEO? A: No. SEO means getting your pages to show up in search results. A search engine cannot log in, so it never sees pages behind a login. Only public answers can appear in search results. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## How to moderate a customer forum without a full-time moderator Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Moderate a forum without a full-time moderator Meta Description: A fixed review routine for one person with a few minutes a day, plus plain rules for when to edit, close, make private, or remove a post. URL: https://forumcat.com/blog/moderate-a-forum-part-time A customer forum with a few new posts a day needs one person for about fifteen minutes, once a day. Read the new posts. Take out any private data. Fix titles nobody would search for. Answer what you can answer. Close exact duplicates and leave a link to the original. Mark solved threads solved. Everything else can wait until tomorrow. Moderating means deciding what stays, what gets fixed, and what gets taken down. This post covers those decisions, the order to make them in, and the cases that are harder than they look. ## What moderating a support forum means Moderation here is three decisions: what stays as it is, what gets fixed, and what gets removed. A customer support forum is easier to moderate than a social community. People arrive with a problem. They want it solved, and then they leave. Long arguments are rare, because nobody came to argue. That changes the work. Most of your time goes on making threads findable. Very little goes on policing behavior. A thread is one question with its replies, on a public page. The next customer has to find that page and follow it. The daily routine for the whole forum is a separate job. Answering, marking threads solved, and checking searches that found nothing are covered in [running a customer community in 15 minutes a day](https://forumcat.com/blog/running-a-customer-community). This post stays on the judgment calls. ## The daily pass, in order Do the pass once a day, in a fixed order. The first steps are the ones that cannot wait. 1. Open the list of unanswered questions. Unanswered means no staff reply yet, or no accepted answer yet. 2. Read the new posts oldest first. The person who waited longest gets your attention first. 3. Remove any private data you see. That means account numbers, invoice numbers, home addresses, and screenshots showing an email address. 4. Fix titles that nobody would search for. 5. Answer anything you can answer. Pass the rest to the person who can. 6. Close exact duplicates. Always leave a link to the original thread. 7. Mark solved threads solved. The accepted answer is the one reply later readers should trust. It pins under the question. ![The questions list in a Forumcat dashboard, showing each question with its status](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/11-questions-light-1788188151847-compressed.png) _The daily pass starts with one list._ On a quiet day this takes ten minutes. On a busy day it takes twenty. If you run out of time, stop after step five. The unanswered person matters more than a tidy list. ## Use the smallest action that fixes the problem Pick the lightest action that solves what is actually wrong. A heavier action costs you trust, and it rarely helps the next reader. Edit when the post is fine and the title is not. Leave the words of the question alone. Change the title to what a customer would type. If you edit anything inside the body, say so in a short line at the end. Reply in public when the rule is worth teaching. Someone posts a support question in the wrong category, or pastes three questions into one thread. A calm public reply teaches the pattern to everyone reading. Three short rules on a page cover most of it, and there is [a community guidelines template](https://forumcat.com/blog/community-guidelines-template) if you want a starting point. Close when the question is answered elsewhere, and always leave the link. Closing means the thread is finished and leaves the open queue. People can still read it. A close with no link reads as a door shut in someone's face. ![Staff tools on a Forumcat thread, showing options to pin and close the question](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/11-thread-staff-toolbar-1788501900184-compressed.png) _Closing with a link to the original is the common case._ Remove when there is private data, spam, or abuse. Removal is for content that should not be on a public page at all. It is not for a post you disagree with. Suspend only for the same behavior a second time. Suspend means the person cannot post for a while. Say what the rule was the first time. If they do it again, act, and tell them why in one plain sentence. ## Fixing bad titles is the highest-value edit The title is what the next person searches, so a bad title wastes a good answer. "Help!!" tells a later reader nothing. "Card declined when updating billing" tells them everything in six words. The answer inside both threads can be identical. Only one of them will be found. Rewrite the title in the words a customer would type. Use the words from the body of their post. Keep the customer's own phrasing where you can, because that is the phrasing other customers will use. This edit takes about ten seconds. It turns one answered question into a page that keeps answering. Do it for every new post, before you write your reply. ## Private data cannot wait a day Private data is the one thing you fix the moment you see it. Everything else on this list can wait until tomorrow's pass. Watch for account numbers, invoice numbers, order numbers, phone numbers, home addresses, and API keys. An API key is a secret string that lets software sign in as that customer. Screenshots hide a lot of this. Check the corners of an image for an email address or a name. Edit the detail out. Then tell the person why, in one short public line. Most people are grateful. They pasted the whole screen because they were stuck, not because they wanted it public. Then move the detail somewhere private. On Forumcat, a question can be made private, so only the asker and staff can see it. The other route is email. A [customer support portal](https://forumcat.com/customer-support-portal) works best when the public part stays free of one person's account details. ## The hard cases Four situations come up often enough to plan for. None of them needs a policy document. An angry customer who is right gets answered first, and in public. Do not move the thread to email to make it quiet. Say what went wrong, say what you are doing, and give a date if you have one. Other readers are watching how you handle it, and a fair public answer is worth more than a hidden one. A public bug report stays public. Confirm you can reproduce it, or ask for the one detail you need. Post back on the same thread when it is fixed. People search for the bug, so the fix should live where they will look. A competitor posting is usually harmless. If the post is a real question, answer it like any other. If it is an advertisement, remove it as spam. Do not argue with them on the thread. A member who answers everything and is often wrong is the delicate one. Thank them in public, then correct the facts, never the person. Write the correct answer as a normal reply. Mark the correct reply as the accepted answer, so later readers follow that one. ## What to skip, and when one person is not enough Skip real-time monitoring. A support forum does not need someone watching it all day. Once a day is enough at this size. Skip approval queues. An approval queue holds every post until staff release it. It turns a forum into a form, and the delay teaches people to email you instead. Post first, review after. Skip building a moderation team you do not need. One named owner beats three people who each assume another will look. One person stops being enough at three signs. The first is more than about twenty new posts a day. The second is customers in a second time zone waiting overnight. The third is a week when you are away. The fix is a second person with staff rights, not a longer rulebook. On Forumcat, staff can pin a thread, close it, and mark the accepted answer. Five roles exist (owner, admin, agent, finance, member), so a helper can be given staff rights for this routine. A question can be made private when it holds account detail. There is no approval queue, so posts appear first and a person reviews them after. A [hosted support forum](https://forumcat.com/support-forum) on a Forumcat subdomain is $9 one time, with a 7-day free trial and no card. Keep reading: [running a customer community in 15 minutes a day](https://forumcat.com/blog/running-a-customer-community) and [how to set up a customer support forum](https://forumcat.com/blog/how-to-set-up-a-customer-support-forum). ## FAQs Q: How much time does moderating a forum take? A: For a customer forum with a few new posts a day, plan about fifteen minutes, once a day. Most of that time goes on titles, duplicates, and marking threads solved. Busy days take twenty minutes. If the daily pass regularly runs past thirty minutes, add a second person with staff rights. Q: What should a forum moderator remove? A: Remove private data, spam, and abuse. Private data means account numbers, invoices, addresses, and screenshots that show an email address. Remove an advertisement posted as a question. Do not remove a complaint, a bug report, or a post you disagree with. Q: Do I need a moderation team for a small forum? A: No. One named owner doing a daily pass is enough for a small support forum. People arrive with a problem, so bad behavior is rare. Add a second person when volume grows, when a second time zone starts waiting overnight, or when you take a week off. Q: Should I approve posts before they appear? A: Approving every post before it appears adds a delay to a question someone asked because they were stuck. That delay teaches people to email you instead. Let posts appear, then review them in the daily pass. Remove the rare post that should not be public. Q: How do you handle an angry customer in public? A: Answer them first, and answer on the thread. Say what went wrong, say what you are doing about it, and give a date if you have one. Do not move the conversation to email to make it quiet. Other readers judge you by that reply more than by any of your calm ones. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## Ticket deflection rate: how to measure it and what is good Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Ticket deflection rate: how to measure it Meta Description: One formula for deflection rate, what it cannot see, and how to judge a good number against your own baseline month. No borrowed benchmarks. URL: https://forumcat.com/blog/ticket-deflection-rate Ticket deflection rate is the share of people who needed help and got it without opening a ticket. Take the help-seekers who did not write in, divide by all help-seekers, and multiply by 100. Count people who were looking for help, not page views. There is no published benchmark worth chasing, because the numbers you find are measuring different populations. The figure that matters is your own baseline month and the direction it moves after that. This post gives one formula, explains both sides of it, and says what the number cannot see. It quotes no third-party figure at all, and the reason for that is below. ## What ticket deflection means Ticket deflection means answering a question before it becomes an email. The customer had a problem, found the answer on a public page, and never wrote to you. A ticket is one customer request that a person on your team has to handle. It usually arrives as an email, a chat, or a form. Each one costs staff time, which is why teams try to answer common questions in public first. That work is called [ticket deflection](https://forumcat.com/use-cases/ticket-deflection). Deflection does not mean turning people away. The customer still gets the answer, from a page instead of from a person. ## How to calculate the rate The formula is one line. Deflection rate = help-seekers who did not open a ticket, divided by all help-seekers, times 100. A help-seeker is someone who searched your help pages or opened your forum with a problem. Somebody who read your pricing page is not a help-seeker. Somebody who typed "reset password" into your help search is one. Here is how to count each side. 1. Pick one calendar month. Use whole months, because support volume moves through a month. 2. Count help-seekers. Use searches on your help pages and forum, plus visits to a help article or a thread from search results. 3. Count tickets opened in that month by people who fit the same description. 4. Subtract the tickets from the help-seekers. That is the top of the fraction. 5. Divide by all help-seekers and multiply by 100. Set one counting rule before you start. The same person, with the same problem, in the same week, counts once. Without that rule, a frustrated customer who searched nine times looks like nine people. Say 1,000 people searched your forum or help pages in a month. Of those, 300 opened a ticket that month. That leaves 700 who did not. 700 divided by 1,000 is 0.7, which is 70 percent. Those figures are made up for the arithmetic, not measured from anything. ## Why published benchmarks do not help The benchmark numbers you find online are not comparable to each other. Vendors put different things on the top and the bottom of that fraction. One counts deflected contacts over attempted contacts. Another counts help-center visitors over people who opened tickets. A third counts sessions minus tickets, divided by sessions. Each is a defensible choice. Each describes a different group of people. Two rates that look identical can therefore mean unrelated things. One may count everyone who landed on a help page. The other may count only people who started writing a ticket and stopped. Comparing your figure to a stranger's is comparing nothing. That is why there is no benchmark in this post. Any figure quoted here would carry the same problem. Write down your own formula, keep it fixed, and compare your months to each other. ## What the number cannot see Deflection rate is a trend line. It does not measure how much value your help pages create. Some readers were never going to write in. They would have shrugged and moved on, or given up on the product quietly. Your pages helped them, and the formula treats them the same as a rescued ticket. Some people read the answer and wrote in anyway. Maybe the answer was unclear. Maybe they wanted a human to confirm it. They show up on the ticket side even though the page did its job. A page view is also not a solved problem. Somebody can open a thread, read two lines, and leave more confused. Nothing in the arithmetic knows that. So treat the rate as rough. Do not report it to two decimal places, and do not tie anyone's bonus to it. A move of several points across a quarter is a signal. A move of half a point in one week is noise. ## How to set a baseline Pick one month before you change anything, and write the number down. That is your baseline. Every later number is read against it. Then change one thing. Publish the ten answers your inbox repeats most, or add search to your help site. Changing three things at once means you learn nothing about which one worked. Read the number again after a full month, not after a week. Support volume moves with releases, billing dates, and holidays. A launch week and a quiet week give different numbers. Compare the same month next year, not last week. December against December tells you more than December against November. Keep the numbers in one sheet with a note on what you changed each month. ![The analytics page in a Forumcat dashboard showing question and view counts](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/10-analytics-light-1788188142296-compressed.png) _The top half of the fraction, one month at a time._ ## Three numbers that move earlier Deflection rate is slow. Three smaller numbers move sooner and are easier to trust, so watch these while the main figure catches up. The first is repeat tickets. Count the tickets this month that asked a question you have already answered in public. Every one of those is a page that people are not finding. The fix is usually the title, not the answer. The second is no-result searches. A no-result search is when someone typed words into your search box and found no matching page. That list is a to-do list written by your customers, in their own words. The third is linked answers. Count the support replies this month that linked to a public thread. That number shows whether your team is using the public answers they wrote. It also grows the deflection rate later, because each link teaches a customer that the answers live there. All three are countable by hand in an hour. None of them need a new tool. ## What raises the rate Four habits move the number, and none of them are technical. Answer in the customer's words. If people write "the card on file will not update", title the public answer that way. A title like "Payment method management" uses words nobody types. Keep one public thread per repeated question. Two threads on the same problem split the traffic and confuse search. Merge or close the weaker one. Show existing answers while somebody types a new question. Suggestions at that moment stop a repeat before it becomes a ticket. On Forumcat, the portal suggests existing threads while a customer types a title, and search covers every question and every answer. Link to the public answer in your email replies. Answer the person properly, then paste the link. The next person who searches will find that thread instead of writing to you. This also lowers what each request costs you, which the post on [the cost of a support ticket](https://forumcat.com/blog/cost-of-a-support-ticket) works through. ![Search results in a Forumcat portal for the query webhook, listing solved questions](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/03-search-webhook-1788188135310-compressed.png) _A search that finds an answer is a ticket that never gets written._ ## Where the numbers come from Be clear about which tool holds which half of the fraction. Getting this wrong is how teams end up with a number nobody trusts. The Forumcat dashboard has an analytics page with question and view counts. That covers the top half, the people who came looking for an answer. It is the view you would use to set a baseline month. The ticket side comes from your help desk. Forumcat is not a ticketing system and does not connect to one. There is no import, no sync, and no integration. You read the ticket count from your help desk and do the division yourself, in a sheet. That split is fine for a monthly number. It is a copy of two figures once a month, into one row. If you want the self-serve half of that setup, a [hosted support forum](https://forumcat.com/support-forum) on a Forumcat subdomain is $9 one time, with a 7-day free trial and no card. Keep reading: [how to cut support tickets with a self-service forum](https://forumcat.com/blog/cut-support-tickets-self-service-forum) and [what a customer portal is](https://forumcat.com/blog/what-is-a-customer-portal). ## FAQs Q: What is a good ticket deflection rate? A: There is no reliable public benchmark, because vendors calculate the rate differently. A number from another company is measuring a different population than yours. Set your own baseline month, keep the formula fixed, and judge yourself on the direction it moves. Steady growth over two quarters is a good result. Q: How do you calculate ticket deflection rate? A: Divide the help-seekers who did not open a ticket by all help-seekers, then multiply by 100. A help-seeker is someone who searched your help pages or opened your forum with a problem. Count the same person with the same problem once per week. Use whole calendar months on both sides. Q: What is the difference between deflection and resolution? A: Deflection counts people who got help without opening a ticket. Resolution counts tickets that were opened and then closed with an answer. Deflection is measured before a ticket exists, and resolution is measured after. A team can have strong resolution and weak deflection at the same time. Q: Why is my deflection rate hard to measure? A: Because the top of the fraction is a guess about intent. You cannot tell from traffic alone who needed help and who was browsing. Some people read an answer and write in anyway, and some would never have written in at all. Pick one definition, write it down, and stay with it. Q: How long before deflection rate changes? A: Give it two or three full months. New public answers need time to be found by search engines and by your own team. Repeat tickets and no-result searches move sooner, often within weeks, so watch those first. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## Community guidelines: a copy-paste template with examples Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Community guidelines: a copy-paste template Meta Description: Twelve short clauses for a customer forum, in plain words, with example wording you can paste and adapt. No legal voice. URL: https://forumcat.com/blog/community-guidelines-template Good community guidelines fit on one page. They say what the forum is for, what gets removed, and who decides. Twelve clauses cover a support forum: what the forum is for, be kind, one question per thread, searchable titles, search first, no private data, stay on topic, no spam, how staff answers work, what we edit or remove, how to disagree with a moderator, and where security and account problems go. Example wording for each clause is below. Copy it, change the words so they sound like your company, and publish it. Community guidelines are the rules for posting on your forum. Moderation is the work of applying those rules. The wording here is ours, written for a support forum. ## Why a support forum needs its own rules A support forum is different from a social community, so the usual community rules do not fit. People arrive with a broken product and a deadline. They want an answer. Most rule templates are written for membership groups and social communities. They cover tone, self-promotion, and staying friendly. Those clauses still matter here. They are not enough on their own. Two problems are specific to support. The first is private data. Customers paste invoice numbers, order numbers, and screenshots that show an email address. Once that sits on a public page, anyone can read it. The second problem is findability. Every thread is a page the next customer may land on. A thread is one question with its replies. Threads with two questions in them, or titles like "urgent help", are hard to find later. Half your rules exist to keep pages findable. That is the difference between rules for a [customer community](https://forumcat.com/customer-community) and rules for a social one. Yours protect private data and keep answers easy to find. ## The template: twelve clauses you can paste Each clause below has a short heading and example wording. Use the heading on your page. Edit the wording to match how your team speaks. ### 1\. What this forum is for Use this forum for questions about the product. Anyone can read the answers here, including people who are not customers. For anything about your own account or your bill, email support instead. ### 2\. Be kind, even when the product broke Something may be broken, and that is frustrating. Write about the problem, not the person. We answer faster when we can see what went wrong. ### 3\. One question per thread Post one question in each thread. If you have two problems, open two threads. Single-question threads are easier for the next person to find and follow. ### 4\. Write the title in the words you would search Write the title the way you would type it into a search box. "The save button does nothing on the billing page" works well. "Help please" does not help anyone find your thread. ### 5\. Search before you post Search the forum first. Your question may already have an answer. If you find a thread that is close but not the same, link to it in your post. ### 6\. Never post private data Do not post account numbers, invoice numbers, card details, or your home address. Check screenshots for an email address before you upload them. If we need your account details to help, we will ask you by email. ### 7\. Keep it about the product Posts should be about using this product. General industry chat, job posts, and news belong somewhere else. We close off-topic threads and say why. ### 8\. No spam, no affiliate links, no recruiting Do not post ads, referral codes, or affiliate links. Do not use the forum to recruit people. Links are welcome when they help answer the question. ### 9\. How staff answers work Staff replies show a role next to the name, so you can tell who works here. The person who asked, or a staff member, marks one reply as the accepted answer. That reply pins under the question and the thread shows as solved. Solved threads stay up, because the next person with the same problem needs them. ![A solved question in a Forumcat portal with the accepted answer pinned under the question and a staff role shown next to the name](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/06-thread-solved-1788188139254-compressed.png) _The accepted answer is what the rules point at._ ### 10\. What we edit, close, or remove We edit posts to take out private data. We close threads that are answered or off topic. We remove spam. When we do any of this, we say so in the thread. ### 11\. How to disagree with a moderator If you think we got a decision wrong, email us. Please do not argue about it inside the thread. We will explain the decision, and we change it when we are wrong. ### 12\. Security reports and account problems Do not post security problems in public. Email us instead and we will reply. Account and billing problems also go to email, because they need details that should stay private. ## How to write a clause Name the behavior, not the person. "Posts that include card numbers get edited" is a rule. "Do not be the kind of person who posts card numbers" is an insult. Say what to do, not only what to avoid. A rule that ends with a next step teaches. "Email support for billing" is more useful than "no billing posts". Keep each clause to one or two sentences. If a clause needs a paragraph, it is probably two clauses. Write in the same voice your team uses in email. Skip legal language. Your terms of service handle the legal side. Terms of service are the contract a customer agrees to when they sign up. Guidelines are house rules for posting, in plain words. ## Where the guidelines page lives Rules only work when people see them. Put the page where a person meets the forum for the first time. 1. Pin the page at the top of the forum, so it stays above the newest threads. 2. Link it from the form where someone writes a new question. 3. Link it from the auto-reply your mail tool sends when a customer emails support. 4. Link it from the footer of the forum, next to your terms of service. One page is enough. Do not split the rules across three places, because then nobody knows which page is current. ## How to enforce the rules Enforcement has five steps, from smallest to largest. Edit the post. Reply in the open. Close the thread. Remove the post. Suspend the member, which means they cannot post for a while. Use the smallest step that fixes the problem. Most rule breaks are accidents. Someone pasted an invoice number without thinking about who can read it. Say what you did and why, in the thread. "I removed the invoice number from this post, because the page is public." That one sentence teaches every reader, not only the person who posted. Silent edits look like censorship. Enforcement should stay small work. A quick daily pass over new posts is usually enough, and [moderating a forum part time](https://forumcat.com/blog/moderate-a-forum-part-time) covers how to keep it that short. ## When to update the page Update the page after the forum teaches you something. Three moments are worth watching for. The first moment is the first argument. When two people fight in a thread, you learn whether your tone clause is clear enough. The second is the first data leak. When someone posts an account number, check whether clause 6 says plainly what counts as private data. The third is any clause you had to explain twice. If two people read a rule the same wrong way, the rule is unclear. Rewrite it in their words. ![Staff tools on a Forumcat thread, showing options to pin and close the question](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/11-thread-staff-toolbar-1788501900184-compressed.png) _Closing a thread is usually enough. Removal is the last step._ Put a date at the bottom of the page, such as "Last updated 4 September 2026". Readers can then see the rules are current. ## What the software does for you Some clauses are easier to keep when the tool helps. On Forumcat, staff replies show the person's role next to the name, so clause 9 is true by default. The asker or a staff member marks one reply as the accepted answer, and it pins under the question. A question can also be made private, so only the asker and staff can see it. That is the practical answer to clause 6. When a customer needs to share an order number, the thread can hold it without becoming a public page. Your removal clause is still done by a person reading new posts. Any [hosted support forum](https://forumcat.com/support-forum) still needs someone to look at the board each day. Keep reading: [running a customer community](https://forumcat.com/blog/running-a-customer-community) and [how to set up a customer support forum](https://forumcat.com/blog/how-to-set-up-a-customer-support-forum). ## FAQs Q: What are community guidelines? A: Community guidelines are the posting rules for your forum. They say what the space is for, how people should treat each other, and what gets edited or removed. On a support forum they also cover private data and how staff answers work. They are written in plain words, not legal ones. Q: What should community guidelines include? A: Include what the forum is for and where other requests should go. Include tone, one question per thread, searchable titles, and searching before posting. Include a clear rule about private data such as invoices and card numbers. Then say what you edit, close, or remove, and who decides. Q: How long should community guidelines be? A: One page that someone can read in two minutes. Around twelve short clauses is enough for a support forum. Long rule pages go unread, and unread rules do not shape behavior. If a clause needs more detail, link to a separate page for it. Q: What is the difference between community guidelines and terms of service? A: Terms of service are the contract a customer agrees to when they sign up, and they are written by lawyers. Community guidelines are house rules for posting on the forum. Guidelines can change often and should read like a person wrote them. Link the two pages to each other. Q: How do you enforce community guidelines? A: Use the smallest step that fixes the problem: edit, reply in the open, close, remove, then suspend. Say what you did and why, inside the thread. Public enforcement teaches the rule to everyone reading, and it shows the rules are applied the same way each time. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## How to seed a new forum so it does not look empty Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-02 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: How to seed a new forum so it does not look empty Meta Description: Post the ten questions your inbox already answers, in the customer's words, and mark the accepted answers. A useful forum on day one, honestly. URL: https://forumcat.com/blog/seed-a-new-forum Seed a new forum with the ten to twenty questions your inbox already answers. Post each one in the customer's words. Answer it yourself. Mark the correct reply as the accepted answer. The accepted answer is the one reply later readers should trust. You then have a useful forum on day one, before a single visitor posts. Seeding means writing those first threads yourself, so the board already has answers when people arrive. A thread is one question with its replies, both on public pages. This post covers where the seed questions come from, how to write them well, and how many you need before you share the link. ## Write the first threads under your own name People launching a forum this week often worry that this looks fake. It is a fair worry. You are posting the question. You are also posting the answer. A visitor can see both names. The questions are real. A customer already asked them. You already answered them in mail. You are moving that work onto a page the next person can find. That work is documentation. Documentation means writing down what you already know, in a place later readers can use. Post under your own name. Answer as yourself. If your tool shows a staff role next to your name, leave it visible. A staff role is the job label beside the name, such as agent or admin. Official answers should look official. What would be fake is invented users. Do not make accounts that pretend to be customers. Do not write praise that nobody sent. Do not add fake replies to make the board look busy. Visitors notice names that never come back. Before you post, cut anything private. Remove names, email addresses, invoice numbers, and account IDs. Keep the problem and the steps. The next customer needs the method. They do not need someone else's details. ## Where the seed questions come from Start with the support inbox. The support inbox is the mailbox where customers write when they need help. Open last month. Write down the questions that showed up more than once. The ten most repeated questions are your first ten threads. Then open the mail you already sent. Look for answers you have typed twice. If you sent the same steps to two people, that answer belongs on the forum. Copy the steps. Rewrite them as a public reply. Strip the private parts. Sales calls are a third source. A sales call is a talk with someone who is thinking about buying. Those people are called prospects. They ask the same few things each week. How billing works. Whether two people can share a login. What happens if they cancel. Put those questions on the forum too. Prospects can read them before they write to you. Those [customer questions and answers](https://forumcat.com/customer-questions-and-answers) already sit in your mail and your calls. The forum is where they become pages other people can find. Once the forum is live, watch empty searches. An empty search is a query that found no matching thread. The visitor already typed the words they use. Write that question next. Answer it. Mark it solved. A solved thread is a question with an accepted answer. Say 15 emails a week ask how to change the card on file. Each reply takes ten minutes. That is 150 minutes a week on one question. One public thread, titled in those words, does that job after you write it once. ## How to write a seed thread A seed thread has four parts. The title. The question body. The answer. The mark that the answer is accepted. Write the title in the words a customer would type. A title like "How do I change the card on file" uses the words they would search. A title like "Billing FAQ 4" uses a label they would not type. The question body is two or three sentences. State the problem. State what they already tried, if you know. A customer wrote that they cannot change the card on the billing page. They tried the save button and saw an error. That is enough. The next reader wants to match their problem in a few seconds. The answer should be complete and plain. Name the page. Name the button. Name what should happen when it works. Stop when the job is done. Do not add extra sales language. Then mark the reply as the accepted answer. On Forumcat, the asker or a staff member marks it. The accepted answer pins under the question. The thread shows as solved. A solved thread is the unit of a healthy forum. One question. One trusted reply. A later reader can use it without guessing. ![A solved question thread in Forumcat with the accepted answer pinned under the question](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/06-thread-solved-1788188139254-compressed.png) _The unit of a healthy forum: one solved thread._ While a customer types a new question title, Forumcat suggests existing threads that already answer it. Your seed answers then show up at the moment someone is about to ask the same thing again. ## How many threads is enough Ten solved threads is the minimum. Twenty is comfortable. You can go live at twenty. You can add more later from empty searches and from new mail. Three to five categories is enough. A category is a named group of threads on one topic. Name the groups the way customers speak. Billing. Getting started. Using the product. Troubleshooting. Account. A forum with two empty categories looks worse than a forum with none. Empty shelves say nobody uses this place. A few filled shelves say answers live here. If you only have enough threads for three categories, make three. Do not open fifteen rooms and hope they fill. You can split a category later, when it is too long to scan. ![A Forumcat portal filtered to solved questions, showing a seeded board](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/01-home-sort-solved-1788188145446-compressed.png) _Ten solved threads read as a place answers live._ ## What to do in the first two weeks The seed gives visitors something to find. Sending people to the forum on purpose is what starts real use. That sending is called routing. Routing means you point a repeat question at a public thread, instead of answering it only in email. When a repeat question arrives by email, answer it on the forum first. Then send the person the link. You still helped them. You also left a page for the next person with the same problem. Put the forum link in three places. Your site menu. Your email signature. The auto-reply that goes out when someone writes support. An auto-reply is the message your mail tool sends as soon as a customer writes in. Those are the places customers already look. Answer anything new within a day. In the first two weeks, speed matters. A short, correct answer today helps more than a long one next week. You can come back and add steps later. If nobody posts for a few days, that is normal. Keep routing. Keep answering. The first real visitor question is the sign that people have found the room. ## What not to do Do not create fake accounts. Do not invent activity so the board looks busy. Do not write reviews of your own product in a customer's voice. Visitors notice. Your team notices too. Do not post engagement prompts into an empty room. An engagement prompt is a post that asks people to chat, such as a request to name a favorite feature. With no members, it sits there with zero replies. A quiet board of solved threads is easier to trust. Do not make fifteen categories on day one. Three to five filled shelves beat a long list of empty ones. Skip points, badges, and welcome campaigns until people already use the place. Those tools reward a crowd. You do not have a crowd yet. You have twenty answers and a habit of sending people there. A [hosted support forum](https://forumcat.com/support-forum) on a Forumcat subdomain is $9 one time. A subdomain is a web address like yourcompany.myforumcat.com. There is a 7-day free trial, and you do not need a card. Keep reading: [how to build a customer community](https://forumcat.com/blog/build-a-customer-community) and [how to set up a customer support forum](https://forumcat.com/blog/how-to-set-up-a-customer-support-forum), and [a support forum for an early-stage startup](https://forumcat.com/blog/support-forum-for-startups), and [welcome posts for new members](https://forumcat.com/blog/welcome-posts-for-new-members). ## FAQs Q: How do I start a forum with no members? A: Seed it with the questions your inbox already answers. Post ten to twenty of them in the customer's words. Answer each one. Mark the reply that worked. You then have a useful board before anyone else posts. Members arrive later, after they find those pages. Q: Is it okay to post questions on my own forum? A: Yes, when the questions are real. Use the words customers already sent you. Post under your own name. Answer as staff. Cut private details before you publish. Do not invent users or praise. Moving a real question onto a public page is documentation. Q: How many posts should a new forum have? A: Aim for ten solved threads at the low end, and twenty if you can. Pair them with three to five categories so no shelf is empty. A small board of solved threads looks used. A large board of empty rooms looks abandoned. Q: How do I get the first real members to post? A: Send people to the forum from your site, your email signature, and your auto-reply. When a repeat question arrives, answer it on the forum and send the link. Answer new questions within a day. The first real post is often a customer who already found a seed thread and now has a new problem. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## How to switch forum platforms without losing your rankings Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-02 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Switch forum platforms without losing rankings Meta Description: Rankings follow URLs. Map every old thread to its new home with permanent redirects and you keep most of what you earned. A calm, ordered plan. URL: https://forumcat.com/blog/switch-forum-platforms-keep-rankings Rankings follow URLs. A URL is the address of one page, like example.com/questions/refund-policy. Google builds its trust in those addresses, not in the software behind them. So if every old thread address points to its new home with a permanent redirect, you keep most of what you earned. If the old addresses stop working, the rankings on them go away too. The whole job is protecting the addresses that matter. Here is the plan, in order. ## Why moving a forum is not like moving a website Most migration guides talk about a site with thirty pages. A forum is not shaped like that. A forum that has run for a few years may have thousands of thread addresses. Each answered thread is its own page in Google's index. Each one can rank on its own for its own question. That changes the work. You are moving a large pile of small pages, and deciding what happens to each one. The helpful part is that the pages are not equal. A small share of threads usually brings most of the search visits. Find that share, protect it carefully, and the job gets much smaller. ## Step 1: make a list of every thread address Do this before you touch anything else. You need a full list of the addresses your forum publishes today. There are two easy ways to get one. Many forum platforms can export a list of thread URLs from the admin area. If yours cannot, run a crawler over the site. A crawler is a tool that walks your pages link by link and writes down every address it finds. Screaming Frog and Sitebulb are two common ones. Now add the traffic numbers. Your analytics tool shows visits per page. Search Console shows clicks from Google. Search Console is Google's free tool for site owners. It shows which of your pages get clicks from search, and for which searches. Export its page report for the last twelve months and match it to your URL list. Sort the result by clicks, highest first. Most forums find that a modest set of threads carries a large part of the search traffic. Those threads are the asset you are protecting. Everything below them is history, and you get to choose how much of it comes with you. ## Step 2: give every address one of three fates Go down the sorted list and mark each address with one of three choices. Do it in groups where the threads are alike, so the work stays sane. The first choice is redirect. The thread survives the move and lives at a new address on the new platform. You will point the old address at the new one. The second choice is re-create, then redirect. You write the question and the answer fresh on the new platform, because the content is worth keeping but the old post cannot be moved as it is. The new page gets a clean address, and the old thread points at it. The third choice is let it go. Dead threads with no visits and no useful answer do not need to travel. For those, the honest move is a "gone" status. That is a plain signal from your server saying the page was removed on purpose. It tells Google to stop checking back, and it does not harm the pages you kept. ## Step 3: redirect thread to thread with a 301 A 301 is a permanent redirect. It is a short instruction your server sends when a browser or a search engine asks for an old address. It means "this page moved here for good". Google follows it, and over time it moves the standing it gave the old address to the new one. This is not instant and it is not exact, but it is the mechanism that carries rankings across a move. Map each old thread to the page that answers the same question on the new platform. Thread to thread, one at a time. Resist the shortcut of sending a big group of old threads to your homepage. A redirect to a page about something else looks to Google like the old page was simply deleted. The old page's standing then has nothing to attach to. If a thread has no good match on the new side, return the gone status instead of pointing at the homepage. That is a cleaner answer. Keep the redirects running for years, not for a month. Other sites still link to your old addresses. People still have them in bookmarks and in old emails. Redirects are cheap to keep, and switching them off later undoes the work you just did. ## Step 4: set up the new side so Google can follow Give each question exactly one address on the new platform. If the same thread is reachable at two addresses, the signals split between them. When duplicates are unavoidable, use a canonical tag. That is a line in the page's code that tells Google which address is the real one when several show the same content. For threads you re-create by hand, keep the new title close to the old title. People searched with words that matched the old wording. Changing the question to something clever makes it harder to match. Then publish a sitemap and submit it in Search Console. A sitemap is a file that lists the pages you want search engines to find. Submitting it is a nudge, not a command, but it speeds up discovery of the new addresses. After that, watch and wait. Google recrawls a large forum slowly, page by page. The first few weeks usually look unsettled, with pages moving up and down while the old and new addresses swap places. Check the coverage report in Search Console to confirm the new pages are being indexed and the old ones are being redirected. Judge the outcome at two to three months, not at two weeks. ## Step 5: leave some things behind on purpose A move is the one good chance to get smaller. Take that chance. Years of off-topic chat rarely earn search visits, and they cost you time in the move. Threads with wrong or expired answers are worse than nothing, because a stale answer that ranks well sends bad information to customers. Old user lists are their own problem. People agreed to hear from your old forum, not from a new tool, so treat consent as something that does not transfer. Write the skip list down before you start. Otherwise the move quietly expands to cover everything, and it stalls. ## If you are moving to Forumcat Forumcat does not import content from other forum platforms. There is no importer, and there is no one-click move. Teams that switch re-create their best answered threads by hand, then redirect the old addresses to the new ones. That sounds heavy until you look at the list from step 1. The work is bounded by the threads that actually earn visits, which is usually tens of threads, not thousands. A person can re-create thirty good answers in a couple of afternoons. The rest of the old forum gets a gone status and stays in the past. On the domain side, a paid plan puts the portal on your own address, such as help.yourcompany.com, with the certificate that turns on the padlock handled for you. Once the custom domain is connected, the Forumcat subdomain redirects to it, and the canonical tags follow the custom domain. So the address you point your redirects at is the address Google treats as real. If you want the platform-specific notes before you commit, the [platform alternatives hub](https://forumcat.com/alternatives) covers what moving from each common tool involves. ![The custom domain settings page in the Forumcat dashboard](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/32-domain-light-1788265390790-compressed.png) _One real address for the portal, with the Forumcat subdomain redirecting to it._ Keep reading: [self-host or buy your customer forum](https://forumcat.com/blog/self-host-or-buy-your-customer-forum) and [how to set up a customer support forum](https://forumcat.com/blog/how-to-set-up-a-customer-support-forum). ## FAQs Q: Will I lose my Google rankings if I change forum software? A: Not automatically. Rankings sit on individual thread addresses, so what matters is whether those addresses keep working. Point each old thread at its new page with a permanent redirect and most of the standing carries over. You are likely to see some movement while Google recrawls, and pages usually settle within a few months. Q: How long do forum redirects need to stay up? A: Longer than most people expect. Plan on years, and treat "forever" as the default. Links from other sites, old bookmarks, and old emails keep sending people to the original addresses long after the move. Redirect rules cost almost nothing to keep in place. Q: Should I redirect old threads to my homepage? A: No. A redirect works when the new page answers the same question as the old one. Sending many unrelated threads to the homepage reads as a deletion, and the old pages' standing has nowhere to go. When there is no matching page, return a gone status instead and let those pages drop cleanly. Q: Do I need to migrate every old thread? A: No, and trying to is usually what makes a move fail. Move the threads that earn visits or answer questions customers still ask. Let the dead ones go. A smaller forum with current answers serves customers better than a large one full of stale threads, and it is far easier to keep accurate. Q: Where should the new forum live? A: Choose the address before you write a single redirect, because every redirect you write points at it. A subfolder or subdomain on your main domain is the usual choice for a customer-facing Q&A site. The pages on [hosted forum options](https://forumcat.com/forum-hosting) and on [running a support forum](https://forumcat.com/support-forum) walk through the trade-offs. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## A forum software requirements checklist Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-02 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: A forum software requirements checklist Meta Description: Judge forum software by five jobs: reading, asking, answering, moderating, and owning. The checklist to take into any trial or demo. URL: https://forumcat.com/blog/forum-software-requirements-checklist Judge forum software by five jobs: reading, asking, answering, moderating, and owning. Check each job while you try the tool. Do this before you compare brand names. Reading: a visitor can read and search without an account. Asking: a person can post in a few steps, and the tool shows answers that already exist. Answering: staff can mark one reply as the accepted answer. The accepted answer is the reply later readers should trust. Moderating: one person can review new posts in a few minutes a day. Owning: you can export your data, keep your links, and see how the price grows. Take this list into any trial. A trial is a period when you use the tool with your own questions. No vendor is ranked here, including ours. If you want names of tools, there is [a forum software roundup](https://forumcat.com/best/forum-software). Use these checks on those tools. ## Reading and search without an account Most people who visit will never post. They have a problem. They search. They want to read an answer. Open the tool without signing in. Try to search. Try to open a thread. If reading requires an account, many visitors will leave and email you instead. Check that search covers every question and every answer. Type a phrase from a real customer email. See if the matching thread appears. Open a thread on a phone. You should be able to read the replies without turning the phone sideways. Pages should load without a long wait. Use your own phone on ordinary wifi for this. Ask whether a search engine can index every public answer. A search engine is a tool like Google that lists pages. Index means it can find the page and show it in results. If answers sit behind a login, they will not show up there. Look at a thread with several replies. A reader needs a way to tell which reply is the right one. An accepted answer pinned under the question is one clear way. A solved mark on the thread is another. If every reply looks the same, the next person has to guess. Some tools add structured data to public answers. Structured data is extra code on the page. It tells a search engine the page is a question with an answer. Ask if the tool does this. ![Search results in a Forumcat portal for the query webhook, showing solved questions](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/03-search-webhook-1788188135310-compressed.png) _Reading and finding: the first job to test._ ## Steps to ask a question Count the steps from the home page to a posted question. Click the button to ask. Note whether an account is required first. Note whether you must pick a category, which is a folder for a topic such as billing. Extra fields count as steps too. Write the number down. A long path means fewer people will post. More of them will email you instead. While you type a title, watch for suggestions. Suggestions are existing threads shown before you post. If the same question already has an answer, the person can open that thread and stop. A duplicate is a repeat question. Duplicates take staff time. They also make search harder, because the same topic now lives in two places. Sign-in should not require a new password. A password is a secret word the person has to invent and store. Many tools send a magic link, which is a sign-in link in email. Some send a six-digit code to email. Some let the person use Google. Any of those beat a new password the person will forget. Do this as a customer would. Use a personal email, not the staff login you used to set the tool up. Time how long it takes. ![Related questions suggested next to a thread in a Forumcat support portal](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/06-thread-related-questions-1788188148911-compressed.png) _Duplicate suggestions stop repeat questions before they post._ ## Marking the accepted answer Staff need to write answers. They also need to mark which answer later readers should trust. Look for an accepted answer. The asker or a staff member marks one reply. That reply pins under the question. The thread then shows as solved. A solved thread is a page the next customer can follow without reading every reply. Staff replies should look different from customer replies. A role next to the name is one way. A role is a label such as agent or admin. Official answers then look official. If staff and customers look the same, people cannot tell which reply to follow. The team also needs one list of unanswered questions. Unanswered means no staff reply yet, or no accepted answer yet. If that list is missing, open questions hide. Someone has to hunt through the pile. These checks are the core of [Q&A software](https://forumcat.com/qa-software). Q&A software is built for one question with one trusted reply. The next customer should find that page. ## Moderating in minutes a day Moderating means reviewing new posts, hiding what should not be public, and keeping labels tidy. A support forum stays useful when this job stays small. Sit with the trial and time a review. Open the new posts. Read them. Answer or close the easy ones. On a quiet day this should take a few minutes. If the layout makes you click around, note the extra clicks. Some questions include account-specific detail. Account-specific means names, order numbers, or plan info that should not be public. The tool should let you make a question private. Private means only the asker and staff can see it. The rest of the forum stays public. You also need a way to suspend a member. Suspend means they cannot post for a while. A small support forum may still get spam. When it does, you need a clear action, not a hunt through settings. Categories and tags should be managed by staff. A tag is a short label on a thread. If every member can invent new labels, the list gets messy. Search then fails, because the same topic has three names. ## Domain, export, price, and links Owning means you can leave with your data, and you understand the bill. Ask whose domain the forum runs on. A domain is the web address people type, such as help.yourcompany.com. A vendor subdomain is an address the vendor owns, such as yourcompany.theirproduct.com. If you leave, a vendor address goes away. Your own domain can be pointed at a new host. Ask how you export your data. Export means you get a copy of every question and every answer. Ask what format the copy uses. Ask how long it takes to get it. You need a way to leave with a full copy. Ask what price rises have looked like for that vendor. Look at old pricing pages, old help articles, and public threads. The current price page shows today's price. It does not show past rises. You want to see whether the bill jumps after you depend on the tool. Ask what happens to your links if you leave. A link is the address of one thread. Search results and emails point at those addresses. If the addresses die, those results die. A custom domain plus a redirect plan keeps old links useful. A redirect is a rule that sends an old address to a new one. Ask whether the price grows with traffic, seats, or both. Traffic is how many people visit. A seat is an account for someone on your team. A working support forum collects more answers over time, so more people visit. If the bill tracks traffic, success makes the price rise. Write down which meter the vendor uses. ## How to run the trial Use real questions from your inbox. Do not type sample text and call it a trial. Copy about ten recent emails that ask the same things. Post them as questions. Write the answers your team already sent. Then search for those answers as a customer would. Invite one real customer. Ask them to find an answer and to post one question. Watch where they get stuck. Note where they pause or give up. Open the forum on a phone. Read a thread. Try to post. A large screen can hide problems that appear on a phone. Time the setup. Setup is the work from sign-up to the first public question. Write down the minutes. A demo is a walkthrough a vendor runs for you. A trial is you using the tool with your own mail. Two weeks with real mail is a better test than a demo. This checklist is also how we would want to be judged. Forumcat is a hosted Q&A portal. A Q&A portal is a public site where customers ask questions and your team answers. The reading, asking, and answering checks above describe what it does. Visitors can read and search without an account. While someone types a question title, the portal suggests existing threads. The asker or staff can mark one reply as the accepted answer. Staff replies show a role next to the name. A portal on a Forumcat subdomain is $9 one time. There is a 7-day trial and no card. You can try it against this list. The same offer is on the page for [a hosted support forum](https://forumcat.com/support-forum). Keep reading: [open source forum software compared](https://forumcat.com/blog/open-source-forum-software-compared) and [how to set up a customer support forum](https://forumcat.com/blog/how-to-set-up-a-customer-support-forum), and [a support forum for SaaS](https://forumcat.com/blog/support-forum-for-saas). ## FAQs Q: What should I look for in forum software? A: Look at five jobs: reading, asking, answering, moderating, and owning. Visitors should read and search without an account, and post in a few steps. Staff should mark an accepted answer and review new posts in minutes a day. You should be able to export your data, keep your domain, and see how the price grows. Q: How do I run a forum software trial? A: Use real questions from your inbox, not sample posts. Invite one real customer, and open the forum on a phone. Time the setup from sign-up to the first public question. Two weeks with real mail is a better test than a vendor demo. Q: What forum features matter most for customer support? A: Look for features that help the next customer find an answer. Those include search without an account, suggestions while typing, and an accepted answer that pins under the question. Staff roles on replies, a list of unanswered threads, and private questions for account details also matter. Extra discussion tools matter less when the job is support. Q: Should forum pricing grow with traffic? A: It can, but you should know before you start. Traffic is how many people visit. A useful support forum gains visitors as answers pile up, so a traffic-based price rises as the forum works. Write down whether the vendor charges for traffic, for staff seats, or for both. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## Open source forum software: a calm comparison Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-02 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Open source forum software: a calm comparison Meta Description: Discourse, Flarum, NodeBB, phpBB, and MyBB, compared by the job you have and the upkeep each one asks of you. No ranking, no star counts. URL: https://forumcat.com/blog/open-source-forum-software-compared The five names you will see most are Discourse, Flarum, NodeBB, phpBB, and MyBB. All five are free and open source, and all five are good software. Discourse is the fullest of the group and the heaviest to run. Flarum and NodeBB are lighter and feel more modern. phpBB and MyBB are the long-lived classics, and they run on cheap shared hosting. There is no single best one. The right pick depends on the job your forum has to do, and on who will keep it running after launch. Here is the detail, one project at a time. ## The five names you will keep seeing Each of these is a real project with real people behind it. Some are run by companies, some by volunteers. All of them have carried large public communities for years. ### Discourse Discourse is a discussion platform made by the company of the same name. It is open source under the GNU GPL, so you can run it on your own server without paying for a license. It runs on Ruby on Rails, with PostgreSQL as the database and Redis alongside it. The official way to install it uses Docker, which keeps those pieces together in one bundle. Running it is the heaviest job of the five. It will not sit on a basic shared PHP host. You want a server you control, with enough memory for those services. In return you get a lot in the box, including trust levels that give steady members more ability over time, and email replies that work like a mailing list. Discourse also sells official hosting for people who would rather not run it. Its pricing page listed plans starting at $100 per month when we checked in September 2026. Teams tend to pick Discourse when they want a serious public community and have someone who can look after a server. ### Flarum Flarum is forum software written in PHP. It is free and open source, and the core is kept deliberately small. Extensions add the rest, so you choose what your board can do. The reading experience is one flowing page. Discussions are flat rather than deeply nested, which keeps long threads easy to follow. To run it you need PHP, a MySQL or MariaDB database, and a web server. Plenty of shared hosts can handle that. It asks for a current version of PHP, and it is usually installed with Composer, a package tool for PHP, so command line access helps. People tend to pick Flarum when they want a clean, modern-looking community and do not mind adding extensions themselves. ### NodeBB NodeBB is forum software written in JavaScript and run with Node.js on the server. It is open source, and the company behind it also offers managed hosting for anyone who wants it done for them. It can store its data in MongoDB, PostgreSQL, or Redis. That choice is unusual among forum projects and handy if you already run one of those. Running it means having a server that can run Node.js and keep a process alive. Most cheap shared hosting cannot do that. Pages update live, so new posts show up without a refresh. Teams tend to pick NodeBB when they are already comfortable with JavaScript on the server and want a board that feels quick and current. ### phpBB phpBB is one of the oldest forum projects still going, and it is still actively maintained by volunteers. It is free and open source, written in PHP, and it works with common databases such as MySQL. This is the easy end of the range. It installs on ordinary shared hosting, the kind that costs a few dollars a month. The layout is the classic board: categories, then forums inside them, then topics, then posts in order. People tend to pick phpBB when they want a familiar public board, cheap hosting, and software with a very long track record. ### MyBB MyBB is another classic PHP board, also free and open source, and also run by volunteers. It covers the same ground as phpBB: categories, forums, threads, and posts, with themes and plugins on top. Like phpBB, it is happy on shared hosting and simple to install. It has a full admin control panel where most settings live, and a template system you can edit to change how the board looks. People tend to pick MyBB when they want a straightforward board they can restyle, without much server work. ## What actually separates them Three things matter more than the rest when you are choosing. The first is weight. Discourse and NodeBB need a real server with services running on it. Flarum, phpBB, and MyBB fit the plain PHP hosting most people already have. That one fact narrows the list faster than any feature comparison. The second is the shape of the conversation. All five are built for open discussion first, not for questions and answers. There is no built-in idea of one correct reply that sits at the top of the page. Several can be pushed part of the way there with add-ons, but that is something you bolt on, not the core shape of the software. The third is finding help when you are stuck. Each project runs its own public forum on its own software. That is the best place to ask a question, and it also shows you the software in real use before you commit. ## The upkeep is the same job on all five Self-hosting any of these means the same short list of chores becomes yours. You install updates, including security updates. You take backups, and you test one by restoring it. You keep your email landing in inboxes instead of spam folders. You also handle spam, because a public forum with open sign-up gets found by spammers quickly. None of it is hard. It is just constant. Say it takes an hour in a normal month, and a slow afternoon when a major update lands. Over a year that is a real amount of someone's time. It has to be someone's job, or it stops happening. That trade is worth thinking through before you install anything. We walk through the same decision in more detail on the page about [forum hosting choices](https://forumcat.com/forum-hosting), including when paying someone else to run it is the cheaper answer. ## How to choose, by the job you have If you want an open community with depth, long threads, and strong moderation, Discourse is the natural pick, as long as you can carry the weight of running it. If you want a lighter modern community and you like choosing your own parts, look at Flarum. If you want the same lightness but your team lives in JavaScript, look at NodeBB. If you want a familiar board on cheap shared hosting, with almost no server work, phpBB and MyBB both do that well. Install both, look at each admin panel, and pick the one you prefer. You will be the one using it every week. If you want the direct head-to-head detail, such as Flarum next to Discourse, we keep that on our page comparing [open source forum options side by side](https://forumcat.com/compare/open-source-forums). ## When the job is customer questions and answers There is one case worth pausing on. If the forum's real job is customers asking about your product and your team answering, a discussion platform may be more than you need. What you want is a question, a clear answer marked as the right one, and a page a search engine can find later. The rest of the discussion features will mostly go unused. That is the job [a customer support forum](https://forumcat.com/support-forum) is shaped for, and it is what we built Forumcat to be. It is hosted, so there is nothing to install and no server to update. A portal is live in about five minutes. It is $9 one time on a Forumcat subdomain, or $99 a month with your own domain, and there is a 7-day free trial with no card. ![A Forumcat customer portal home page with answered questions and an Ask a question button](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/00-home-ask-hover-1788188154841-compressed.png) _For customer questions, a smaller tool can carry the whole job._ If your forum is really a community, ignore all of that and install one of the five above. They are built for community discussion, and that is not what Forumcat does. Keep reading: our roundup of [free forum software](https://forumcat.com/blog/free-forum-software) and a closer look at [what Discourse hosting costs](https://forumcat.com/blog/discourse-hosting-costs). ## FAQs Q: What is the best open source forum software? A: There is no single best one. Most rankings reflect the writer's own needs, not yours. Discourse gives you the most out of the box and asks for the most in return. Flarum and NodeBB are lighter and more modern in feel. phpBB and MyBB are the cheapest and simplest to keep running. Start with what your hosting can support, then pick on feel. Q: Is Discourse open source? A: Yes. Discourse is released under the GNU GPL, and you can download it and run it on your own server without paying for a license. The company that makes it also sells official hosting, which its pricing page listed from $100 per month when we checked in September 2026. Both are the same software. Q: Which open source forum is easiest to run? A: phpBB and MyBB are the easiest to get started with, because they run on ordinary shared PHP hosting and install in a few steps. Flarum is close behind, though it wants a current PHP version and is usually set up from the command line. Discourse and NodeBB both need a server you control, which is more work at the start and more work every month after. Q: Do open source forums cost anything to run? A: The software is free. The running is not. You pay for hosting, a domain name, and often a service that sends your email reliably. On top of that you pay in time, since updates, backups, and spam are now your job. A small board on shared hosting can be very cheap. A busy one on its own server is not. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## What free forum software really costs Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-02 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: What free forum software really costs Meta Description: phpBB, MyBB, Flarum, NodeBB, and Discourse are free to install. The forum still costs a server, mail, spam cleanup, and your hours. The honest bill. URL: https://forumcat.com/blog/free-forum-software You can run a forum on free software. phpBB, MyBB, Flarum, NodeBB, and Discourse are all free to download and install. They are mature projects with years of careful work behind them. Free covers the licence, which is the permission to use the software. It does not cover the running of the forum. A live forum needs a server, email that arrives, spam cleanup, updates, and backups. A little of that is money. Most of it is time. This post adds up the full bill so you can decide with open eyes. ## What you genuinely get for free The word free is honest here. You get the complete software, not a trial and not a cut-down version. There is no fee per member, so a forum with five people costs the same as one with five thousand. Features are not locked behind a paid tier. You can read the code, change it, and run it wherever you like. You also get people. These projects have their own forums, chat rooms, and documentation written by users who solved your problem last year. That help is real, and it belongs on the positive side of the ledger. Free forum software is serious software. Large communities have run on these tools for a long time, and they still do. If you are still choosing between them, a side-by-side [comparison of forum software](https://forumcat.com/best/forum-software) is the right place to start. This post is about the part that comes after you choose. ## Free is the licence, not the forum The licence is the part that costs nothing. A forum is more than the licence. It is the software, plus a machine to run it on, plus an address people can reach, plus a person who keeps all of that working. The cost sits in that gap. Nobody is hiding it. It simply does not appear on the download page, because these projects give away code rather than a service. Once you can see the gap, the choice gets easier to make. ## The bill, item by item A server comes first. The software has to run somewhere all day and all night. A small cloud server typically runs in the range of $10 to $30 a month, and that is a typical range rather than a quote. Your price depends on your host, your traffic, and how much you store. Email is next, and it surprises people. Your forum sends sign-in links, password resets, and notifications. Mail from a brand new server often lands in the spam folder. Fixing that means setting up records that prove the mail really came from your domain, or paying a small monthly fee to a service that sends mail for you. Spam is the third item. Any forum that lets strangers post will attract bots. They sign up, they post links, and someone has to remove them. Filters help a lot. They do not get to zero, so a person still checks. Updates and security patches are the fourth. Forum software gets security fixes, and so does the server under it. Applying them is a job somebody has to own. Skipping them for a year is how a small site becomes a problem. Backups are last. A backup you have never restored is not a backup yet. Test one, then write down what you did, so the next person can follow it under pressure. Each of these is small on its own. Together they are a standing job that never quite finishes. ## The time math, with your own numbers Do this sum yourself. Say a quiet month takes two hours: half an hour of updates, half an hour of clearing spam, and an hour of small things you did not plan. Some months will be lighter. The month a plugin breaks after an upgrade will be much heavier. Now put your own value on an hour of your time. Multiply it by two, then by twelve for the year. Add the server cost from above. That total is what a free forum costs you. Compare that number with what a hosting bill would be. If your hours are cheap right now, or if you enjoy the work, free wins the sum easily. If your hours are scarce, the answer often flips. Neither result is the wrong answer. They are just different situations. ## When free is the right call Free is a good choice when you already run servers. If you have a machine, a backup routine, and someone who patches things, you are adding a small task to an existing habit rather than starting a new one. It is a good choice when you enjoy the work. Plenty of people like tuning their own forum, and that time is not a cost to them. It is a good choice when you need control. If you must keep data in a specific country, or you want to change how the software behaves, running it yourself is the honest way to get that. And it is a good choice when money is genuinely tighter than time. A student group, a hobby project, or a company before its first customers can all run a fine forum on free software and some patience. That is a good answer on its own terms. ## When free is the wrong call Free stops making sense when nobody on the team wants the upkeep. A server without a clear owner falls behind slowly and quietly. If you cannot name the person who will apply the patch, the plan has a gap in it. It also stops making sense when the forum is part of customer support. Downtime on a hobby forum is a small problem. Downtime on the page where customers look for answers creates more support work, usually on a day that is already busy. The third case is timing. If setup takes you three weekends, that is three weekends where customers ask the same question and get no public answer. Sometimes the cost of waiting is larger than any bill. ## Paying money instead of time There are two ways to move the upkeep off your desk, and both are fair. The first is managed hosting for the free software you already picked. Someone else runs your phpBB, Flarum, or Discourse, keeps it patched, and handles the mail and the backups. You keep the software and its community, and you pay a monthly fee instead of doing the work. The [forum hosting page](https://forumcat.com/forum-hosting) walks through what that usually covers. The second is a hosted product, where the software and the running of it come together. This makes sense when your job is customer questions rather than open discussion. A [customer support forum](https://forumcat.com/support-forum) has a narrower shape than a general community. A customer asks, your team answers, and one reply gets marked as the accepted answer. The thread then becomes a page other customers find later. Forumcat is that second kind. It is a hosted question-and-answer portal on your own domain or a Forumcat subdomain, live in about five minutes, with nothing to install. A subdomain portal is $9 one time. A custom domain and higher caps are $99 a month. There is a 7-day free trial and no card is needed to start. It sits beside a help desk as the public self-serve layer, and it does not replace one. ![Creating a new forum in Forumcat with the name and web address filled in](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/03b-new-forum-filled-1788188160710-compressed.png) _The hosted path: minutes to live, a small bill, no upkeep._ Keep reading: [open source forum software compared](https://forumcat.com/blog/open-source-forum-software-compared) and [self-host or buy your customer forum](https://forumcat.com/blog/self-host-or-buy-your-customer-forum). ## FAQs Q: Can I create a forum for free? A: Yes. phpBB, MyBB, Flarum, NodeBB, and Discourse are all free to install, and none of them charge per member. You will still need somewhere to run the software, which usually means a small cloud server. The licence is free, and the hosting and the upkeep are yours. Q: What is the best free forum software? A: It depends on what you want the forum to do. phpBB and MyBB are long-running and familiar to a lot of people. Flarum and NodeBB feel more modern. Discourse is powerful and asks more of the machine it runs on. Pick the one whose default settings are closest to what you want. It will need the least work from you later. Q: What are the hidden costs of a free forum? A: They are less hidden than scattered. A server, email that reaches inboxes, spam cleanup, security updates, and tested backups. Each item is small, and together they need a regular hour or two from a person who knows the setup. Q: Is free forum software good enough for customer support? A: It can be, and many companies do run support on it. The question is who keeps it running on a bad week. If your team can own the upkeep, free software will serve customers well. If it cannot, paying for hosting moves that work to someone else. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## Should you self-host your customer forum? Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-02 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Should you self-host your customer forum? Meta Description: Self-host if you run servers and want control. Go hosted if you want your evenings back. Four questions that settle the build vs buy decision. URL: https://forumcat.com/blog/self-host-or-buy-your-customer-forum Self-host your customer forum if you already run servers and you want full control. You also have to accept that the forum becomes a small ongoing job. Choose a hosted forum if you want the forum without that job. Customers still ask in public. Your team still answers. The software you pick matters less than who will spend an evening on each upgrade. Self-hosting means you rent a server, install the forum software, and keep it running. A server is a computer on the internet that stays on. Hosted means a company runs that software for you. You pay them. You do not touch the machine. ## What self-hosting gives you You hold the data. The posts, accounts, and files live on a server you control. You can read the code. You can change it. You can keep running it after a vendor would have shut a plan down. There is no monthly software bill for the forum itself. Open-source forum software is code you can run without paying the authors. You still pay for the server. You still pay in time. You do not pay a company for permission to keep using the product. No vendor sets your features or your price. A vendor is the company that would sell you a hosted product. They can raise prices. They can drop a feature. They can close a plan. On a server you run, those decisions stay with you. You can modify anything. If the stock software lacks a sign-in method you need, you can add it, or pay someone to add it. If an old add-on matters to you, you can keep it running. That freedom is real. It is also work. For some teams this is the right call. If you already run servers, and someone on the team likes that work, self-host. Some companies must keep customer data in a country they choose, or on hardware they name in a contract. Self-hosting is a direct way to meet that. You get a forum that matches how you already operate. You do not wait for a host to add a feature. ## What self-hosting costs besides the server The server bill is the line people remember. The rest of the cost is a short list of jobs that never finish. Updates arrive on the software's schedule, not yours. Security patches are updates that close holes in the code. Those need to go on too. You take backups, and you test them. A backup is a copy of the posts and accounts. A restore is using that copy to bring the forum back. You only know a backup works after you restore one. The forum has to send email, so sign-in links and notices actually arrive. That is mail delivery, and it breaks in dull ways. A changed DNS record, a blocked sender, a full mail queue. DNS is the system that points a name at a server. Someone has to notice, and then fix it. Disk space and the database need care as well. The database is where posts are stored. Disk is the space those files use. Both fill up. Someone has to notice before the forum stops writing new posts. Each of those jobs is small on a quiet week. Together they stay on the list every month, for as long as the forum is up. A failed upgrade can take an evening. A mail problem can take a morning. The costs are small on their own. They are steady, and they do not stop. ## Four questions that decide it Walk through these with the people who would do the work. Write the answers down. Do this before you compare features. ### Who already runs servers and enjoys it Name the person. If nobody on the team already runs servers, do not start with a customer forum as the first machine. The learning curve is real, and customers will feel the mistakes. If someone already does this work, and they enjoy it, self-hosting fits. Enjoying it matters. A person who dreads update day will put it off. If patches wait, holes in the software stay open. ### What happens when that person is away The forum still needs care when that person is on holiday, or ill, or leaving. Name a second person who can apply an update and restore a backup. If you cannot name one, write the steps so someone else can follow them. A customer forum that only one person can revive is a risk. That gap shows up when the person is gone and a patch is due. ### Whether customer data on your server is a comfort Some teams sleep better when customer data sits on a server they run. That is a fair reason to self-host. Comfort means you also accept the duties that come with it. Those duties include backups, uptime, and data requests. Uptime is the time the site is reachable. If the server is down, customers cannot read answers. GDPR is a European data-protection law. It lets a person ask you for a copy of their data, or ask you to delete it. On your server, those requests are yours to fill. If that list feels like a load, it is a load. Hosted does not remove your legal duties. It does move the server, the backups, and the uptime onto someone whose job is that work. ### What an hour of your team's time costs Write down what one hour of that person's time costs your company. Use salary plus the usual extras, or a number your finance person already uses. Say that person spends two hours in a quiet month on updates, backups, and mail. Two hours times that rate is your quiet-month cost. Add a buffer for a month when an upgrade fails. Compare the total to a hosting bill for the same month. If the time cost is lower, and the person is staying, self-host. If the time cost is higher, or that time is better spent on the product, pay for hosting. Do the sum with your numbers. Do not guess from a price page alone. ## If you decide to self-host Pick boring, well-documented software. Boring here means it has been around a while, other companies run it, and the docs tell you how to install, back up, and upgrade. Skip software that is new and still changing fast. Customer answers need a tool that will still be there next year. Start by [comparing open-source forum software](https://forumcat.com/compare/open-source-forums). Choose one that matches a support forum, not a wide public community, unless a wide public community is what you actually want. Automate backups on day one. Then restore one backup onto a spare server, or a spare folder, and prove you can read the posts. Until you restore a backup, you do not know that it works. Put the upgrade day in the calendar. Pick a quiet window. Read the release notes before you start. Have the last working backup next to you. Do not wait for a scare to learn the steps. ## If you decide to go hosted A hosted forum is a company running the software so you do not have to. You still need to check a few things before you pick a vendor. Ask how you get your data out. You want a way to export every question and every answer. Ask whether that export is complete. Ask how long they keep a copy if you leave. Ask what uptime they state. Uptime here is the share of time they say the site will be reachable. A number on a page is a claim. Read what they offer if they miss it. Ask what happens to your domain and your links if you leave. A custom domain is your own web address, like help.yourcompany.com. You want to keep that address. You also want old links to keep working, or a clear redirect, so search results do not die with the contract. If you want that trade written out in one place, there is a page on [hosted forums](https://forumcat.com/forum-hosting). Use it as a checklist, then judge any vendor against the same three questions. ## If you want a forum without a server to keep Forumcat is a hosted customer Q&A portal on your own domain or a subdomain. A Q&A portal is a public site where customers ask questions and your team answers. It is live in about five minutes, with nothing to install. A portal on a Forumcat subdomain (a web address like yourcompany.myforumcat.com) is $9 one time, with a 7-day trial and no card. It is for customer product questions. It is not a general discussion platform. The same offer is on the page for [a hosted support forum](https://forumcat.com/support-forum). ![Creating a new forum in Forumcat with the name and web address filled in](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/03b-new-forum-filled-1788188160710-compressed.png) _The hosted trade: minutes to live, no server to keep._ Keep reading: [what Discourse hosting really costs](https://forumcat.com/blog/discourse-hosting-costs) and [how to set up a customer support forum](https://forumcat.com/blog/how-to-set-up-a-customer-support-forum), and [what free forum software really costs](https://forumcat.com/blog/free-forum-software). ## FAQs Q: Is it cheaper to self-host a forum? A: The server bill is often smaller than a hosted software bill. Your time is the rest of the cost. If someone on the team already does that work and likes it, self-hosting can cost less. If that time comes out of product work or support, hosted can cost less. Q: What skills do I need to self-host a forum? A: You need to be comfortable with a server, a database (where posts are stored), and sending email from a machine. You also need to apply security patches, which are updates that close holes in the code, and restore a backup rather than only take one. If nobody on the team enjoys that work, hosted is the safer pick. Q: Is self-hosting a forum safe for customer data? A: It can be, if you treat backups, access, and uptime as your jobs. Uptime is the time the site is reachable. You also handle data requests under laws such as GDPR, a European data-protection law that lets a person ask for a copy of their data or ask you to delete it. Safe means a tested restore, a plan for a leak, and someone who can act when the server is down. Q: How do I choose between self-hosted and hosted forum software? A: Start with the people, not the feature list. If someone already runs servers and will still be around next year, self-host. If you want the forum without that job, go hosted. Then pick software that matches the job. Choose a place for product questions, or a wider discussion platform, depending on what you actually run. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## What Discourse hosting really costs Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-02 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: What Discourse hosting really costs Meta Description: Official hosting starts at $100 a month. Self-hosting is free software plus a server and your time. The full bill for each path, in one honest table. URL: https://forumcat.com/blog/discourse-hosting-costs Hosting run by the Discourse team starts at $100 per month. That figure comes from Discourse's own pricing page, checked September 2026. Self-hosting works out differently. The software itself is free and open source, so your bill is a server plus your own time. A small cloud server typically runs in the range of $10 to $30 a month, depending on size and provider. The rest of the cost is hours, and hours are easy to forget. This page lays out both bills, plus a middle path, so you can add up your own number. ## The official hosted plans Discourse sells hosting for the software it builds. The plans below come from Discourse's own pricing page, checked September 2026. Pro is $100 per month. It includes 500,000 monthly page views and 5 staff seats. A staff seat is an account for someone on your team who replies or moderates. Business is $500 per month and includes 15 staff seats. Enterprise pricing is custom, so you have to ask them for a quote. There is a free trial if you want to try the software before you pay. Those are the public numbers. Your real bill depends on how many staff need seats and how much traffic your forum gets. ## What managed hosting actually pays for The monthly fee covers more than rent on a server. Someone else runs the upgrades. Someone else takes the backups and watches the disk space. Someone else gets woken up if the site goes down at night. Discourse is a mature product with a long track record. Plenty of large public communities run on it, and the software is well regarded. If a forum is central to your business, paying the people who wrote the code is a reasonable choice. You are paying for their attention as well as their servers. ## The self-hosted bill, item by item Self-hosting means you install the free software on a server you rent. The licence costs nothing. Here is what does cost something. First, the server. A small cloud server typically runs in the range of $10 to $30 a month, depending on size and provider. Bigger forums need more memory, so the number moves up with use. Second, the first install. Discourse's site says the software installs in under 30 minutes on your own server. That claim is fair. The install is the small part of the job. Third, everything after the install. This is the part people leave out of the math. New versions come out, and someone has to apply them. Upgrades sometimes fail, and then someone has to work out why. Backups need to run on a schedule. They also need to be restored once in a while, so you know they really work. You also need email to leave your server. Sign-up confirmations, password resets, and reply notifications all go out by mail. Mail from a fresh server often lands in spam, so most people connect a mail service and set up the DNS records that prove the mail is really yours. Disks fill up too, mostly with uploaded images, and someone has to notice before the site stops writing. None of this is dramatic. It is a short list of chores, and the chores are yours. In a good month, self-hosting takes an hour or two of attention. In a bad month, when an upgrade breaks or mail stops arriving, it takes a lot more. Put your own value on an hour and the true cost of self-hosting starts to look clearer. We work through that trade in more detail in our guide to [self-hosting or buying a customer forum](https://forumcat.com/blog/self-host-or-buy-your-customer-forum), and our [comparison of open source forum software](https://forumcat.com/compare/open-source-forums) covers the other free options in the same space. ## The middle path: third-party managed hosts There is a group of smaller companies that host Discourse for you. They are not Discourse, and they usually charge less than the official plans. You still get someone else doing the upgrades and the backups. Prices vary a lot, so check each one directly rather than trusting a number you read in a forum thread. Before you pick one, ask four plain questions. How often are backups taken, and can you download a copy yourself? Who applies upgrades, how quickly, and what happens when one fails? Can you export your data and leave without asking permission? Is email included, or do you still have to arrange that? Our page on [forum hosting options](https://forumcat.com/forum-hosting) walks through the same checks in more depth. A good third-party host is a fine answer. A cheap host that never applies upgrades is a problem you will have to deal with later. ## The question under the question Most people who search for Discourse pricing are really asking a bigger question. They want to know what a public place for their users should cost. Discourse is a full discussion platform. It has categories, ongoing conversation, trust levels, and the tools a real community needs. If you are building a community, that depth is the point, and paying for it makes sense. Some teams do not need that. They need one public page per customer question, so the next person who asks can find the answer. That is a smaller job, and a smaller tool can do it. Forumcat is a hosted question and answer portal for exactly that job. It costs $9 one time on a Forumcat subdomain, or $99 per month if you want it on your own domain with higher limits. There is a 7-day trial and it does not ask for a card. If you want the feature-by-feature view, we keep a [Forumcat and Discourse comparison](https://forumcat.com/vs/discourse) for that, and our [hosted support forum](https://forumcat.com/support-forum) page describes the smaller job on its own. ![A Forumcat customer portal home page with answered questions and an Ask a question button](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/00-home-ask-hover-1788188154841-compressed.png) _If the job is customer Q&A, the tool can be smaller._ ## The four options side by side Every number in this table comes from the sources named above. Discourse figures are from Discourse's own pricing page, checked September 2026. The server figure is a typical range, not a quote from any one provider. OptionMonthly costWhat is includedWho does the maintenanceDiscourse Pro (official)$100 per month500,000 monthly page views, 5 staff seatsDiscourseDiscourse Business (official)$500 per month15 staff seatsDiscourseSelf-hosted DiscourseA server in the $10 to $30 range, plus your timeThe full software, free and open sourceYouForumcat$99 per month on your own domain, or $9 one time on a subdomainA hosted question and answer portalForumcat ## A short way to choose Self-host if you already run servers and enjoy it. You will save real money, and you will pay for it in hours. That is a fair swap when the hours are cheap for you and control matters. Pay for official hosting if the community is core to what you sell. When the forum going down is a business problem, hand that risk to the people who wrote the software. Pick a smaller question and answer tool if the job is support. Most support forums are a list of questions with good answers under them. You do not need a full discussion platform to run one. A simpler setup also means fewer things to look after each month. Keep reading: [self-host or buy your customer forum](https://forumcat.com/blog/self-host-or-buy-your-customer-forum) and [how to set up a customer support forum](https://forumcat.com/blog/how-to-set-up-a-customer-support-forum), and [open source forum software compared](https://forumcat.com/blog/open-source-forum-software-compared). ## FAQs Q: How much does Discourse cost per month? A: Discourse's own pricing page, checked September 2026, lists Pro at $100 per month with 500,000 monthly page views and 5 staff seats. Business is $500 per month with 15 staff seats. Enterprise pricing is custom and quoted on request. A free trial is available. Q: Is Discourse free to self-host? A: The software is free and open source, so there is no licence fee. You still pay for the server it runs on, which typically falls in the range of $10 to $30 a month depending on size and provider. You also pay in time. That time is the part most people underestimate. Q: What does self-hosting a forum actually involve? A: Discourse says the install takes under 30 minutes on your own server, and that is the easy part. After that you handle version upgrades, backups you have actually tested, a mail service so sign-in and notification emails arrive, and disk space as uploads grow. Expect an hour or two a month when nothing goes wrong. Expect more when something does. Q: Is there a cheaper alternative for a customer support forum? A: Yes, if your job is customer questions and answers rather than open community discussion. Forumcat is a hosted portal for that at $9 one time on a subdomain, or $99 per month on your own domain, with a 7-day trial and no card needed. Smaller open source projects can also work, though they put the maintenance back on you. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## Running a customer community in 15 minutes a day Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-02 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Running a customer community in 15 minutes a day Meta Description: A small customer community does not need a full-time manager. The daily routine: answer, accept, close, and read the searches that found nothing. URL: https://forumcat.com/blog/running-a-customer-community A small customer community needs one person, 15 minutes a day, and a fixed order of work. Answer new questions. Mark the reply that solved the problem as the accepted answer. The accepted answer is the one reply later readers should trust. Close finished threads. Check the searches that found nothing. Then you are done for the day. That sequence is community management for a support community. Community management means keeping a public Q&A room current, so customers can find answers without emailing you. A support community is not a social network. Volume stays low. Questions are concrete. Most days, nothing dramatic happens. A fixed small routine keeps the room current. A vague plan to post more often usually fades after two weeks. If you already run [a community help center](https://forumcat.com/community-help-center), the daily work is review. You are not trying to entertain a crowd. You are keeping answers findable. ## Answer new questions first The person who posted is waiting. Start there. Open the list of new and open questions. Read the newest ones first. If you know the answer, write it. If you need to check the product, say you are looking. Come back the same day when you can. Give this five to eight minutes. A small community often has zero or one new question. Some days you will spend the whole 15 minutes here. That is the right use of the time. An unanswered question is what makes the room look abandoned. If a customer already answered well, add a short staff note. Say the steps are correct. Staff replies should show the person's role next to their name. A role is the job title shown beside the name, such as agent or admin. Official answers then look official. If you use Forumcat, this routine sits on two screens. A questions list is where you review and moderate threads. Moderate means handle the thread: answer it, mark it solved, or close it. A members page is where you handle the rare suspension. ![The questions list in the Forumcat dashboard where staff review new and open threads](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/11-questions-light-1788188151847-compressed.png) _The whole daily review, one list._ ## Mark the reply that worked Later readers need to know which reply to follow. Several replies can all sound plausible. One of them is the one that actually solved the problem. The asker or a staff member marks that reply as the accepted answer. It pins under the question. The thread then shows as solved. A solved thread is a page the next customer can trust. This takes about a minute per thread. Do it the same day you answer, while you still remember what worked. If a customer wrote the useful reply, mark theirs. You still want the pin. The next reader should not have to guess. Leave a thread unsolved only when you are still waiting on a real next step. A maybe-correct reply is not an accepted answer. Mark it when you know. ## Close finished threads An open list full of old, solved threads is hard to scan. Close the ones that are done. Closing means the thread is finished. It leaves the open queue. People can still read it and search it. A tidy list of solved threads looks like someone is paying attention. People search it. They trust it. A long open list of month-old questions looks like a room nobody tends. Give this two minutes. If a thread is waiting on the customer, leave it open. If the answer is up and the asker has gone quiet, close it. You can reopen it if they come back. ## Check searches that found nothing After the live questions, look at searches that returned no useful thread. Those are called empty searches. They tell you which answers to write next. A customer already typed the words they use. If your tool shows empty searches, write them down. If it does not, keep a running note. Add a line when you or a teammate cannot find an answer. Post that question in the customer's words. Write the answer. Mark it solved. This is often three to five minutes. Some days the list is empty. Skip it. Some days one query shows up twice. Write that answer first. Say three people a week search for "change the card on file" and find nothing. Each then emails you. Each reply takes ten minutes. That is 30 minutes a week on one missing page. One public thread, titled in those words, does that job after you write it once. ## A 30-minute pass once a week Once a week, take 30 extra minutes. Skim the busiest threads. Fix any wrong answer that showed up later. Products change. A reply that was right in March can be wrong in September. Edit it, or add a new accepted answer. Thank one customer who helped another. A short public note is enough. People who answer well will often do it again if they know you saw it. Note which questions suggest a product fix. If several people asked how to export a file, the product may need a clearer button. Write that down for the product team. The community is a list of stuck moments, in the customers' own words. Do not turn this weekly pass into a publishing calendar. You are checking quality. You are saying thank you. You are sending one note to product. ## Write three rules and use them Most customer communities see very little bad behavior. People come with a problem. They want an answer. They leave. Write three rules and post them where people can find them. A simple set is: stay on the product, no insults, and no posting other people's private data. Remove what breaks them. Suspend repeat offenders. Suspend means that person cannot post for a while, or at all. Moderation is the work of keeping the room usable. You do not need a large team for a quiet Q&A room. Have the rules. Use them when you must. Then go back to answering questions. The members page is for that rare bad day. Search for the person. Take the action. Then return to the questions list. ![The forum members page in the Forumcat dashboard with search and per-member actions](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/12-members-light-1788246033771-compressed.png) _Member management for the rare bad day._ ## When 15 minutes is no longer enough Watch for three signs. Question volume grows past what one person can answer in 15 minutes. You are still finishing yesterday's questions today. More than one language shows up, and you cannot answer all of them well. Private cases mix into the public room. Private cases are account-specific problems, such as a refund or a bug in one account. When that happens, add a teammate with a role. Give them a named job, such as agent, so their replies look official. Split the 15 minutes. One person takes new questions. One person takes empty searches and the weekly review. Do not add a second tool for the same Q&A work. Keep private cases off the public list. If your tool can mark a question private, use that. A private question is visible to the asker and staff only. Your help desk still handles the cases that need account access. The public room sits beside it as the self-serve layer. A [hosted support forum](https://forumcat.com/support-forum) on a Forumcat subdomain is $9 one time. A custom domain is your own address, like help.yourcompany.com. That plan, with higher caps, is $99 per month. There is a 7-day free trial, and you do not need a card. Keep reading: [how to build a customer community](https://forumcat.com/blog/build-a-customer-community) and [how a self-service forum cuts support tickets](https://forumcat.com/blog/cut-support-tickets-self-service-forum), and [how to moderate a forum part time](https://forumcat.com/blog/moderate-a-forum-part-time), and [a community manager's first 30 days](https://forumcat.com/blog/community-manager-first-30-days). ## FAQs Q: How much time does community management take? A: For a small customer community, plan 15 minutes a day and 30 minutes once a week. Most of that time is answering new questions and marking the reply that worked. If you have no new questions, the empty-search check still takes a few minutes. Miss a day if you must. Do not miss two weeks. Q: Do I need a community manager? A: A small support community can be run by someone who already answers customers. A community manager is a person whose full job is the room, the events, and the people in it. You need that title when volume, languages, or extra programs outgrow a daily 15 minutes. Until then, a named owner of the routine is enough. Q: How do I moderate a customer community? A: Write three rules. Post them. Remove posts that break them. Suspend people who keep breaking them. Most days you will do none of this. Spend your time on answers, not on a large enforcement process. Q: What should I do with unanswered questions? A: Answer them first, the same day if you can. If you need time to check, say so on the thread. If the question is a duplicate, link the older solved thread and close the new one. Unanswered questions are the fastest way a community starts to look unused. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## How to build a customer community (start with answers) Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-02 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: How to build a customer community Meta Description: Skip the engagement playbook. A calm 30-day plan: seed ten answered questions, route repeats to the community, and let members in once answers work. URL: https://forumcat.com/blog/build-a-customer-community A customer community begins as a public place where questions get answered. It does not begin with events, badges, or a posting schedule. Pick one place where customers can ask in the open. Answer the questions your inbox already gets. Keep doing that for 30 days. At the end you will have a small community that is useful on day one. Everything else can be added later. Here is a 30-day plan. It assumes a small company with no crowd yet and nobody free to run one full time. ## Why answers come first People need a reason to show up. An answer is a reason. Someone has a problem right now and wants it fixed. If your page fixes it, they stay for a minute and remember where they were. Answers also keep working after you write them. One clear answer can help people for years. A post that asks "what is everyone working on this week?" is read once and then goes quiet. There is a second gain. Every question you answer in public is a question you stop answering by email. Say 30 emails a week ask the same five things. At ten minutes each, that is five hours a week. Answer those five things in public once and a good share of that time comes back to you. That saving is what pays for the effort. It is the whole case for [customer community software](https://forumcat.com/customer-community) in one paragraph. ## Why "engagement first" stalls for small companies Most guides open with engagement. Set a posting schedule. Run a welcome thread. Plan a monthly event. That advice comes from large communities that already have members. You do not have members yet. A prompt posted into an empty room gets no replies. Then the empty room is the first thing a new visitor sees. That looks worse than having no community at all. Questions work differently. A prompt asks a stranger to give you something. An answer gives the stranger something first. Early on, only one of those two will work. ## Days 1 to 7, set up the room Start by picking where the questions will live. It should be public, easy to search, and readable without an account. Most people who read your answers will never sign up, and they should not have to. If you are still weighing options, our [community platform](https://forumcat.com/community-platform) page covers what to look for. This is the job Forumcat does. It is a hosted question and answer portal on your own domain or a Forumcat subdomain. It goes live in about five minutes, with nothing to install. Categories, search, and accepted answers are built in, and anyone can read and search without signing in. Next, make three to five categories. Name them the way customers speak, not the way your team is organized. "Billing and refunds" is better than "Revenue operations". Keep the list short. A long list of empty categories makes the place look abandoned. ![A Forumcat category page listing answered questions in the General category](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/04-category-general-1788246030953-compressed.png) _Shelves named the way customers speak._ Now seed it. Open your support inbox and find the ten questions you answer most often. Post each one as a question. Then answer each one yourself, in full, in plain words. You are writing both sides for now. That is fine, and it is not fake. These are real customer questions, written down where the next person can find them. Try to end week one with ten answered threads. A first-time visitor should land on a page that already helps. ## Days 8 to 21, build the habit Weeks two and three are about one habit. When a repeat question arrives by email, do not answer it in email. Answer it in the community first. Then reply to the email with the link and one line of context. That costs an extra minute the first time. It saves the whole reply the next time. This is how the library gets built, one question at a time. Then make the place easy to find. Add a link in your website menu. Add a line to your email signature. Add it to your support auto-reply. Put it in the help section of your product if you have one. People cannot use a [support forum](https://forumcat.com/support-forum) they never see. Answer new questions within a day. In the first month, speed matters more than polish. A short, correct answer today beats a careful one next week. You can always come back and improve it. When a reply solves the problem, mark it as the accepted answer. The accepted answer is the single reply that gets pinned under the question, so the thread reads as solved. A reader can then see the fix without reading every comment. In Forumcat, either the person who asked or a staff member can mark it. ![A solved question thread in Forumcat with the accepted answer pinned under the question](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/06-thread-solved-1788188139254-compressed.png) _The accepted answer shows readers what worked._ ## Days 22 to 30, let members in So far you have done all of the writing. The last week is about bringing other people in. Write to your most active customers one at a time. Use their name. Keep it to two lines. Say that they have asked good questions before. Tell them where those questions now get answered in public, and ask them to post there. Ten personal emails will do more than one announcement to your whole list. When a customer answers another customer, thank them in the thread, in public, by name. Do it every single time. That small act is what turns a reader into a member. Do not add points, levels, or badges yet. Those reward volume. With a handful of active people there is nothing much to rank. The scores only draw attention to how quiet the place is. ## What day 30 looks like These are rough expectations, not measured results. Your numbers will depend on your traffic, your product, and how often people write in. Treat them as a rough shape, and compare month two against your own month one. - A few dozen solved threads, most of them written by you. - A few questions a week arriving on their own, without you asking. - One or two answers written by a customer instead of by you. - A little traffic from search, since answered pages are ordinary web pages. The first answer written by a customer is the one to watch for. It means someone came back and felt able to help. ## What to add later, and what to skip Add one thing at a time, and only once the questions keep coming without you pushing. A monthly live session works well when there are enough regulars to fill it. A short monthly email with the best threads is easy to write and brings people back. Member spotlights are worth doing once you have members worth featuring. Badges and points can wait until there are enough people for a ranking to mean anything. Skip engagement bait in a support community. Threads like "Friday chat, tell us your favorite feature" add noise to the search results. People come to your community to find an answer. Every post that is not an answer makes that a little harder. None of this needs much money. A Forumcat portal on a Forumcat subdomain is $9 one time. A custom domain and higher caps are $99 a month. There is a 7-day free trial and no card is needed. The real cost of a customer community is your attention in the first month. Keep reading: [running a customer community](https://forumcat.com/blog/running-a-customer-community) and [how to set up a customer support forum](https://forumcat.com/blog/how-to-set-up-a-customer-support-forum), and [how to seed a new forum](https://forumcat.com/blog/seed-a-new-forum), and [the types of online communities](https://forumcat.com/blog/types-of-online-communities), and [private vs public communities](https://forumcat.com/blog/private-vs-public-community). ## FAQs Q: How do I start an online community from zero? A: Pick one public place for questions, then post and answer the ten questions your support inbox already handles. Send every repeat question there instead of answering it by email. Do that for a month before you think about events, prompts, or promotion. Starting with answers means the place is useful even on the day nobody visits. Q: How long does it take to build a community? A: You can have a useful one in about a month, because ten good answers already help people. Getting to steady customer-to-customer help usually takes longer, often several months. It depends on how many customers you have and how often they need help. The first month is the part you fully control, so treat it as the real starting line. Q: Do I need a community manager? A: Not at the start. In month one the work is answering questions, which your support team is already doing somewhere else. Budget a few hours a week for one person who owns it. A dedicated manager makes sense later, once there is more conversation than one person can read. Q: What platform should a small company use for a customer community? A: Look for public pages that anyone can read without an account. You also want good search, categories, and a way to mark the accepted answer. Setup time matters more than feature lists when the team is small. Chat tools like Slack or Discord are fine for talking, but the answers scroll away and search engines never see them. A hosted question and answer portal such as Forumcat covers the basics and can be live in about five minutes. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## A Discord alternative for your customer community Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-02 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Discord alternative for customer communities Meta Description: Discord is built for live chat. Customer questions need answers that stay put. How to tell when your community needs a public Q&A forum, and how to move. URL: https://forumcat.com/blog/discord-alternative-for-customer-communities If most of your community is customers asking for help, move that part to a public Q&A forum. A forum gives every question its own page. The answer stays on that page for the next person who asks. Another chat app will not fix the problem, because the shape is the same. If your community is mostly people talking in real time, Discord is still a good home for it. Many companies keep Discord and add a forum next to it. This post helps you tell which parts belong where. ## What Discord is good at Discord is free and takes minutes to set up. People are already in it, so they join without learning anything new. Real-time talk works well there. Voice channels, quick reactions, and side chat make a group feel alive. That feeling matters, and a forum does not create it. None of the problems below are about quality. Discord does the job it was built for. The trouble starts when you ask a chat app to hold your support knowledge. ## Why chat is the wrong shape for support answers In chat, answers move down and out of view. A good answer from Tuesday is a hundred messages up by Thursday. Nobody scrolls that far. So the same question comes back next week, and someone types the answer again. Search inside chat looks for single messages. A real answer is often four messages from three people, plus a screenshot. Search can find one piece of that. It rarely hands you the whole thing. Chat is also closed to the outside. A customer with the same problem searches Google at 11pm. Your server is private, so nothing you wrote can help them. They open a ticket instead, or they give up. New members see the last hour of talk. They do not see what the group already knows. The knowledge is in there somewhere, but no one can reach it. ## A test you can run in ten minutes Open your busiest channel. Read the last 50 messages. Count how many are questions your team has already answered before. Then do the math out loud. Say 20 of those 50 are repeats. Say each one takes about eight minutes to answer well. That is over two hours a week, spent typing answers that already exist. Run the same count next week to check the number. If the repeats are a small share, chat is working fine for you. Leave it alone. If half the room is asking questions that were answered before, the shape is costing you real time. ## Route by job, not by tool ranking Most lists of Discord alternatives rank 16 chat apps. That is the wrong question. Ask which job each part of your community is doing, then pick a home for each job. Real-time hangout stays in chat. Launch days, banter, voice calls, and event chatter all belong there. Discord is good at this and moving it would be a loss. Customer questions and answers belong in a public Q&A forum. Each question is a page. The best reply gets marked as the accepted answer and pins to the top, so nobody has to read the whole thread. The page keeps working for months. Private work belongs in your help desk. Billing details, account problems, and anything with one customer's private data need an owner and a due date. A forum should not try to be a ticket queue, and a good one does not. Forumcat is [a hosted community platform](https://forumcat.com/community-platform) built for the middle job. Anyone can read and search it without an account, so a customer gets an answer before they ever sign in. Every answered public question ships QAPage structured data, which is a small block of code that tells search engines this page is a question with an accepted answer. That is how last month's answer starts helping people who never joined your server. ![A Forumcat portal sorted by top voted, showing the questions most customers share](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/01-home-sort-top-voted-1788246027389-compressed.png) _Votes surface what chat buries._ If you want the longer version of this split, see how [customer community software](https://forumcat.com/customer-community) differs from a chat server, and what [a support forum](https://forumcat.com/support-forum) is meant to hold. ## What moving looks like in practice Do not migrate your history. Years of chat logs are not worth copying, and they would read badly as forum posts anyway. Start with the questions that keep coming back. Pick 15 of them. Use the count from the test above. Post each one on the forum in the customer's own words, then answer it properly. Write the answer once, and write it well, because this version is the one people will find. Pin the forum link in your Discord channels. Put it in the channel topic and the welcome message. From then on, answer repeat questions in Discord with a link to the forum thread. If the answer is not there yet, post it there first, then paste the link. ![Search results in a Forumcat portal for the query webhook, showing solved questions](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/03-search-webhook-1788188135310-compressed.png) _Last month's answer, still findable._ Give it a month before you judge it. The forum starts empty and slow. It gets useful as the pile of answered questions grows, and each one keeps paying off after the day you wrote it. ## What you give up A forum is slower and quieter than chat. That is on purpose, and it is a real trade. You lose the fast back-and-forth. You lose voice. You lose the memes and the sense that someone is always around. People post less often on a forum, and they wait longer for replies. Some members will never move, and that is fine. This is why most teams keep both. Discord holds the room. The forum holds the answers. The forum takes the repeats off your chat, which usually makes the chat nicer to be in. ## A small first step You do not need a migration plan. Stand up a forum, answer 15 questions on it, and link to it from Discord for a month. Then look at whether your repeat count went down. A Forumcat portal on a subdomain is $9 one time, and it takes about five minutes to set up. There is a 7-day free trial with no card. Keep reading: [how to build a customer community](https://forumcat.com/blog/build-a-customer-community) and [how a self-service forum cuts support tickets](https://forumcat.com/blog/cut-support-tickets-self-service-forum), and [how a public forum creates customer advocates](https://forumcat.com/blog/customer-advocates). ## FAQs Q: Is there a better alternative to Discord for customer communities? A: It depends on what your community does. For real-time talk and voice, Discord is hard to beat. For customer questions that need to stay findable, a public Q&A forum works better, because each answer keeps its own page. Many teams run both and send each type of conversation to the right place. Q: Can I use Discord for customer support? A: Yes, and plenty of companies do. It works well while the volume is low and the questions are new. It gets expensive once the same questions repeat, since every answer scrolls away and has to be typed again. Watch your repeat count, and add a forum when it climbs. Q: Should I move my community off Discord? A: Usually no. Moving a whole community is hard and you can lose the people who liked it there. Move one job instead: take the questions and answers to a forum and leave the talking in chat. If the chat goes quiet on its own after that, you have your answer. Q: Can I keep Discord and add a forum? A: Yes, and that is the common setup. Pin the forum link in your channels and answer repeat questions with a link to the thread. Discord stays the place people hang out. The forum becomes the place people search. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## How to set up a customer support forum, the fast way 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: How to set up a customer support forum fast Meta Description: The setup takes minutes. The first ten answers decide whether it works. A step-by-step plan for launching a support forum customers actually use. URL: https://forumcat.com/blog/how-to-set-up-a-customer-support-forum You can set up a customer support forum today. A hosted tool takes minutes. If you install the software yourself, plan for a longer first day, plus the server work after that. What decides whether anyone uses it is the first ten answers, and the first two weeks of sending people to those pages. Pick hosted or self-hosted. Create the forum. Add three to five categories named the way customers talk. Post the ten questions your inbox already answers. Link the forum in your site nav, your email signature, and your auto-reply. When a repeat question arrives by email, answer it on the forum and send the link. ## Pick hosted or self-hosted Self-hosting means you rent a server, install the forum software, and keep it running. You choose the code, the extra plugins (small add-ons that change how the forum works), the mail setup so sign-in emails arrive, and the backup plan. You get full control. You also get update days, failed upgrades, and hours that never appear on a price page. A hosted forum is the other trade. A company runs the software. You pay. You sign in, name the forum, and it is live. You give up root access to a machine most support teams did not want to tend. You get your evenings back. If you want that trade written out in one place, read a plain comparison of [hosted forums vs self-hosting](https://forumcat.com/forum-hosting), then pick any tool that matches how you like to spend time. If you already run servers and you want to change the code, self-host. If you want a working forum and you do not want a second job, go hosted. ## Create the forum Most hosted tools share the same first screen: a name, a web address, a create button. This example uses Forumcat so the clicks are real. Sign in, pick a name, and pick an address on a Forumcat subdomain (a web address like yourcompany.myforumcat.com). Upload your logo. Pick the accent color from your site so buttons and links match. The forum is live in about five minutes, with nothing to install. [A hosted support forum](https://forumcat.com/support-forum) on a subdomain is $9 one time. There is a 7-day free trial, and you do not need a card. ![Creating a new forum in Forumcat with the name and web address filled in](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/03b-new-forum-filled-1788188160710-compressed.png) _The setup form: name, address, create._ ![Forumcat display settings where you upload a logo and pick an accent color](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/30-settings-display-light-1788188164775-compressed.png) _Make it look like your site before you share the link._ Other tools follow the same shape. They differ mainly in how long this step takes. A self-hosted install waits on the server, the database (where posts are stored), mail, and the first working backup. If you follow this example, the [setup docs](https://forumcat.com/docs) cover the same clicks. ## Make three to five categories Start with three to five categories, not fifteen. A new forum with fifteen empty rooms looks dead. Three shelves that already have a few threads look like a place people use. Name them the way customers speak: Billing, Getting started, Using the API, Troubleshooting, Account. Those are the words people type when something is stuck. Do not name categories after your org chart. Engineering, Finance, and Customer Success are how you sit. A customer with a failed charge is looking for Billing. Pull the names from your inbox. If half of last month's mail is "how do I invite a teammate" and "how do I change the card", you already have Getting started and Billing. Leave a catch-all only if you must, and rename it once a real cluster shows up. You can split a category later, when it is full. Empty rooms on day one help no one. ## Seed it with ten answered questions An empty forum reads as abandoned. Ten solved threads read as a place answers live. Open last month's inbox. Pick the ten questions you already typed an answer for, more than once. Post each one as a question, in the customer's words. Then post the answer you already send. Mark that reply as the accepted answer. On Forumcat, the accepted answer pins under the question, so the next reader sees it first. Strip anything private before you post. Cut names, email addresses, invoice numbers, and account IDs. Keep the problem and the steps. The next customer needs the method, not someone else's details. Write the title the way a person would search. "How do I change the card on file" is a title. "Billing FAQ 4" is a filing label, and people do not search for filing labels. If you cannot find ten repeats, start with five. A thin, solved forum still works. An empty one does not. This is work you have already done. You are moving answers out of a private inbox and onto a page the next person can find. ## Send people to the forum A forum grows when you send people there, on purpose, for two weeks. Add the link to your site nav or help menu. Add it to your email signature. Add it to the auto-reply that goes out when someone writes support. Those three places are where customers already look. One buried page in a footer is easy to miss. When a repeat question arrives by email, answer it on the forum first, then send the person the link. You still helped them. You also left a page for the next person with the same problem. Say 20 emails a week ask how to reset a password, and each reply takes five minutes. That is 100 minutes a week on one question. One public thread, plus a line in the auto-reply, does that job after you write the answer once. Write the auto-reply in plain words. "We got your mail. You can also search past answers at \[forum address\]. If you find the same question, the accepted reply is the one that worked." Then keep moving repeats onto the forum when they show up again. People show up because you put the link in front of them and you keep doing it. That habit is the whole growth engine. ## Keep it healthy in 15 minutes a day Set a timer for 15 minutes. That is enough at the start. Answer new questions first. If a reply is the right one, mark it accepted so the thread shows as solved. Close what is done. Then look at searches that return nothing. Those queries are your next answers. A customer already told you the words they use. Post the question in those words, write the answer, mark it solved. If your tool does not show empty searches, keep a running note. When you or a teammate cannot find an answer, write the query down. That list is the same signal. One person who already answers email can keep a small forum current. Miss a day and nothing breaks. Miss two weeks and the place starts to look stale, which is when people go back to email and stay there. ## What to skip at the start Skip a custom domain until the forum earns it. A custom domain is your own address, like help.yourcompany.com. It looks like your site. It also is extra DNS work (the records that point a name at a server) on a day when you still need ten answers more than you need a prettier URL. Use the address the tool gives you. Move later, once people already use the forum. Skip gamification. That means points, badges, and leaderboards that try to make posting feel like a game. You do not have a crowd yet. You have ten threads and a habit. Badges on an empty board do not write the next answer. Skip extra categories. Skip extra moderators. One person who owns the 15 minutes beats five people who each think someone else will log in. Add those things when the forum is already in use. Keep reading: [how a self-service forum cuts support tickets](https://forumcat.com/blog/cut-support-tickets-self-service-forum) and [what a customer portal is](https://forumcat.com/blog/what-is-a-customer-portal), and [should you self-host your forum](https://forumcat.com/blog/self-host-or-buy-your-customer-forum), and [how to seed a new forum](https://forumcat.com/blog/seed-a-new-forum), and [a community guidelines template](https://forumcat.com/blog/community-guidelines-template). ## FAQs Q: How long does it take to set up a forum? A: With a hosted tool, the empty forum is live in minutes. Self-hosting takes as long as the server, the install, mail, SSL (the certificate that makes the address start with https), and the first backup. Plan hours, not minutes. Either way, the useful version takes a few hours more: categories, ten answers, and the links that send people there. Q: How many categories should a new forum have? A: Three to five. Name them in the words customers already use. Add more only when a category is full enough that people cannot scan it. Q: How do I get people to use the forum? A: Put the link where they already look: site nav, help menu, email signature, and auto-reply. When a repeat question arrives in email, answer it on the forum and send the link. Do that for two weeks. People use the place you send them to. Q: Should I self-host my forum? A: Self-host if you want full control and you already like running servers. Choose hosted if you want the forum without that job. Software on both sides can be good. The difference is who gets the update day. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## 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. --- ## Knowledge base vs community forum: which cuts more tickets? 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: Knowledge base vs community forum for support Meta Description: A knowledge base covers the questions you predicted. A forum covers the ones customers actually ask. An honest side-by-side to help you pick. URL: https://forumcat.com/blog/knowledge-base-vs-community-forum A knowledge base answers the questions you predicted and wrote down. A community forum answers the questions customers actually ask, including the ones nobody on your team saw coming. Both cut tickets. If you can only run one, decide by who writes the content. In a knowledge base that is always your team. On a forum the customer writes the question, and your team writes the answer once, in public. Most teams end up wanting both. Pick the one that fits how your customers behave today, then add the other. ## The real difference is direction A knowledge base is a set of articles your team writes and keeps. Someone decides a topic matters, writes the page, adds screenshots, and files it under a category. The work runs top down. The order is tidy, the tone is yours, and nothing goes live until you approve it. When the product changes, a person has to go back and edit the page by hand. A forum runs the other way. A customer posts a question in their own words, and someone on your team answers in public. Nobody planned that page. It exists because a real person needed it. The thread stays up, the next customer finds it, and the archive grows one question at a time. You never sit down to write it. You just answer. ## A knowledge base covers what you wrote, and nothing else The article model has a quiet cost. Every new edge case needs someone to spot it, agree it deserves a page, write the page, and publish it. That is four steps between a customer's problem and a page that solves it. Most of those steps wait on a week nobody has. On a forum the first step is free. The question writes itself the moment a customer types it. Your job shrinks to the answer, which you were going to write anyway in a private reply to that one person. The only change is that the reply is public and stays up. Try the math. Say twelve people a month hit the same odd setup problem. With articles only, that is twelve private replies until someone finally writes the page. On a forum, person one asks, you answer, and people two through twelve find the thread. The same work, done once. That is the whole idea behind [a self-serve forum that cuts ticket volume](https://forumcat.com/blog/cut-support-tickets-self-service-forum). ![Related questions suggested next to a thread in a Forumcat support portal](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/06-thread-related-questions-1788188148911-compressed.png) _The archive grows along what customers ask._ ## Both go wrong, in different ways Knowledge base articles go stale silently. A screenshot shows a button that moved last spring, and the page keeps ranking, keeps getting read, and keeps sending people to support with a new problem on top of the old one. Nothing on the page tells the reader it is out of date. Someone has to remember. Forum threads age in the open. Every post carries a date, so a reader can see the answer is from two years ago and read it with care. When something changes, a customer often says so in a follow-up reply, and your team can post a correction under the same question. Old threads get repaired instead of quietly rotting. Forums have their own failure modes, and they are real. An empty forum helps nobody and looks abandoned, so the first few months need your team to seed and answer. And customers sometimes post confident answers that are wrong. That needs a person watching, and a way to mark the correct reply so the right answer sits at the top. Most tools let the asker or your staff mark one reply as accepted, which fixes the ranking problem inside a thread. It does not fix the watching problem. Somebody on the team has to read the new posts. ![The questions list in the Forumcat dashboard where staff review and moderate threads](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/11-questions-light-1788188151847-compressed.png) _A forum needs a moderator, and the dashboard makes it a small job._ ## Customers start in Google, not in your search box Almost nobody opens your site and hunts through a docs menu. They type the problem into a search engine, in their own words, usually as a question. "Why does my export come out empty" is a search. It is rarely an article title. Forum threads match that shape by default, because a customer wrote the title. Article titles get written by people who know the product well, which is exactly why they use the internal word for the feature instead of the word the customer would use. You can fix that in articles with care and keyword work. On a forum you get it free. This is where a hosted Q&A portal earns its place. On [Forumcat](https://forumcat.com/support-forum), every answered public question ships QAPage structured data, so a search engine can read the page as a question with an accepted answer under it. And while a customer types a new title, the portal suggests threads that already answer it, so a good share of duplicates never get posted at all. ## Side by side Knowledge baseCommunity forumWho writes itYour team, every pageCustomers write the question, your team writes the answerCovers questions you did not predictNo, only what you thought to writeYes, that is the main thing it doesWorks from day one with no customersYes, write ten pages and launchNo, an empty forum needs seedingEditorial controlFull, nothing publishes without youPartial, customers post freelyGoes stale silentlyOften, nothing signals ageLess, posts carry dates and follow-upsNeeds moderationNoYes, someone reads new postsStep-by-step guides with screenshotsStrong, this is what it is forWeak, threads are answers, not manualsMatches how customers searchOnly with deliberate workBy default, titles are customer wordsEffort per new answerNotice, decide, write, publishAnswer the person who askedGrows on its ownNo, growth equals writing timeYes, along real demand The knowledge base wins the top of that list on control and on teaching. If you need a twenty-step setup guide with annotated screenshots, write an article. Nobody wants to read that as a forum reply. If you are weighing [alternatives to knowledge base software](https://forumcat.com/alternatives/knowledge-base-software), that is the trade to keep in mind. You give up some polish and gain coverage you could not have planned. ## How to choose Choose a knowledge base first if your product needs long tutorials, if your customers rarely talk to each other, or if you are pre-launch and have no customers to ask questions yet. Ten solid articles beat an empty forum every time. Choose a forum first if the same questions keep repeating in your inbox, if your customers phrase things in ways your docs never will, or if your product is broad enough that you cannot guess what people will hit. Also choose it if writing has stalled. A forum turns support replies you are already writing into pages, so the archive grows even in a week when nobody has time to write. Run both once either one is working. Articles carry the paths you can plan, threads carry everything else, and a [help center that holds both](https://forumcat.com/help-center-software) covers more ground than either alone. Many teams link out from an article to the thread where the awkward version of the question got answered. Starting the forum side is cheap enough that it is not much of a bet. A portal on a Forumcat subdomain is $9 one time, and the trial runs 7 days with no card. Give it a month of real questions and count how many threads get read more than once. Keep reading: [what a customer portal actually is](https://forumcat.com/blog/what-is-a-customer-portal) and [how a self-serve forum cuts support tickets](https://forumcat.com/blog/cut-support-tickets-self-service-forum), and [how to build a customer community](https://forumcat.com/blog/build-a-customer-community), and [forum vs FAQ page](https://forumcat.com/blog/forum-vs-faq-page). ## FAQs Q: Is a forum better than a knowledge base? A: Neither is better in general. A forum covers questions you did not predict and matches how people search. A knowledge base gives you control and handles long guides well. The right first choice depends on whether your customers ask a lot of varied questions or mostly need the same few tutorials. Q: Can a forum replace documentation? A: Not fully. Setup guides, reference pages, and anything with a fixed order belong in documentation. A forum handles the questions around the edges of your docs, and there are usually more of those than teams expect. Most teams keep docs and let the forum grow beside them. Q: Do I need content before launching a forum? A: Some, yes. An empty forum helps nobody. Seed it with the ten or fifteen questions your team already answers by email every week, post real answers to them, and it looks alive on day one. After that, customers supply the questions. Q: How do wrong answers get handled on a customer forum? A: Someone from your team reads new posts and replies with the correct answer, then marks the correct reply as accepted so it pins under the question. Wrong replies usually stay visible with the right one above them, which is honest and helps readers who tried the same wrong thing. The daily work is small once the habit is set, usually a few minutes. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## What is a customer portal? A plain-English guide 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: What is a customer portal? A plain-English guide Meta Description: Customer portal means three different things: an account portal, a help center, and a public Q&A portal. What each one does and which your customers need. URL: https://forumcat.com/blog/what-is-a-customer-portal A customer portal is a private or public place on your website where customers help themselves. They check on their stuff, find answers, or ask you things, without sending you an email. People use those two words for three different products. One is a login where a customer sees their own invoices, orders, and tickets. One is a help center of articles your team wrote. One is a public Q&A site where customers ask, you answer once, and everyone after can find that thread. Choose by the job you need done. Most companies end up with more than one. ## The same name covers three products You will see "customer portal" on pricing pages, in help-desk features, and in articles about letting customers help themselves. The label names three products. Buy the wrong kind and you still have the same inbox. ### An account portal shows one customer their own data An account portal is the login behind your product. After a customer signs in, they see their world: invoices, orders, licenses, shipping status, open tickets. Only that customer sees that page. Your staff can see it too, because you run the site. This kind is private and one-to-one, meaning one customer talking to you about their own record. It usually ships as part of a billing tool or a help desk. It is the right place for "where is my order?" and "send me last month's invoice." It cannot teach the next customer how to do the same task, because the next customer cannot see Jane's thread. ### A help center is articles you wrote ahead of time A help center is a public set of pages your team wrote. People also call this a knowledge base, which means the same thing: articles, written by you, published for anyone to read. It is one-way. You publish. They read. They cannot leave a new question on that page. Write a help center for setup guides, pricing, and anything that needs screenshots in a careful order. It will miss questions you never thought to document. It will also miss searches that use words you never put in the title. ### A Q&A portal lets people ask in public A community or Q&A portal is public and two-way. A customer asks a question other people can see. You answer it. That thread stays up. The next person with the same problem finds the page, often from Google, and does not have to write to you. This is the same job as a [support forum](https://forumcat.com/support-forum). Private mail still has a place: a refund, a bug in one account, a security issue. The public threads take the repeats. ![A public Forumcat customer portal home page with a list of answered questions and an Ask a question button](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/00-home-ask-hover-1788188154841-compressed.png) _The public kind: every answer stays findable._ ## Pick by the job, not by the label Customers keep asking to see last month's invoice. That is an account portal job. Customers keep asking how a feature works. That is a public answers job. The public layer might be a help center, a Q&A portal, or both. Most companies end up with one of each. The account login handles "my invoice." The help center handles the guides you want to write with care. The public Q&A layer handles the questions you did not predict. The common error is buying one kind and expecting it to do another kind's job. An account portal will not cut repeat how-to email, because those answers stay locked to one person. A help center will not show someone their last invoice. A Q&A portal will not run a refund for a single account. Your help desk still does that private, one-to-one work. A [customer support portal](https://forumcat.com/customer-support-portal) of the public kind sits beside it. ## A public answer serves more than one customer A private portal helps one person per visit. Jane looks up Jane's order. That page has no second reader. A public answer works for the next person too. You write it once. Every later searcher can use it. Customers start in Google. They type the problem in their own words. A thread titled in those words can appear in the results. Say 30 emails a week ask how to change a billing card, and each reply takes ten minutes. That is five hours a week on a single question. Answer it once on a public page. Put the link in the automatic reply your mail tool already sends. The next 30 people can read it. Some will still email. Many will not. That is why the public kind is the one that shrinks an inbox. The private kind still matters. It serves a different reader: this customer, this record, right now. If you want [customer questions and answers](https://forumcat.com/customer-questions-and-answers) to keep helping after the first asker is gone, they have to live where later people can find them. ## What a public Q&A portal needs to work A useful public portal needs a short list of jobs. It should live on your own domain (yourcompany.com) or a subdomain (a web address like help.yourcompany.com), so it sits next to the rest of your site. Search should cover every question and every answer. A customer who cannot find a match needs a way to ask. The asker or a staff member should be able to mark one reply as the accepted answer, so it pins under the question and the thread shows as solved. Staff replies should show the person's role next to their name, so an official answer looks official. People should be able to read and search without creating an account. Forumcat is a hosted customer Q&A portal on your domain. Customers read and search without an account, the accepted answer pins under the question, and staff replies show the person's role. A new portal is live in about five minutes. ![A Forumcat portal filtered to one category, showing billing questions grouped together](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/02-home-category-applied-billing-1788188157700-compressed.png) _One shelf per topic, named in customer words._ Categories give the portal shelves people can browse when they are not sure what to type. Keep the list short. Billing, Getting started, and Using the product will cover most teams. Name the shelves the way customers speak. A public answers layer can take the shape of a [community help center](https://forumcat.com/community-help-center), a Q&A list, or a support forum. The shared job is the same: one answer, many readers. ## When a help center is no longer enough You have outgrown "just a help center" when the same questions keep arriving by email even though the article exists. The page is live. People still write to you. They cannot find it, they do not trust it, or they describe the problem with words your docs never use. A help center is written in your voice. Customers search in theirs. "How do I cancel," "stop my plan," and "I was charged again" can all be the same issue. If your article is titled "Managing subscriptions," the person who typed "I was charged again" may never see it. A public Q&A thread starts with the customer's words. Later searches match because the question already used those words. Keep the help center for guides that need screenshots and a fixed order of steps. Add the Q&A layer for the questions that keep slipping past the docs. The longer split between articles and threads is in the [knowledge base vs community forum](https://forumcat.com/blog/knowledge-base-vs-community-forum) comparison. If you want to try a public Q&A portal, Forumcat is $9 one time on a Forumcat subdomain, or $99 a month for a custom domain. Keep reading: the [knowledge base vs community forum](https://forumcat.com/blog/knowledge-base-vs-community-forum) comparison, and [how to set up a customer support forum](https://forumcat.com/blog/how-to-set-up-a-customer-support-forum), and [how to build a customer community](https://forumcat.com/blog/build-a-customer-community), and [anonymous questions in a customer forum](https://forumcat.com/blog/anonymous-questions-in-forums), and [why public answers beat private email](https://forumcat.com/blog/public-answers-beat-private-email). ## FAQs Q: What is a customer portal used for? A: A customer portal is used so people can help themselves on your site. They look up their own orders or invoices, read answers, or ask a question without waiting on email. The exact use depends on which kind you built: private account data, public articles, or public Q&A. Q: What is the difference between a customer portal and a help center? A: A help center is one kind of customer portal: a public set of articles your team wrote. The same phrase also gets used for a private account login and for a public Q&A site. A help center is one-way. A Q&A portal is two-way. Q: Is a customer portal the same as a community? A: Sometimes people mean that, and sometimes they do not. A community is usually public and two-way: customers talk, and you talk back. An account portal is not a community. A help center is also not a community, even if it lives at help.yoursite.com. If the page only shows that one person's data, it is an account portal. Q: Do customers need an account to use a portal? A: For an account portal, yes. That is how you know whose invoices to show. For a public help center or Q&A portal, they should be able to read and search with no account. Asking them to sign up before they can even look is how you send them back to email. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## Cut support tickets with self-service (a practical guide) 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: Cut support tickets with self-service | Forumcat Meta Description: A practical week-one plan to cut support tickets: answer your top repeat questions once, in public, and let customers find them before they email. URL: https://forumcat.com/blog/cut-support-tickets-self-service-forum The short answer is simple. Find the questions your customers ask most, answer each one in public, and make those answers easy to find. That is the whole method. When you answer a question in a private email, the answer helps one person and then disappears. When you answer it on a public page, it keeps working for every person who asks next. Most support inboxes are full of repeats. So this one change takes real volume off a small team, without hiring and without buying a big new system. Here is how to set it up in about a week. ## What ticket deflection means Ticket deflection means answering a question in public once, so the next person with the same question never has to email you. The customer still gets the answer. They just get it in seconds, at 11pm, without writing a message and waiting until morning. That is why a deflected ticket is a win on both sides. Your team writes one careful answer instead of forty rushed ones, and the customer stops waiting. Deflection is not about hiding your contact form. If someone cannot find the answer, you want them to reach you fast. The goal is to make the easy questions easy, so your real support time goes to the hard ones. ## Why the same questions keep coming back Open your support inbox and read the last fifty messages. You will probably see the same handful of questions again and again, in slightly different words. There is a simple reason. New customers all walk the same path through your product, and they get stuck at the same steps. The person who signed up today hits the same confusing screen the person who signed up last Tuesday hit. Nothing about that repeats itself by accident. Email answers do not stop the cycle, because email is private. Your reply goes into one inbox and stays there. Nobody else can read it, search it, or link to it. If the person who wrote that great answer leaves the company, the answer leaves too. You end up paying for the same work over and over. Public answers behave the other way around. Write one, and it sits there and does its job every day without anyone touching it. ## The math of one public answer You do not need a study to see the size of this. Use your own numbers. Say one common question reaches you thirty times a year. Each reply takes about ten minutes once you count reading the message, checking the account, writing a clear answer, and switching back to what you were doing. That is 300 minutes a year, or five hours, for one question. Now say you have ten questions like that. Ten questions, thirty asks each, ten minutes an ask works out to about fifty hours a year. That is more than a full work week spent retyping things you already know. Writing those ten answers in public might take twenty minutes each, so a little over three hours in total. Even if only half of your customers find the public answer and the rest still email you, you save around twenty-five hours in the first year. And the answers keep paying out in year two, when you write nothing at all. Run this with your real numbers before you commit to anything. Whatever figure you land on, repeat answers will be among the most expensive things in your inbox, and they are also the easiest to remove. ## What self-service needs to work Plenty of teams write help pages and see no drop in tickets. Usually one of three parts is missing. The first part is answers a search engine can find. Your customers do not start on your help page. They start in Google, and they type your product name plus the thing that broke. If your answer is not in those results, it might as well not exist. The second part is search on your own site. Once someone lands on your portal, they should be able to type a few words and get the thread they need, without an account and without clicking through a menu of categories. The third part is a way to ask when nothing matches. This is where most help centers stop. A help center covers the questions you predicted when you wrote it. A [self-service portal built around questions](https://forumcat.com/customer-self-service) also covers the ones you never thought of, because customers write those questions for you, in their own words. Their wording is often closer to what the next person will search for than anything you would have written. (If you are weighing the two formats against each other, we wrote a longer piece on [how a knowledge base and a community forum differ](https://forumcat.com/blog/knowledge-base-vs-community-forum).) Forumcat is a [hosted support forum](https://forumcat.com/support-forum) built for exactly this job. Answered threads ship QAPage structured data, which is a small piece of markup that tells a search engine "this page is a question with an accepted answer", and anyone can read and search the portal without making an account. ![Search results in a Forumcat support portal showing answered questions matching the query webhook](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/03-search-webhook-1788188135310-compressed.png) _Customers search first; answered threads are what they find._ ## How to start deflecting this week You do not need a project plan for this. Five steps, and you can do the first three in an afternoon. 1. Pull your last fifty repeat questions. Scroll back through the inbox and copy each question into a list. Group the ones that are really the same question. Sort the list by how often each one shows up. 2. Post and answer the top ten yourself. Write them as real questions in the customer's words, not as tidy headings like "Billing overview". Post each one, then answer it properly. Yes, you are writing both halves. That is normal for a new portal, and it seeds the search index so the next visitor finds something. 3. Put the link everywhere email lives. Your signature, your auto-reply, your contact page, the footer of your product emails. Nobody uses a self-service page they have never seen. 4. Mark the correct answer on every thread. One reply gets marked as the accepted answer, and it pins under the question so a reader knows which reply to trust. A thread with five replies and no marked answer makes people email you anyway. ![A solved question thread in Forumcat with the accepted answer pinned under the question](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/06-thread-solved-1788188139254-compressed.png) _One accepted answer, pinned, findable forever._ 5. Watch the searches that return nothing. Empty searches are a list of the answers you still owe. Write those next, and you keep [deflecting tickets](https://forumcat.com/use-cases/ticket-deflection) month after month instead of once. One more thing that keeps a portal clean: while a customer types a new question title, Forumcat suggests existing threads that already answer it. Many people read the suggestion and never post, which stops duplicate threads before they exist. ## What self-service will not fix Self-service does not replace a help desk, and you should not plan for it to. Billing problems need someone to look at an account. Account-specific issues ("my export failed last night") need someone with access to logs. Bugs need someone to file them. Angry customers need a person, quickly. None of that belongs on a public page, and pushing it there makes the experience worse. What self-service removes is the repeats. That is the layer sitting on top of your help desk, catching the easy questions before they turn into tickets, so the tickets that do arrive are the ones that deserve a human. If you are also picking support tools right now, our notes on [what to check before buying help desk software](https://forumcat.com/blog/before-you-buy-help-desk-software) cover how the two fit together. Cost is not usually the blocker either. A Forumcat portal on a subdomain is $9 one time, and the trial runs seven days with no card, so you can test the top ten answers before you decide anything. Keep reading: [what to check before buying help desk software](https://forumcat.com/blog/before-you-buy-help-desk-software) and [knowledge base vs 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 [how to measure ticket deflection rate](https://forumcat.com/blog/ticket-deflection-rate), and [how to reduce repeat questions](https://forumcat.com/blog/reduce-repeat-questions). ## FAQs Q: What is ticket deflection? A: Ticket deflection is answering a question in public once so that future customers with the same question find the answer instead of contacting support. The customer still gets helped. Your team just does not write the reply again. Q: How do I reduce support tickets without hiring? A: Start with volume, not tools. Find the ten questions you answer most, publish clear public answers to them, and link that page from your email signature and auto-reply. Then check every month for searches that returned nothing and answer those. Most of the savings come from the first ten answers. Q: Do customers actually use self-service? A: Many people prefer it, because it is faster than waiting for a reply. The catch is findability. Customers use self-service when the answer shows up in a search engine, when your own site search works, and when the page is written in the words they used. When a portal gets ignored, the search path is usually the thing that broke, not the customer. Q: What is a good first set of questions to answer publicly? A: The setup questions new customers ask in their first week, your top three "how do I" questions, your pricing and plan limits, and anything that has ever caused a refund request. Keep them short and specific. Ten good threads beat fifty vague ones. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. --- ## Sample Page Author: Sai Krishna Author URL: https://forumcat.com/blog/author/sai-krishna Published: 2026-07-26 URL: https://forumcat.com/blog/sample-page This is a page. Notice how there are no elements like author, date, social sharing icons? Yes, this is the page format. You can create a whole website using Superblog if you wish to do so! --- This blog is powered by Superblog. Visit https://superblog.ai to know more. ---