Product Support Hub

Server structure

Overview

Built for a company that supports one product and wants a person with a problem to find the right door in under a minute. #start-here is the first channel a member sees: it explains the three ways to get help and links to each. #faq is a forum where every answered question keeps its own thread and a tag (Getting started, Account, Billing, Setup, Fixed), so the same question stops being asked in chat. #status-updates and #release-notes are read-only feeds posted by the Product Team, and #open-a-ticket holds nothing but the ticket panel, so account and payment details never appear in public. #troubleshooting is an open forum tagged by platform, and #ask-the-community is the one public help channel, where Product Experts, customers who have earned the role by answering well, reply in the open. The Feedback category is a gate: only members holding Customer or Product Expert can post in #feature-ideas, which keeps drive-by requests out. The staff side is invisible to customers: #triage is where agents claim tickets, #needs-engineering is the hand-off to the Product Team, #saved-replies holds the answers agents paste most, and #ticket-transcripts is where Vetox files the record when a ticket closes. Two notification roles, Release Watcher and Status Alerts, let members choose which feed pings them.

When to use it

Your support inbox is a mix of the same five questions, real bugs and billing problems, and all of it lands in one general channel where it scrolls away. This layout gives each kind of request its own path: the FAQ forum answers the repeats once, the ticket panel takes the private cases, the status feed stops the 'is it down?' messages, and the hidden desk lets agents triage without customers watching.

What makes it different

• #faq is a tagged forum, so an answered question stays findable instead of being re-asked weekly.
• #status-updates and #release-notes are Product Team feeds; customers read, they do not reply.
• #open-a-ticket contains only the ticket panel, keeping account and billing details out of public view.
• The Support Desk category is hidden from customers: triage, engineering hand-off and transcripts.
• Product Expert is a role for customers who answer well, giving the community a visible helper tier.

Recommended Vetox setup

• Tickets

  Post the ticket panel in #open-a-ticket with options for Account, Billing and Bug, and send closed-ticket transcripts to #ticket-transcripts.

• Self-Roles

  Put a Self-Roles panel in #notify-roles so members opt into Release Watcher and Status Alerts pings instead of muting the server.

• Suggestions

  Point Suggestions at #feature-ideas so each request gets a vote and a status instead of a thread that dies.

• Embed Messages

  Write the #start-here explainer and the #how-to-guides entries as Embed Messages so they stay pinned, formatted and easy to update.

• Auto-Mod

  Enable Auto-Mod link filtering in #ask-the-community, where fake 'support' links are aimed at frustrated customers.