Now accepting projects — Q4 2026

// SALESFORCE · SLACK AI

AI on Slack — one workspace, clear roles, under control

Slack's own AI, Agentforce, Claude and ChatGPT can all work inside Slack. Nobody has decided which should answer what, what data each may see, or where that data lives. A CTA plans the roles and the governance, brings Salesforce data into the conversation safely, then builds the agents people will actually use.

  • Slack AI
  • Agentforce in Slack
  • Claude
  • ChatGPT / Codex
  • Slack MCP
# sales-key-accounts
  1. Sales lead

    @Agentforce Which deals are stuck in negotiation this week? And compare the contract drafts, please.

  2. AgentforceSALESFORCE

    3 opportunities have sat in negotiation for more than 14 days, sorted by amount with links. Only records you can see are listed.

  3. ClaudeTHIRD-PARTY AI

    I've put the payment-terms and warranty differences across the three drafts into a table in this channel's canvas.

ILLUSTRATION · One question: Agentforce answers from Salesforce, a third-party AI handles the documents
// SOUND FAMILIAR?

Everyone uses AI in Slack. Nobody manages it.

  • Every team buys its own

    Sales uses ChatGPT, engineering uses Claude, IT is trialling Slack AI. Licences overlap and nobody knows which ones get used.

  • CRM data stays outside the chat

    Customer issues are discussed in Slack, the answers sit in Salesforce, and people still copy and paste between two windows.

  • Security cannot answer the questions

    Which channels can a third-party AI read? Which country holds the data? Is it used for training? Without answers, the default is a blanket ban.

  • Agents nobody uses

    The pilot looked great, but it never reached the channels and processes people use every day. Three months later it's forgotten.

// TWO KINDS OF AI, ONE WORKSPACE

Built-in AI and third-party AI are good at different things

We are not tied to any vendor. We look at where your data lives, who will use it and for what, then decide which AI handles which part of the work.

FIRST-PARTY · SLACK & SALESFORCE

Native Slack and Salesforce AI

Data stays inside Slack and Salesforce permissions — the best fit for work that touches customer data and internal conversations.

  • Slack AI and Slackbot

    Conversation summaries, recaps, search answers, huddle notes and AI steps in Workflow Builder. Slackbot can find and act on Salesforce data from inside Slack.

  • Agentforce in Slack

    Employee agents built in Agentforce Builder, working in channels and DMs, reading and writing CRM data under Salesforce permissions, with custom Slack actions.

  • Salesforce channels

    Slack channels tied to records such as Accounts and Opportunities. View and edit records in Slack with Salesforce permissions still enforced.

THIRD-PARTY · CLAUDE · CHATGPT · CUSTOM

Third-party AI and custom agents

Strong at writing, analysis, code and cross-system work. What matters is which apps you approve and which data you open to them.

  • Claude Tag

    Anthropic's Claude joins chosen channels as a team member, keeps their context, and plans and follows up on tasks. Engineering teams can also hand coding tasks to Claude Code from Slack.

  • ChatGPT and Codex

    ChatGPT's Slack connector searches and summarises the Slack content a user may see. @ChatGPT in a channel can pass repository work to Codex in the cloud.

  • Custom Slack agents

    Slack's Agents & AI Apps surface, the Slack MCP server and the Real-time Search API turn your own models, knowledge bases and internal systems into agents inside Slack.

// WHAT WE ACTUALLY DO

Connecting Salesforce data with everyday collaboration

One CTA-led team designs, builds and runs the layer between Slack, Salesforce and AI.

  • Slack-to-Salesforce org connection, user mapping and permission design
  • Salesforce channels and record view / update flows in Slack
  • Agentforce employee agents, prompts and custom Slack actions
  • Approved-app lists and rollout settings for Claude, ChatGPT and other AI
  • Custom agents on Agents & AI Apps, MCP and the Real-time Search API
  • Workflow Builder automation and cross-system alerts (via MuleSoft where needed)

// GOVERNANCE & SECURITY

Decide what AI can seebefore you switch it on

Slack admins can open AI features by feature, by person or by group, and third-party apps and MCP clients need admin approval. We turn those settings into one clear policy, checked against Taiwan, Hong Kong and Singapore privacy laws and GDPR, and configure it once, properly.

See the Claude × Codex rollout & governance workshop
  • Who may use which AI

    ACCESS

    Slack AI features opened by team and role; third-party apps go through an approved list instead of self-service installs.

  • Where the data lives

    DATA

    Data-residency and AI-processing regions planned for your Slack plan, with the options and limits for Asian customers spelled out.

  • Only what each person may see

    PERMISSIONS

    Agentforce and Salesforce channels follow Salesforce permissions; we design custom agents to search with each user’s own permissions and keep no copy of Slack data, and test that before go-live.

  • Traceable when it matters

    AUDIT

    Agent actions, app approvals and setting changes are logged and included in the monthly run report.

// SERVICE CATALOG · SLACK AI

Decide who does what first — then put AI into the channels

Assess and plan, implement and build, roll out and run — every service can be bought on its own. Bring us in for a single readiness assessment, or hand the whole layer between Slack, Salesforce and AI to one CTA-led team. If you do not need another licence, we will say so.

CTA
CTA-designed architecture

Led by Taiwan's only Salesforce CTA. User mapping, permissions and data flows between Slack and Salesforce are settled before anyone builds.

Neutral
No AI vendor lock-in

Slack AI, Agentforce, Claude and ChatGPT split the work by use case; we recommend only the licences you actually need.

Governed
Governance before access

Who may use what, which channels each AI can read and where data lives — written as one policy and configured once, in terms security and compliance can follow.

