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, just walk over to the other person or send a DM/call.
Suggested configuration
- Enable notifications only for mentions and direct messages and the sync/notifying channels mentioned below.
- Set up
queue-<name>-x-<name>private channels to send non-notifying messages to colleagues. SLA to respond within 24 hours. - Set up
All unreadsin 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-<name>-x-<name> | 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 Plain. |
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 Plain
We use the following prefixes for channels
- customers:
ext-(synced in plain.com, plain app joins automatically) - partners:
partner-(not synced in plain.com) - vendors:
vendor-(not synced in plain.com)
All support/sales communication in ext-* channels happens via Plain.
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 who wants to be a member of all external channels. Everyone else can help out in this channel via the Plain integration, the App automatically joins all
ext-*channels. - 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 Plain 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 Plain. - 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.
Was this page helpful?