Support
Contents
Support is one inbox for every customer conversation, with the sender's session replay, events, and errors already attached. You see what went wrong instead of asking the customer to reproduce it.
In the API and the SDK, Support is called Conversations: the posthog.conversations methods, the $conversation_* events, and the disable_conversations option. The product is Support.
These pages are for the Support product you run for your own customers. If you need help with PostHog itself, see support options.
Where you can use it
Read and reply in the Support inbox. You can also work tickets from Slack with SupportHog, from an MCP client, or from the API.
PostHog Web
Read and reply to customer tickets, each with the sender's replay and events in view.
Manage tickets →SupportHog in Slack
Raise tickets with @SupportHog or a :ticket: reaction, and reply in the thread.
API
Build a custom support experience on the posthog.conversations JavaScript API.
Where tickets come from
A ticket can start in the widget, by email, in Slack, in Microsoft Teams, on GitHub, or from your own code. Each channel syncs both ways, so you answer from one inbox.
Widget
In-app chat button. Auto-attaches events, session replay, URL, and identity.
Set up the widget →SupportHog (Slack)
SupportHog turns messages, mentions, or an emoji reaction into tickets.
Connect Slack →SupportHog (Microsoft Teams)
Beta. Channel messages and @SupportHog mentions become tickets.
API
The JavaScript API creates widget tickets. The compose API starts an email ticket from your backend.
Create tickets from code →See how channels work for the full list, including how API tickets appear in the inbox.
We run our support on it
PostHog uses SupportHog for its own customer support. Enterprise and high-paying customers can have a shared Slack channel with us, or a Microsoft Teams channel if they prefer Teams. A message in a channel we mark as a support channel becomes a ticket. In any other channel with SupportHog in it, anyone in the thread, including the customer, can mention @SupportHog, or react with :ticket: in Slack.
That is the setup we recommend for B2B support. Connect Slack or connect Microsoft Teams.
Use cases
The same inbox covers in-app chat, a shared support@ address, GitHub issues, and a move off Zendesk or Intercom. Recurring bugs can become Self-driving pull requests you review.
Free to use
The widget, the inbox, every channel, workflow automation, and historical imports are free. There is no ticket cap and no per-seat charge. The AI agent is free while it is in beta. We will set a price later, and we will tell you before any charge starts. See pricing for the limits.