One team
One team assesses, builds and runs

The people who assess are the people who build and the people who run it. No hand-offs, nothing lost in between.

PHASE 01 · ADVISORY

Assess & plan

Whether you are still choosing or every team already uses something different, start by seeing the current state and setting the rules. None of these require an implementation contract with us.

SF-SL1Start here

Slack AI Readiness AssessmentSLACK AI READINESS

Review licences, data and use cases, and decide what Slack AI, Agentforce and third-party AI should each handle.

  • Inventory of Slack plan, Salesforce licences and AI tools in use
  • Interviews and prioritisation of high-value use cases
  • Recommended AI for each use case
  • Licence gaps and overlapping licences you can drop

For companies already on Slack and Salesforce who want AI in everyday collaboration but are unsure where to start.

Format
2–3 weeks · fixed price
Deliverable
AI role map + licence advice + rollout roadmap
SF-SL2

AI Governance & Security DesignGOVERNANCE & SECURITY

Before any AI is switched on, decide who may use it, what it can see and where the data lives.

  • Slack AI feature access and the approved third-party app list
  • Data-residency and AI-processing region plan
  • Mapping to Taiwan, Hong Kong and Singapore privacy laws and GDPR
  • Side-by-side comparison of AI vendors’ data terms

For companies where security or compliance must sign off first, or where people have already installed AI apps on their own.

Format
2 weeks · fixed price
Deliverable
AI usage policy + admin configuration checklist
PHASE 02 · IMPLEMENTATION

Implement & build

Build the use cases ranked during assessment: connect Slack and Salesforce first, then Agentforce, then your own agents where needed.

SF-SL3

Agentforce in Slack RolloutAGENTFORCE IN SLACK

Let people query Salesforce and update records from Slack, with permissions still enforced.

  • Slack-to-Salesforce org connection and user mapping
  • Agentforce employee agent design, topics and actions
  • Salesforce channels and custom Slack actions
  • Testing, go-live and user onboarding

For sales, service or operations teams who discuss Salesforce customers and cases in Slack every day.

Format
6–10 weeks · priced by number of use cases
Deliverable
Live Agentforce agent + design documentation
SF-SL4

Custom Slack AI AgentsCUSTOM SLACK AGENTS

Turn your knowledge base, internal systems and chosen model into an agent inside Slack.

  • Agents & AI Apps surface, streamed replies and suggested prompts
  • Slack MCP server and Real-time Search API integration
  • Model choice: Claude, OpenAI or Agentforce
  • Internal app or Marketplace distribution plan

For companies whose internal knowledge off-the-shelf AI cannot answer, or whose work spans several internal systems.

Format
4–8 weeks · priced by scope
Deliverable
Live Slack agent + source code + runbook
PHASE 03 · MANAGED SERVICES

Roll out & run

AI only counts when people use it. Roll third-party AI out safely to every team, then keep tuning and tracking use and results.

SF-SL5

Claude & ChatGPT RolloutTHIRD-PARTY AI ROLLOUT

Connect Claude and ChatGPT to Slack safely, and show every team how to use them.

  • Admin set-up for Claude Tag, the ChatGPT connector and @ChatGPT
  • Channel and data access scoping
  • Claude Code and Codex workflows for engineering teams
  • In-person, hands-on training by team

For companies that have chosen Claude or ChatGPT and want one managed set-up instead of individual installs.

Format
3–4 weeks · fixed price
Deliverable
Live configuration + usage guide per team
SF-SL6

Slack AI Run & OptimiseRUN & OPTIMISE

Someone looks after your agents, settings and licences, and you see each month how the AI is being used.

  • Agent answer-quality monitoring and prompt tuning
  • Review of new Slack, Salesforce and AI vendor features
  • App approvals, permission and configuration changes
  • Monthly usage, results and licence report

For companies with AI live in Slack who need someone to maintain it and keep up with new features.

Format
Monthly · priced by scope
Deliverable
Monthly Slack AI run report
AI ADVISORY

Is your team new to Claude and Codex?

See in-person Claude × Codex training
FAQ

Four questions clients ask before rolling out AI on Slack

Slack AI, Agentforce, or Claude / ChatGPT?

Usually not one of the three. Use Agentforce where answers depend on Salesforce data and CRM permissions; Slack's built-in AI for summaries, search and everyday collaboration; Claude or ChatGPT for writing, analysis and code. The assessment works out the smallest set of licences your use cases need.

Will our Slack data be used to train models?

Slack states that customer data used by Slack AI never leaves Slack-controlled infrastructure and is not used to train any LLM. Third-party AI vendors have their own terms; we compare them side by side and recommend an admin-approved app list that controls which apps can read which channels.

Can our data stay in Taiwan or Hong Kong?

Not today. Slack's Asian data-residency regions are Tokyo, Singapore, Seoul, Mumbai and Sydney, and data residency needs a Business+ or Enterprise plan. Since November 2026 there is also a regional AI inference option, currently Japan only. We recommend the set-up that fits your compliance needs.

Can we build our own Slack AI agent?

Yes. Slack's Agents & AI Apps surface, MCP server and Real-time Search API connect your knowledge base and internal systems to Slack. Slack applies tighter API rate limits to distributed apps outside its Marketplace, so we usually build the agent as an internal app in your workspace, or plan a Marketplace route if you need one.

// NEXT STEP

See how AI should share the work in your Slack

Start with a Slack AI readiness assessment: we review your licences, data and use cases, and hand over a role split, a governance policy and a rollout roadmap.

We use cookies

We use strictly necessary cookies to run this site, plus optional analytics cookies (Google Analytics) to understand how visitors use it. See our Cookie Policy and Privacy Policy.