Internal Agents Map

Slackbot

Salesforce was 'customer zero' for the rebuilt Slackbot; an employee agent that finds company context, drafts work, and connects Slack context with Salesforce data; now also an external product.

Company
Salesforce
Approach type
Agent
Human involvement
Drafts reviewed
Invocation
Interactive
Interfaces
Slack
Deployment stage
Scaled
Evidence strength
Detailed primary
Entry reviewed
Copy as MDAsk ChatGPT

How it works

Employee request to a drafted briefing or shared Canvas in Slack.

Prepare a customer-meeting briefing

Pulls recent discussions, relevant documents, and customer history into a single, clear briefing before a critical customer conversation[Source 1]

Turn scattered analysis into a shared Canvas

In a documented demonstration, it correlated pilot feedback with an uploaded dashboard image, queried Salesforce for candidate accounts, and wrote the plan into a shared Canvas[Source 3]

Where people stay involved

People review, approve, or guide the agent’s work here.

Reported: Drafts are refined through conversation with the requesting employee; no approval gate beyond that user is documented.

  • Supervision level

    Work-product review

    A person reviews the draft or implementation.

    Level 3 of 5

    • employee request → drafted work[Source 1]

How supervision levels work

Implementation details

Model
Anthropic Claude (named via VentureBeat); additional providers planned within the year, with Google Gemini named and OpenAI possible[Source 3]
Harness
An employee agent intended as a front door to other agents[Source 1]
Sandbox
Not reportedThe interview describes an LLM with a robust search layer; no execution or isolation boundary is documented.
Tool access
Finds company context, drafts work, manages meetings, connects Slack context with Salesforce data[Source 1]Meeting booking was announced as arriving a few weeks after general availability; calendar availability checking shipped at launch.
Knowledge
Slack context joined with Salesforce CRM data[Source 1]
Context management
Not reportedGrounding in Slack context and conversation continuity are described; how context is maintained or organized over time is not.
Credentials
Permission-aware by construction; sees what the employee can see, respects roles and access controls[Source 1]The documented mechanism is data-access authorization bounded by the employee's permissions; credential storage is not described.
Interfaces
  • slack
[Source 1]

Mechanisms

Permission-aware context

Agent visibility is bounded by the invoking employee's permissions[Source 1]

Validation and failure handling

Not reported: The staged interview self-describes citing sources and admitting unknowns; no systematic check of outputs is documented.

Reported observations

These results come from the sources. Notes below each result explain what it covers and any reported limits.

Key observation

Two-thirds of Salesforce's roughly 80,000 employees tried the new Slackbot, and 80% of those users continued using it regularly[Source 3]

Reported by
Salesforce
Scope
Salesforce employees during the internal rollout; continuation measured among those who tried it

The source does not report the denominator of this figure.

Observed in January 2026

About this result
Category
Adoption output
Evidence type
Reported measurement
What it covers
Salesforce employees trying the new Slackbot during the internal rollout and continuing to use it
Key observation

Internal satisfaction reached 96%, and employees report saving between two and 20 hours per week[Source 3]

Reported by
Salesforce
Scope
Internal satisfaction rating and employee-reported weekly hours saved during the internal rollout

The source does not report the denominator of this figure.

Observed in January 2026

About this result
Category
Effectiveness
Evidence type
Reported measurement
What it covers
Internal satisfaction rating and self-reported weekly hours saved

Lessons

Salesforce used Slackbot internally before its phased customer rollout and describes itself as customer zero.[Source 1]

Salesforce says Slackbot uses Slack roles and access permissions to limit the information it surfaces.[Source 1]

Back to agents
Improve this record

Give your coding agent the context and instructions to prepare a source-backed update.

Paste the prompt into your coding agent, then describe the correction or add a public source.

Preview prompt

Sources and research details

