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.

Get started

Where you can use it

Read and reply to customers in the Support inbox. You can also ask about support data in Slack, manage tickets over MCP, or build a custom experience with the API.

PostHog Web

Read and reply to customer tickets, each with the sender's replay and events in view.

Manage tickets →

PostHog Slack

Ask @PostHog about your support data.

Ask in Slack →

PostHog MCP

List and update tickets from any MCP client.

MCP tools reference →

API

Build a custom support experience on the posthog.conversations JavaScript API.

Build a custom widget →

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 →

Email

Forward support@ mail in, and replies thread back to the customer's inbox.

Connect email →

Slack aka SupportHog

SupportHog turns messages, mentions, or an emoji reaction into tickets.

Connect Slack →

GitHub

Issues in monitored repos become tickets, and replies post back as comments.

Connect GitHub →

Still have questions?

Was this page useful?