AIArcsen sets up Slack with Salesforce for sales, service and operations teams in the Gulf and Egypt, so deals, cases and approvals are handled in channels tied to the Salesforce record. The aim is a CRM that stays current, because what is agreed in a conversation is written back to the record by Slackbot or a flow.
What we build
Slack around the record, with rules from day one.
Salesforce channels
We decide which accounts, opportunities, cases and campaigns get a Salesforce channel, who joins it and when it closes. Channels then follow the deals and cases that need a team, and what they decide is captured on the record.
Slackbot on CRM data
Slackbot answers questions from Salesforce data and Slack conversations, and can create or update records. Salesforce permissions carry over, so we review sharing rules and field access before switching it on for each team.
Swarming on service cases
Service Cloud swarming lets agents pull experts into a case, in Slack or on the record, and logs who took part. We set it up and agree with your service leads when a swarm should start.
Approvals and alerts through Flow
Salesforce Flow can post messages to Slack channels, and Slack workflows can run Salesforce flows. We use both for discount approvals and case escalations, with each decision written back to the Salesforce record.
Slack Connect for partners
Distributors, brokers and agencies can work with your teams in Slack Connect channels from their own Slack, with invitations approved by your admins. We decide which channels go external and keep customer records in Salesforce.
Security and retention
Enterprise+ adds native data loss prevention, audit logs and legal holds, with customer-managed encryption keys (EKM) as an add-on. We agree retention, external sharing and app approval rules with your security team, and configure them before the first channel opens.
Client work
Slack with Salesforce, in client work.
How we deliver
A few use cases first, then team by team.
Pick the first use cases
We choose two or three places where work stalls today, such as deal approvals, escalated cases or handover checks, and design the channels, workflows and record updates for those first.
Set the rules
Channel naming, retention, external sharing, app approvals and Salesforce connections are agreed with IT and security, written down and configured before the first users arrive, so nobody has to unlearn habits later.
Connect and test
We connect Slack to your Salesforce org, map users, check record access with real roles, and test Slackbot, flows and channels on sample deals and cases before go-live.
Review and extend
Each team gets a short session on its own channels and workflows. We review usage with team leads, retire what nobody uses and add the next use cases.
Questions we get
Asked by every buyer, answered straight.
Which Slack plan do we need?
New Salesforce customers now get a free-tier Slack workspace connected to their org, and Salesforce channels work on every Slack plan. Slackbot’s Salesforce actions need Business+ or Enterprise+, or an AI add-on on older enterprise plans. Enterprise+ adds data loss prevention, audit logs and legal holds. We match the plan to your first use cases.
Does Slack work in Arabic?
Only in part. Arabic is not one of Slack’s interface languages, and Slack’s help centre says it does not support right-to-left languages. We keep Arabic customer correspondence and case notes in Salesforce, which supports Arabic with a right-to-left layout in Lightning Experience, and use Slack for internal coordination.
Will Slack become a second CRM?
It can, without rules. Ours are short: decisions and next steps go back to the record, Slackbot or a flow writes the update, and a channel closes when its deal or case closes. Salesforce stays the system of record, and Slack is where people discuss it.
How does Agentforce fit into Slack?
Agentforce agents can run in Slack channels, threads and direct messages, so people use them where they already talk. We define each agent’s task, the data it may read and when it hands over to a person, then pilot it in one channel. Our free Agentforce Readiness Assessment takes ten working days and ends with three use cases and a pilot plan.
Fix permissions and data first, then let Slackbot read the CRM.
Start with a free Salesforce health check
Or talk to the team. See also: Zahid Group case study · Air Cairo case study.