Citations link to the original publisher. Each source also keeps a preserved copy in the repository, so a changed or removed page stays checkable.

  1. Salesforce announces general availability of Slackbothttps://www.salesforce.com/ap/news/press-releases/2026/01/14/salesforce-announces-the-general-availability-of-slackbot-your-personal-agent-for-work-sg/Release · First party · Last source verification: 2026-08-31
  2. Interview with Slackbot about connected work contexthttps://www.salesforce.com/in/news/stories/salesforce-slackbot-ai-interview/Corporate article · First party · Last source verification: 2026-08-31
  3. Salesforce rolls out new Slackbot AI agenthttps://venturebeat.com/technology/salesforce-rolls-out-new-slackbot-ai-agent-as-it-battles-microsoft-andNews · Independent secondary · Last source verification: 2026-08-31
  4. Hacker News submission for the Salesforce Slackbot rollouthttps://news.ycombinator.com/item?id=46600760Hn thread · Community · Last source verification: 2026-08-31
Question coverage and scope
purpose
Reported
workflow
Reported: The briefing run is from the launch post; the Canvas run is the documented product demonstration. Both are employee-initiated.
human involvement
Reported: Drafts are refined through conversation with the requesting employee; no approval gate beyond that user is documented.
implementation
Reported
validation
Not reported: The staged interview self-describes citing sources and admitting unknowns; no systematic check of outputs is documented.
observations
Reported
lessons
Reported
Research details for every claim on this page
  1. Summary
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Not assessed
    Confidence reason
    No explicit confidence assessment is recorded for this claim.
  2. Harness
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Not assessed
    Confidence reason
    No explicit confidence assessment is recorded for this claim.
  3. Model
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Not assessed
    Confidence reason
    No explicit confidence assessment is recorded for this claim.
  4. Interfaces
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Not assessed
    Confidence reason
    No explicit confidence assessment is recorded for this claim.
  5. Tool access
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Not assessed
    Confidence reason
    No explicit confidence assessment is recorded for this claim.
  6. Knowledge
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Not assessed
    Confidence reason
    No explicit confidence assessment is recorded for this claim.
  7. Credentials
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Not assessed
    Confidence reason
    No explicit confidence assessment is recorded for this claim.
  8. Permission-aware context
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Not assessed
    Confidence reason
    No explicit confidence assessment is recorded for this claim.
  9. Prepare a customer-meeting briefing
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Not assessed
    Confidence reason
    No explicit confidence assessment is recorded for this claim.
  10. Turn scattered analysis into a shared Canvas
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Not assessed
    Confidence reason
    No explicit confidence assessment is recorded for this claim.
  11. Key observation
    Statement type
    Metric
    Provenance
    Reported
    Confidence
    Medium
    Confidence reason
    Salesforce internal adoption figures relayed by VentureBeat without a measurement method or window.
    Reported by
    Salesforce
    Scope
    Salesforce employees during the internal rollout; continuation measured among those who tried it
    Denominator
    Not reported
    Method
    Not reported
    Observation date
    2026-01
  12. Key observation
    Statement type
    Metric
    Provenance
    Reported
    Confidence
    Medium
    Confidence reason
    Salesforce internal satisfaction and self-reported time savings relayed by VentureBeat; no survey method or baseline is given.
    Reported by
    Salesforce
    Scope
    Internal satisfaction rating and employee-reported weekly hours saved during the internal rollout
    Denominator
    Not reported
    Method
    Not reported
    Observation date
    2026-01
  13. Lesson
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Medium
    Confidence reason
    The launch post includes an internal-use account alongside the rollout dates; it does not demonstrate that internal-first release is best for other products.
  14. Lesson
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Medium
    Confidence reason
    The product announcement makes this permission claim but does not expose the enforcement implementation or independently test its effectiveness.
  15. Operating model assessment
    Statement type
    Inference
    Provenance
    Catalog judgment
    Confidence
    Medium
    Confidence reason
    The source describes an employee agent that prepares drafts and contextual work for human use.
    Observation date
    2026-01-14