Agentforce Agent in Slack: Requires Explicit @Mention to Respond (Does Not Actively Listen)

How Agentforce Works in Slack Threads

When interacting with an Agentforce Employee Agent in Slack:

• The agent responds only when directly @mentioned.
• Each user receives an independent Agentforce session tied to their Salesforce identity.
• The agent does not continue listening after providing a response.
• Subsequent messages posted in the thread do not automatically trigger the agent.
• Thread history is provided to the agent as conversational context when a new session starts.
• The agent can reference previous thread messages but cannot resume an in-progress conversation flow that was initiated by another user.

Example

1. User A mentions the agent and asks a question.
2. The agent responds and requests additional information.
3. User B replies in the thread with the requested information but does not @mention the agent.
4. The agent does not respond.
5. User B must explicitly @mention the agent to start a new session and receive a response.

Why This Happens

Per-User Session Architecture

Agentforce Employee Agents operate using a per-user session model.

Each time a user invokes the agent:

• A new session is created.
• The session is associated with the invoking user's Salesforce identity.
• All actions performed by the agent execute using that user's permissions and access rights.

This design is required because Employee Agents may perform operations such as:

• Viewing Salesforce records
• Updating data
• Executing actions
• Accessing organization-specific information

All of these actions must occur within the authenticated user's security context.

No Shared Sessions

Agentforce does not support shared multi-user sessions.

As a result:

• User A's session cannot be continued by User B.
• User B cannot inherit the internal state of User A's conversation.
• Pending prompts, reasoning steps, and workflow state are not shared across users.
• Only the visible messages that appear in the Slack thread are available as context for future sessions.

Why @Mentions Are Required

The requirement to explicitly @mention the agent is an intentional product design decision.

If the agent remained active after an initial invocation, it could automatically respond to every subsequent message posted by the invoking user within the thread.

This could lead to situations where:

• Users are having human-to-human conversations.
• The agent unintentionally joins discussions.
• Responses are generated when no agent assistance was requested.

Requiring an explicit @mention ensures that users maintain control over when the agent participates in a conversation.

Thread Context Behavior

Although Agentforce creates a new session for every invocation, the Slack integration provides thread history as contextual input.

This means:

• The agent can see previous messages that were posted in the thread.
• The agent can use those messages to understand the conversation.
• The agent cannot access the internal state of previous sessions.
• The agent cannot continue a structured workflow that was started in another user's session.

Thread history acts as a transcript rather than a shared conversational session.