In every channel, you will have Customers (people who create tickets when they post) and Agents (people who can respond to tickets).For shared Slack Connect channels, anyone who is outside of your email domain will automatically be marked as a customer, and anyone in your Slack workspace will be an agent.For internal support channels, anyone who is an “admin” or “agent” of that channel profile will have access to agent features, and anyone else will be considered an internal customer.You can override these settings by navigating to the “Channels” menu in the left, then select the channel you’d like to update, then select “Manage Role Overrides” in the top right. You will then see the following options:Override Teammate ListWhen enabled, only users/groups added to the list below will be treated as internal teammates in this channel (overriding project defaults). If this list is empty, no one is considered a teammate by default in this channel.Override Customer ListWhen enabled, users/groups added to the list below will always be treated as external customers in this channel, overriding all other classifications for them. If this list is empty, no users/groups are explicitly forced to be customers by this specific override (other rules still apply for others).
We know that some customers love threads and some despise them! Fortunately, Unthread is able to group conversations together regardless of whether messages come in threads or the top level of the channel.
Top-level messages are grouped into conversations based on a time interval between messages from the same user. This defaults to 1 hour but you can change this in your Slack settings under the “Group top-level messages” setting.
Threads are always tracked as individual conversations
If you have a conversation happening on the top level, you can thread off of a message to automatically split and create a new conversation out of that thread
If you have multiple conversations that you’d like to combine, you can also merge conversations
If you have a conversation that you’d like to split into multiple conversations, you can split a conversation
In this example where Sam is the customer and Tom is the support agent, the top-level messages will be grouped into a single conversation. If you choose to create a new thread off of one of those individual messages, that will automatically become its own separate conversation. Any replies in the top level will remain tracked to the initial conversation.