> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/integrations/chat/slack/slack-community.md). # Slack Community Scalably support your Slack community bug and help channels by turning customer questions into Pylon issues. Funnel these questions into the rest of your support workflows and leverage your triage channel and kanban board to answer all support questions in one place. ## Use Cases Communities always have a help or getting-started channel where every message is a new question from a different user. You may even have many of these channels, separated by topic or experience levels.
UnificationUnify this support source with the rest of your support workflows in your triage channels and kanban so you can answer your customers from one place.integrate_padding.svg
Autocollect InfoAutomatically ask for more information so by the time you get there, your customer has already added the debug info you need.ai_Logo.svg
AnalyticsGet per account analytics on who is asking for support in your community. Filter down the more important customers in your community and understand how you’re supporting them.analytics_Logo.svg
## Setup When linking a new account in Pylon, select Community as the type. When you invite Pylon to a community channel in Slack, choose `Community Channel`. ## Behavior Before you try it out, here’s some things you should know… * In [Ticket settings](https://app.usepylon.com/settings/ticket-settings), a condition for **Pylon Account Type** is Community must use **Track all threads as tickets**. New Pylon workspaces include this as the **Community Accounts** condition. See [Ticketing Modes](/pylon-docs/integrations/chat/slack/support-ticket-flow.md#ticketing-modes). * Each new top-level message from a community member becomes its own ticket. Replies in its thread stay on that ticket. This is intentionally meant to help your customers start threads and keep your channels tidy. * Turn on **Add checkmark reaction when ticket is closed** so Pylon reacts ✅ to the original message when you're done, making it clear to your community where the queue stands. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.usepylon.com/pylon-docs/integrations/chat/slack/slack-community.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.