> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt # Support Canonical URL: https://posthog.com/docs/support ## On this page - [Where you can use it](#where-you-can-use-it) - [Where tickets come from](#where-tickets-come-from) - [We run our support on it](#we-run-our-support-on-it) - [Use cases](#use-cases) - [Free to use](#free-to-use) Support is one inbox for every customer conversation, with the sender's [session replay](https://posthog.com/docs/session-replay.md), 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. **Need help with PostHog?** These pages are for the Support product you run for your own customers. If you need help with PostHog itself, see [support options](https://posthog.com/docs/support-options.md). ![Support ticket list with status, SLA, assignee, and channel for each ticket](https://res.cloudinary.com/dmukukwp6/image/upload/w_1600,c_limit,q_auto,f_auto/support_tickets_1c0106fcfc.png) [Get started](https://posthog.com/docs/support/start-here.md) ## Where you can use it Read and reply in the [Support inbox](https://posthog.com/docs/support/inbox.md). 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 →](https://posthog.com/docs/support/inbox.md) SupportHog in Slack Raise tickets with `@SupportHog` or a `:ticket:` reaction, and reply in the thread. [Use Support in Slack →](https://posthog.com/docs/support/surfaces/slack.md) PostHog MCP List and update tickets from any MCP client. [Use Support over MCP →](https://posthog.com/docs/support/surfaces/mcp.md) API Build a custom support experience on the `posthog.conversations` JavaScript API. [Build a custom widget →](https://posthog.com/docs/support/javascript-api.md) ## 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 →](https://posthog.com/docs/support/widget.md) Email Forward `support@` mail in, and replies thread back to the customer's inbox. [Connect email →](https://posthog.com/docs/support/email.md) SupportHog (Slack) SupportHog turns messages, mentions, or an emoji reaction into tickets. [Connect Slack →](https://posthog.com/docs/support/slack.md) SupportHog (Microsoft Teams) Beta. Channel messages and `@SupportHog` mentions become tickets. [Connect Teams →](https://posthog.com/docs/support/teams.md) GitHub Issues in monitored repos become tickets, and replies post back as comments. [Connect GitHub →](https://posthog.com/docs/support/github.md) API The JavaScript API creates widget tickets. The compose API starts an email ticket from your backend. [Create tickets from code →](https://posthog.com/docs/support/concepts/channels.md#create-tickets-from-your-code) See [how channels work](https://posthog.com/docs/support/concepts/channels.md) 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](https://posthog.com/docs/support/slack.md) or [connect Microsoft Teams](https://posthog.com/docs/support/teams.md). ## 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](https://posthog.com/docs/self-driving.md) pull requests you review. [See use cases](https://posthog.com/docs/support/use-cases.md) ## 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](https://posthog.com/docs/support/ai-agent.md) is free while it is in beta. We will set a price later, and we will tell you before any charge starts. See [pricing](https://posthog.com/docs/support/pricing.md) for the limits.