When using Service Cloud Swarming in Slack, one limitation is that new users added to a swarm channel cannot see historical messages that occurred before they joined. This behavior is based on Slack’s privacy and data-access model.
Swarming creates a new Slack channel or thread per case, enabling collaboration across departments, but message visibility for late joiners remains restricted.
Option A is incorrect—swarm channels are private by default to protect case data.
Option C is partially true (new channels are created for issues), but it is not the key consideration Salesforce identifies for planning purposes.
Referenced Salesforce Materials:
Salesforce Spring ’24 Release Notes – Service Cloud Swarming Enhancements in Slack.
Service Cloud Consultant Exam Guide – Service Cloud Solution Design Domain.
Salesforce Help: “Considerations for Using Swarming with Slack.”
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit