Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.whop.com/llms.txt

Use this file to discover all available pages before exploring further.

Support chats are one-on-one conversations between a customer and your company. Use them when the conversation is official support, needs to be visible to team members, or should have an open/resolved workflow. Unlike direct messages, support chats are organized around a customer support relationship with your company. They are best for customer service, not peer-to-peer messaging.

​
When to use support chats

Use support chats when your team needs to respond to customers as the company. Examples:
  • A help inbox for paid members
  • A billing or account support conversation
  • A buyer support thread after checkout
  • A creator-to-customer support line
  • An escalation path from your app into Whop-hosted chat UI

​
What makes support chats different

Support chats are the chat type for official customer-to-company conversations.
  • Each support chat connects one customer with your company.
  • For the customer, the conversation behaves like a normal DM-style chat and can appear in their DMs list.
  • For team members, support chats are organized around a support inbox with open and resolved states.
  • Team members can list, sort, and filter support chats by customer, status, and admin/team view.
  • Moderators can help respond to support chats without getting full company admin access.

​
Constraints

  • Support chats are not for group user-to-user conversations. Use direct messages for that.
  • Support chats do not appear in the DMs list component for admins. Build a support inbox with the support channels API instead.
  • Support chats do not grant product or membership room access. Use channels for member-only rooms.
  • Support chats are not peer-to-peer DMs. Use direct messages when users should message each other directly.

​
Access model

A support chat belongs to a company and a customer. Team members with support access can list and respond to support chats for the company. The customer can render and participate in their own support chat when authenticated with the required support scopes. If someone on your team should help manage support chats without getting full admin access, add them as a team member with the moderator role. Moderators can help handle customer conversations while keeping broader company settings locked down.
Support chat IDs start with feed_.

​
Set up a support chat

1

Sync or identify the customer

You need the customer’s Whop user ID or username. If your app has its own user system, map users first with Sync your users.
2

Create the support channel

Use Create Support Channel. Whop returns the existing support chat if one already exists for that customer.
3

Render the conversation

Pass the returned support channel ID to the Chat element.
4

List support chats for your team

Use List Support Channels to build an inbox for your team.
Then render the support chat with the returned channel ID: 
<ChatElement
  options={{ channelId: "feed_XXXXXXXXXXXXXX" }}
  style={{ height: "100dvh", width: "100%" }}
/>

​
Manage support chats

Use Create Support Channel, List Support Channels, and Retrieve Support Channel to manage support chats. Support chats also support inbox-style workflows. You can build views for open conversations, resolved conversations, customer-visible conversations, and team/admin views. See List Support Channels for the available filters.

​
Next steps

Chat element

Render a support chat after you create or retrieve it.

Authentication

Add support chat scopes to your token endpoint.