The Zendesk Community

The Zendesk community product, Gather, adds forums to your help centre. It's genuinely good software, and most teams that turn it on should not have.

Start free trial All guides

What the Zendesk community product gives you

Community forums live inside the same help centre as your articles. Topics contain posts, posts collect comments, and one comment can be marked as the official answer.

Search covers both articles and community posts, which is the real structural advantage: somebody looking for help finds your documentation and other customers’ answers in one result list. Moderators, content flagging and a moderation queue come with it.

It's an add-on rather than something every plan includes, so confirm what you have before planning around it. See the help centre guide for how the pieces fit.

When a community makes sense

Three conditions, and you want all three, not two.

Enough users that peers can answer each other. A forum with four posts a month reads as abandoned, and abandoned is worse than absent.

A product people configure. Communities thrive where there are many correct approaches: developer tools, platforms with integrations, anything with workflows. They wither around products with one obvious way to use them.

A reason for users to talk to each other. Feature requests, workarounds, showing off what they built. If every conceivable question has a definitive answer you could just document, write the documentation instead.

Notice what isn't on that list: reducing ticket volume. Communities do deflect, eventually, but the deflection arrives a year in, once the archive is deep enough for search to land on it.

The moderation load nobody budgets for

This is where community projects die, so be blunt with yourself about it before launching.

An open forum attracts spam within days of being indexed. Someone has to clear it, every working day, forever.

Unanswered posts are worse than spam. A question sitting for two weeks with no reply tells every visitor that nobody is home, and it's visible to search engines. In the first year, your team answers most posts, which means the community is a second support queue with worse tooling.

Wrong answers need handling with tact. A confident customer posting an outdated workaround is a support problem and a relationship problem at the same time.

Budget for a named owner spending a few hours a week. Not "the support team will keep an eye on it".

How it relates to the help centre

The healthy pattern is a pipeline, and it runs in one direction.

Questions appear in the community. The good answers get rewritten as proper articles, with an owner and a review date. The community post then links to the article. Over time the forum becomes the place where new problems surface first and the knowledge base becomes where the settled answers live.

What goes wrong is letting the forum become the documentation. Community posts are dated, unowned and written by whoever showed up. If your only guidance on a subject is a two year old comment thread, you've knowledge debt with a nice interface.

Zendesk lets a moderator escalate a community post into a ticket, which is worth configuring on day one. When a post is actually a support case, it needs to be in the queue, with an SLA, not sitting in a forum hoping.

The honest recommendation

If you have thousands of active users, a configurable product and somebody willing to own it, a community pays back well. It compounds: every answered question is a permanently searchable asset that you did not write.

If you've a few hundred customers and a stretched team, put the same hours into the knowledge base. Ten well written articles beat an empty forum every time, and you can always open the forum later. Closing one you've already launched is much harder.

FAQ

Frequently asked questions

Are Zendesk forums part of the help centre?

Yes. Zendesk forums are what Gather adds to your existing help centre, so the community sits under the same brand, theme and permissions as your articles.

Is Zendesk Gather included in my plan?

It's an add-on rather than standard on every plan. Check your account before designing a community around it.

Does a community reduce ticket volume?

Eventually, once the archive is deep enough to show up in search. Expect roughly a year of investment before deflection becomes measurable.

How much moderation does a Zendesk community need?

A few hours a week from a named owner: clearing spam, answering unanswered posts and correcting outdated advice. Shared responsibility means nobody does it.

Can community posts become tickets?

Yes, a moderator can escalate a post into a ticket. Set this up early so genuine support cases land in the queue with an SLA rather than lingering in the forum.