--- title: Using Slack description: How we use Slack for internal and external communication. --- # Using Slack We use Slack for internal comms and to chat with customers, partners, and vendors. When joining the team, you can sign up for Slack (`langfuse.slack.com`) via your Google account. We use Slack mostly asynchronously to reduce noise and allow everyone to focus on their own work. If you need something urgent, send a DM, start a call, or — if you're both in the office — tap someone on the shoulder. See [Working Remotely](/handbook/how-we-work/remote) for broader async norms. ## Suggested configuration - Enable notifications only for mentions and direct messages and the sync/notifying channels mentioned below. - Set up `queue--x-` private channels to send non-notifying messages to colleagues. SLA to respond within 24 hours. - Set up `All unreads` in the main menu in order to quickly get through the backlog of unread messages. ## Most important channels | Channel | Purpose | | ------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | `team` | General team chat (notifying) | | `team-async` | General team chat (non-notifying, suitable for most messages) | | `engineering`, `product`, `user-feedback`, `market-insights`, `media-recommendations`, `marketing`, `growth` | Topical channels (non-notifying) | | `incidents` | Incident communication (notifying) | | `memehq` | Arguably the most fun channel | | `ai-trickshots` | Show off what you've got done with AI (non-notifying) | | `queue--x-` | Private channel for non-notifying messages between team members | | `ext-*` | Customer communication. Sales/GTM has some notifying in order to drive the conversation forward. Rest of team can mute them as they are managed via Pylon. | | `vendor-*` | Vendor communication. Join the channels which are relevant to you. | | `partner-*` | Partner communication. Join the channels which are relevant to you. | ## External channels For some prioritized customer groups, we use shared Slack Connect channels for support and sales. ### Sync to Pylon We use the following prefixes for channels - customers: `ext-` (synced in Pylon, Pylon app joins automatically) - partners: `partner-` (**not** synced in Pylon) - vendors: `vendor-` (**not** synced in Pylon) All support/sales communication in `ext-*` channels happens via Pylon. ### Create new external Slack connect channel - Use the appropriate channel prefix (e.g., `ext-`, `partner-`, `vendor-`) - Shared channels should be public channels as this allows for discovery within the customer's Slack organization. - When creating an `ext-*` channel (customers): - Invite external members - Invite internal members explicitly, do not make the channel a default channel for everyone. Only invite Clemens and Akio who want to be a member of all external channels. Everyone else can help out in this channel via the Pylon integration, the App automatically joins all `ext-*` channels. - **Private channels:** The Pylon app cannot automatically join private channels. You need to manually: 1. Add the Pylon app to the channel (in Slack, open the channel → click the channel name → _Integrations_ → _Add apps_ → search for Pylon). 2. Add the Slack channel as an account in Pylon: [app.usepylon.com/customers/accounts/add](https://app.usepylon.com/customers/accounts/add). - Optionally: once you see that the external members joined, share a welcome message in the channel and then mute the channel on Slack. From then on, you can help out in this channel via the Pylon integration. ### Configure Slack for external channels - For most channels and most team members: you can mute or leave the existing `ext-*` channels. You will get assigned to threads via Pylon. - For high-value accounts, the person managing the relationship should stay in the channel as this makes it easier to outbound engage the customer → use direct channel to our advantage to be close to the most important customers. --- ## Agent Instructions This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/handbook/tools-and-processes/using-slack.md`. ### Querying these docs If the answer is not on this page, query the documentation instead of guessing: - **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question: ```bash curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?" ``` - **Index of every page**: , with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt). ### Before writing Langfuse code - **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results. - **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application. - **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples. - **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api `) to read or write traces, prompts, datasets, and scores from the terminal. Found an error in these docs? Please open an issue at .