What are the key considerations when designing a Slack-based Agentforce deployment?

Deploying Agentforce agents in Slack requires specific design considerations:

1. Slack channel context: Agents in Slack can be invoked via direct message or @mentioned in channels. Design Topics with awareness that channel messages may be less formal and more context-dependent than structured CRM inputs.
2. Slack Block Kit formatting: Agent responses in Slack are rendered as Block Kit messages — plain text, but with support for buttons (Quick Replies), section blocks, and dividers. Design action outputs to return structured data that maps to useful Slack card layouts.
3. Authentication: Users interacting with the agent in Slack are authenticated via Salesforce-Slack OAuth integration. Ensure the Slack user identity is correctly mapped to a Salesforce user for permission enforcement.
4. Conversation threading: Slack conversations happen in threads — ensure the agent maintains context within a thread and does not lose state between messages.
5. Action scope in Slack: Limit agent actions in public channels to read-only or low-risk operations. Sensitive operations (creating records, updating data) are better suited to direct messages where the interaction is private.
6. Notification vs conversation: Distinguish between agent-initiated notifications (proactive alerts via Slack) and reactive conversations — each requires different Flow and API designs.