Agentforce in Slack, or a custom app?

If the work and the permissions live in Salesforce, use the org-native path. If the agent has to reach systems Salesforce does not own, a custom Slack app through the gateway is usually cleaner.

Will the agent read every channel?

No. Scope it to the channels and the data the desk already has. A bot with workspace-wide history is a finding, not a feature.

Is WhatsApp the same pattern?

The pattern is the same, the constraints are not. In the Gulf, WhatsApp is often the honest choice for customer-facing work. We will say which surface fits.

Salesforce MVP Hall of Fame · Certified Partner since 2010

The desk already lives in Slack.

The first week is in the org, reading what already exists. If the team works in Slack, that is where the agent belongs: a command that acknowledges immediately, a modal that shows what is about to happen, and an approval that writes back to the record. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.

Send the brief

In the org

What a Slack agent actually needs.

A Slack surface is not a chat window bolted onto a prompt. Four things decide whether people keep using it.

01
Acknowledge fast
A response inside a second, before the work starts. Silence is why people abandon a bot.
02
Carry the person
The request runs as the Slack user, not as an app with everyone’s permissions. Identity is exchanged at the gateway.
03
Show the action
A Block Kit modal or card that states the intended write, then asks. Approval after the fact is not approval.
04
Write and report
The record changes through the durable path, and the thread gets the outcome and a link.

A governed Slack agent. The command acknowledges at the edge, the request passes the gateway with the user’s identity, the runtime does the work, and the approval writes back to the system of record.

Mermaid source

flowchart TD
  A["Command, mention, or app home"] --> B["Immediate acknowledgement"]
  B --> C["Gateway: on-behalf-of identity and policy"]
  C --> D["Runtime: Agentforce or a code agent"]
  D --> E["Modal: what is about to happen"]
  E --> F["Approval"]
  F --> G["Durable write to Salesforce or ERP"]
  G --> H["Thread update and trace"]

Why it matters

Slack is the cheapest place to earn trust.

01No new tool to learnAdoption is the hardest part of an agent programme. A channel people already read removes most of it.

02Approvals where people areA human gate only works if the approver sees it in minutes. That is a messaging surface, not an email digest.

03Exceptions get ownersA dead-letter lane posted into a channel with a named owner beats a dashboard nobody opens.

04It is not a licence to leakA channel is a wide audience. Field-level redaction and scoping matter more here, not less.

In an org

A service desk and one agent command.

How Mindcat helps

One command, one desk, one week of watching it.

Questions

What we actually say.

Agentforce in Slack, or a custom app?: If the work and the permissions live in Salesforce, use the org-native path. If the agent has to reach systems Salesforce does not own, a custom Slack app through the gateway is usually cleaner.
Will the agent read every channel?: No. Scope it to the channels and the data the desk already has. A bot with workspace-wide history is a finding, not a feature.
Is WhatsApp the same pattern?: The pattern is the same, the constraints are not. In the Gulf, WhatsApp is often the honest choice for customer-facing work. We will say which surface fits.

What to read next.

The brief

Name the channel and the command.

We will tell you whether Slack is the seat, and what it may not see.

The desk already lives in Slack.

flowchart TD A["Command, mention, or app home"] --> B["Immediate acknowledgement"] B --> C["Gateway: on-behalf-of identity and policy"] C --> D["Runtime: Agentforce or a code agent"] D --> E["Modal: what is about to happen"] E --> F["Approval"] F --> G["Durable write to Salesforce or ERP"] G --> H["Thread update and trace"]