DEMO

IBM Bob inside Slack

IBM Bob joins your Slack as a Salesforce architect: it reads a case, proposes a fix, builds and deploys it, with people approving every step.

Building Blocks used:

ai.engineering

Skills used

Download skills for IBM Bob →

headless-bob

Products Used

IBM Bob

1 Review use case

IBM Bob joins your Slack as a Salesforce architect: it reads a case, proposes a fix, builds and deploys it, with people approving This demo brings IBM Bob, IBM's AI development partner, into Slack, where your team already works, and shows its agentic harness handling a real Salesforce request from case to deployed change. A sales manager files a case: when a deal closes, the Success Plan is created manually days later, so handoffs slip, onboarding starts late and renewals suffer. Without Bob, the request joins the admin backlog of clarify, design, build, test and deploy, which takes days or weeks of mostly waiting. With Bob, it is picked up the moment it arrives.

Bob summarizes the case and proposes a solution: the problem, the fix, why it matters and the skills it applied. With custom Bob skills with Salesforce domain knowledge, Bob responds like an experienced Salesforce architect, and swapping in your own skills makes Bob respond in your domain. The team can push back at any point, asking Bob to explain its reasoning, and the answers are specific to the case rather than boilerplate. A team admin approves the proposal and Bob writes a use-case summary onto the case record in Salesforce, so anyone picking it up later sees what was decided and why. A second approval triggers the build: a new field on the Success Plan object and a flow that creates a Success Plan whenever an opportunity closes as won.

Once deployed, the team inspects exactly what was built through direct links to Salesforce Setup and tests it live: closing a deal as won creates the Success Plan within seconds, fills it with the opportunity details and notifies the account owner. A final approval closes the case, the requester receives a closure email and the channel is archived. Three approvals, zero code typed, one real change in a live Salesforce org, with every action attributed and traceable. The team defines the skills, approvals and connected systems, so the same harness could just as well end in a pull request, a ticket update or a change in any system with an API or MCP server.

Start Here

Watch this short overview

Preview the application

Explore key screens from the demo

2 Try the interactive application

Experience the interactive demo and explore its features. A demo script is provided to help when presenting the application to partners.

Have questions, want a walkthrough or found a bug?

Contact the demo owner for assistance.

Submit a request →

3 Explore how it was built

Three major components. Slack is the team's interface: a Slack app delivers messages and button clicks to the service over signed requests, and each case gets its own channel with approval buttons. The Headless Bob service is a single container that holds everything in the middle: a case state machine that advances only on a click, Bob Shell started over the Agent Client Protocol with Salesforce skills loaded, a read-only MCP endpoint that answers Bob's describe and query calls with the service's own session, a governance layer with a permission policy, budgets and an audit record per turn, and a package pipeline that collects the metadata Bob writes, validates it against the org with a check-only deploy, snapshots what it touches, deploys, and reverts. The Salesforce org is reached only by the service, through the REST API for the case record and the Metadata API for the change. Bob reads the org through the endpoint and writes files into its workspace; it never holds a credential, and nothing reaches the org without the service and a person's click in between.

Architecture

4 Download and modify with IBM Bob

Download the source code and specifications for this application to set up and run it locally. Once downloaded, open the code in IBM Bob to modify and adapt it to your own use case.

Source Code

IBM Bob inside Slack — Seller Demo Script

1. The case arrives

Key message: With Bob, a case is picked up the moment it arrives — not days later when the admin backlog clears.

Open the newest case channel in Slack.
Point at the alert: case number, subject, and the line saying Bob is reading the case and drafting a proposal.
Narrate: A sales manager filed this — when a deal closes, the Success Plan is created manually days later, handoffs slip, onboarding starts late and renewals suffer.

2. Read the proposal

Key message: Bob responds like an experienced Salesforce architect because its skills come from IBM’s Salesforce practice. Swap in your own skills and Bob responds in your domain.

Walk through Bob’s four parts: the problem, the fix, why it matters, and the skills it applied.

3. Push back first

Key message: The team can challenge Bob at any point — the answer is specific and contextual, not boilerplate.

Type: @bob explain the proposed solution before building it.
Bob answers from the case and its own proposal; nothing changes in the org.

4. Approve solution

Key message: Every action Bob takes is attributed and traceable. Anyone picking up this case later sees what was decided and why — without opening Slack.

Click Approve solution.
Bob writes a use-case summary and the service posts it on the case in Salesforce.
Open the link to the case record to show the summary.

5. Ask Bob to implement

Key message: The change is governed — deploying to the org requires a human approval. The same pattern works for any system with an API or MCP server.

Type: @bob implement.
The service replies that deploying a change needs approval and shows Approve deploy and Reject.
Explain: the change is a new field on the Success Plan object and a flow that creates a Success Plan whenever an opportunity closes as won.

6. Approve deploy

Key message: Everything is visible and traceable — like any other deployment.

Click Approve deploy.
The Deployed message lists each component live in the org with direct links into Salesforce Setup, Bob’s test steps, and a quick-test link.

7. Prove it in Salesforce

Key message: Exactly what Bob proposed is now live in the org.

Open the Meridian Renewal deal, set Stage to Closed Won, and save.
Within seconds the flow creates the Success Plan, fills it with the opportunity details, and notifies the account owner.
Back in Slack, point at the It worked message with the link to the new Success Plan.

8. Close

Key message: Three approvals, zero code typed, one real change in a live Salesforce org — with every action attributed and traceable. The team defines the skills, approvals, and connected systems.