Support
Contents
Support gives you one inbox for every customer conversation, whether it arrives from your app, your email, or a GitHub issue. Because PostHog already knows what's happening in your product, each ticket comes with the sender's session replay, events, and errors attached, so you can see what went wrong instead of trying to reproduce it. Those same conversations feed Self-driving, which groups recurring issues into pull requests you review and merge.
Where you can use it
Support does different things depending on where you work. You read and reply to customers in the Support inbox. The other surfaces are for reviewing the Self-driving work your tickets generate.
Web
Read and reply to customer tickets, each with the sender's replay and events in view.
Manage tickets →Slack
Ask @PostHog about your support data and review Self-driving reports built from your tickets.
MCP
List and update tickets and manage Self-driving reports from any MCP client.
MCP tools reference →Code Beta
Review and merge Self-driving reports and PRs built from your tickets, next to the agents improving your product.
PostHog Code →API
Build a custom support experience on the posthog.conversations JavaScript API.
Where tickets come from
Tickets reach your inbox through four channels. Each one syncs both ways, so you answer from a single place no matter where the conversation started.
Widget
In-app chat button. Auto-attaches events, session replay, URL, and identity.
Set up the widget →Slack aka SupportHog
SupportHog turns messages, mentions, or an emoji reaction into tickets.
Connect Slack →How Support works with Self-driving
Your support conversations are a signal source for Self-driving: recurring issues become reports, and when there's a code fix, a pull request you review and merge.
You read and reply to customers in the Support inbox, and review and merge the Self-driving work in the Self-driving inbox. See the Self-driving docs for the full picture.