Slack for Salesforce customers
Slack is where many Salesforce users now see CRM data and work with AI agents. This guide covers what is available and how to plan for it.
Slack is Salesforce's collaboration product. For Salesforce customers, it is more and more the place where people see CRM records, receive alerts and work with AI agents without opening Salesforce. At Dreamforce 2026, Salesforce grouped many of these features under the name Slackforce.
What it is for
Slack helps teams discuss and act on work in channels instead of email. With Salesforce connected, a deal, case or approval can come to the people who need it, and they can respond in the same place. It also links organisations to partners and customers through Slack Connect.
Core capabilities
| Capability | What it does | Status notes |
|---|---|---|
| Slackbot | Slack's AI assistant | Slackbot MCP client and server GA in August 2026 |
| Salesforce in Slack (Slack CRM) | Work with Salesforce records in Slack | Part of Slackforce |
| Slackforce Surfaces | AI-built dashboards and reports in chat | Part of Slackforce |
| Slack Code | Coding-agent channels | Introduced 20 August 2026 |
| Enterprise Search and Channel Expert Agent | Find answers across connected content and channels | Check availability for your plan |
| Workflow Builder | No-code workflows inside Slack | Long-standing feature |
| Slack Connect | Shared channels with other organisations | Long-standing feature |
| Slack Frontline | Slack for frontline workers | Winter '27; status not stated |
Slack and Agentforce
Salesforce documents several links between Slack and its agents. Agentforce Coworker, which Salesforce lists as GA, answers questions across CRM and Slack and can call your deployed agents. Salesforce also lists Sales Cloud in Slack among its Winter '27 features. The Headless Experience Layer, which is rolling out, aims to let one experience render in Agentforce, Slackbot and other surfaces. Tableau Next is also Slack-integrated. Together, this makes Slack a front end for agents built on the Salesforce Platform.
Who it suits
Sales and service teams that already live in Slack, organisations working closely with partners, and companies rolling out Agentforce that want employees to reach agents where they already work.
Planning an implementation
- 01
Choose high-value moments
Pick a few events worth a Slack alert, such as large deals, escalated cases or approvals.
- 02
Map permissions
Check that people see only the CRM data their Salesforce access allows.
- 03
Design channels
Agree naming and ownership so alerts land somewhere people read.
- 04
Pilot with one team
Measure whether response times or hand-offs actually improve.
- 05
Add agents carefully
Introduce agent features in Slack once the underlying Salesforce data and permissions are sound.
Common mistakes
- Sending every record change to a channel until people mute it.
- Rebuilding Salesforce approvals as unconnected Slack workflows.
- Ignoring data visibility when CRM content is shared in channels.
- Planning around announced features before they reach your plan.
How GeekMidst can help
We can help you design the Salesforce side of a Slack rollout, from the automation that sends alerts to the agents people reach in Slack. See our Agentforce and AI automation services, Flow automation services and Salesforce CRM consulting.
Questions we hear
What is Slackforce?
Can Agentforce agents work in Slack?
Do we need Slack to use Agentforce?
Related reading
Record-triggered Flow best practices
Build reliable alerts and automation
→Service case notification journeys
Keeping customers and teams informed
→Salesforce programme governance
Keep tools and channels under control
→Tableau and Tableau Next
Analytics in the flow of work
→Bringing Salesforce into Slack?
We can help you choose the right alerts, workflows and agent features for your teams.
