Pylon
Knowledge BaseWebsiteChangelogBook a DemoLogin
  • Getting Started
    • Introduction
    • Quick Start
    • Slack Setup
    • Channel Configuration
    • User Guide
  • Support Workflows
    • Omnichannel Support
    • Issues
      • Views
      • Statuses
      • Message Editor
      • Copilot
      • Internal Threads
      • Proactive Issues
      • Translation
      • Bulk actions
      • Issue Groups
    • SLAs
    • Support Hours
    • CSAT
    • Ticket Forms
    • Assignment Rules
      • User Status
    • Email
  • Platform
    • Custom Fields
    • Required and Conditional Fields
    • Tags
    • Teams
    • Triggers
      • Logs & History
    • Macros
    • Command Search
    • Roles & User Management
    • Training Data
    • Ask AI
  • AI Agents
    • Overview
    • Build
      • Resources
    • Test
  • Knowledge Base
    • Overview
    • Articles & Collections
      • Editor
      • Copilot
      • Templates
      • Collaboration
    • Knowledge Gaps
    • Styling & Customization
    • Custom Authentication
    • Search
    • Translation
  • Customer Portal
    • Overview
    • Styling & Customization
    • Access Control
    • Portal Experience
    • Custom Authentication
  • In-App Chat
    • Overview
    • Styling
    • Functionality
    • Chat Experience
    • Chat Setup
    • Identity Verification
    • JavaScript API
  • Account Management
    • Accounts
    • Views
    • Notebooks
      • Blocks
    • Highlights
    • Fields
    • Copilot
    • Activities
      • Custom Activities
  • Reporting & Analytics
    • Analytics
    • Default Dashboards
    • Custom Dashboards
  • Broadcasts
    • Overview
    • Create a Broadcast
    • Analytics
  • Integrations
    • CRM
      • Salesforce
      • Hubspot
      • Attio
      • Pipedrive
    • Ticketing
      • Linear
      • GitHub Issues
      • Asana
      • Jira
    • Alerting
      • PagerDuty
      • Opsgenie
    • Chat
      • Slack
        • Internal Threads
        • Collect Data
        • Support Ticket Flow
        • Welcome Message
        • Bookmarks
        • Onboard Employees
        • Left Company
        • Slack Community
      • Microsoft Teams
      • Discord
    • Incident Management
      • incident.io
    • Call Recording
      • Gong
      • Fathom
      • Grain
      • Fireflies
  • Data Warehouse
    • Snowflake
    • BigQuery
  • Developer
    • API
      • Authentication
      • Errors
      • API reference
        • Attachments
        • Accounts
          • Activities
          • Highlights
        • Contacts
        • Custom Fields
        • Issues
        • Knowledge Base
        • Me
        • Messages
        • Tags
        • Teams
        • Ticket Forms
        • User roles
        • Users
      • External IDs
    • Custom Apps
    • Embedded Iframes
    • Webhooks
Powered by GitBook
On this page
  • ​Use Cases
  • Setup
  • Behavior

Was this helpful?

  1. Integrations
  2. Chat
  3. Slack

Slack Community

PreviousLeft CompanyNextMicrosoft Teams

Last updated 7 months ago

Was this helpful?

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.

Setup

When linking a new account in Pylon, select Community as the type.

Behavior

Before you try it out, here’s some things you should know…

  • Every message in the channel will turn into an issue.

  • Every issue must have a threaded message under it (we’ll configure this on the next page). This is intentionally meant to help your customers start threads and keep your channels tidy.

  • After you’re done with the issue, we will react ✅ emoji onto the thread so it’s clear to your customers where the queue stands.

​
Cover

Unification

Unify 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.

Cover

Autocollect Info

Automatically ask for more information so by the time you get there, your customer has already added the debug info you need.

Cover

Analytics

Get 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.