When to use them
Some examples of how teams use groups in practice:- Beta programs, to flag customers trialing a feature before its general release
- VIP or strategic accounts that need faster response times or a dedicated agent
- Pilot cohorts in a structured onboarding or evaluation period
- Internal test users, so your own team’s threads don’t pollute your queue metrics
- Language or regional segments, to route threads to the right agent
- Churn-risk accounts flagged by your CSM team
Setting up groups
Go to Settings → Customer Groups. Each group has a name (shown in the UI), a key (a short slug used to identify the group in the API, likebeta-testers), and a color for the sidebar.
Adding customers to a group
There are three ways. Manually from a thread: open the thread, find the customer panel in the sidebar, and use the group picker. Via workflow rules: add “Add customer to customer group” as a workflow action. You can then automatically group customers based on triggers, like tagging anyone who contacts you through a specific Slack channel, without writing any code. Via the API: theaddCustomerToCustomerGroups mutation assigns a customer to one or more groups in a single call. Use this to keep group membership in sync with an external system, like updating groups whenever a plan changes in a billing platform. See the API docs for the full setup.

