PostHog Handbook Library / Support

193 words. Estimated reading time: 1 min.

Support team overview

The support team exists to help our users succeed with PostHog, and we do that differently than most support teams.

We're not a ticket-routing operation. We genuinely care about making our users' experience exceptional, which we do by being a deeply technical team that takes pride in solving problems ourselves. We write code, ship fixes, update docs, and build internal tooling to deliver that experience. We move fast, stay humble, and believe that great support is about empowering users, not just answering questions.

Slack channels to stay current

To answer customer questions well we need to know what's just shipped. The <PrivateLink url="https://posthog.slack.com/archives/C099B0YCULT"><code>#changelog</code></PrivateLink> internal channel keeps this in front of you — every member of the Support team should join it. It's owned by the Wizard & Docs team and updated constantly as PRs merge.

The channel is populated by agentic workflows that scan merged PRs and feature flag changes in the posthog/posthog repo and summarize them into it. PRs that are still behind a feature flag stay out, based on the Release status section of the posthog/posthog PR template. See how to publish changelog for the full flow.

Canonical URL: https://posthog.com/handbook/support/support-team

GitHub source: contents/handbook/support/support-team.md

Content hash: 74901d123e11d862

Static reader notes
  • MDX_COMPONENT_STATIC_ADAPTER: Adapted interactive MDX components for static reading: OurLongTermVision, PrivateLink, SmallTeam, SupportValues, WhatMakesUsGreat, WhatWeDo.