DEV Community: Dipojjal Chakrabarti

Your Data Quality Will Make or Break Agentforce

Dipojjal Chakrabarti — Tue, 07 Apr 2026 23:05:13 +0000

Your Data Quality Will Make or Break Agentforce

Everyone's talking about Agentforce right now. And honestly, they should be - it's the most exciting thing Salesforce has shipped in years. But here's what I keep seeing in the field: teams rush to spin up AI agents, skip the boring data work, and then wonder why their shiny new agents are giving customers wrong answers.

I've watched this play out at multiple orgs over the past year, and the pattern is always the same. The biggest variable in a successful Agentforce deployment isn't your agent configuration or your prompt engineering. It's your data.

The Uncomfortable Truth About Your CRM Data

Let's be real for a second. Most Salesforce orgs have years of accumulated data debt. Duplicate contacts, outdated account info, inconsistent formatting, free-text fields that should have been picklists from day one. We all know it's there. We've just been living with it because, until now, the consequences were manageable.

AI changes that equation completely.

Data Cloud now stores over 22 trillion data points and crossed the $900 million ARR mark this year. Nearly 60% of Salesforce's top deals include both Data Cloud and AI capabilities bundled together. That tells you something - the platform is pushing hard toward a world where your data isn't just sitting in records, it's actively fueling intelligent agents that talk to your customers.

When a sales rep looks at a duplicate record, they can usually figure out which one is current. An AI agent can't make that judgment call. It'll pull from whichever record it hits first, and if that record has a two-year-old phone number and the wrong job title, that's what your customer gets. Not a great look.

What "Data Readiness" Actually Means

I hear "data readiness" thrown around a lot in Agentforce conversations, but it often stays vague. So let me break down what it actually looks like in practice.

Start with deduplication. This is the single highest-impact thing you can do before turning on any AI agent. Define what a duplicate means for each object - a duplicate lead might have different criteria than a duplicate contact. Use Salesforce's built-in matching rules and duplicate rules as your first line of defense. They'll flag potential dupes before reps can even save a record.

For orgs that have been running for years without this in place, you're probably sitting on thousands of duplicates right now. Tools like DemandTools, Insycle, or DataGroomr can help you tackle the backlog at scale. But don't just merge and move on. Set up duplicate reports on a dashboard so you can catch new ones as they creep in.

Standardize your fields. "Acme Inc." and "ACME" and "Acme, Inc" are three records that should be one. Matching rules depend on consistent formatting to work. Create naming conventions, enforce them with validation rules, swap free-text fields for restricted picklists wherever you can, and use Flows to auto-format data on entry.

Fill in the gaps. AI agents need context to be useful. If half your contact records are missing email addresses or your accounts don't have industry classifications, your agents will be flying blind. Run a data completeness audit and prioritize filling in the fields that your agents will actually reference.

If you're looking for clear definitions of Salesforce-specific terms as you work through this process, salesforcedictionary.com is a solid reference to keep bookmarked.

Building a Data Governance Rhythm

One-time cleanups don't stick. I've seen orgs do a massive data cleansing project, celebrate, and then watch the data decay right back to where it started within six months. You need a rhythm.

Here's what works for the teams I've seen succeed with Agentforce:

Daily: Monitor your agent health dashboards. Salesforce's Agentforce Testing Center lets you track how agents are performing and catch issues early. If response quality drops, check whether a data issue is the root cause before you start tweaking prompts.

Weekly: Run your duplicate reports. Review any records flagged by validation rules that were overridden. Spot-check a sample of recently created records to make sure data entry standards are holding.

Monthly: Do a deeper dive. Look at field completion rates across key objects. Check that your matching rules are still catching what they should. Review any new custom fields that got added and make sure they have proper validation.

Quarterly: Step back and evaluate. Are your agents performing better than last quarter? Where are the gaps? Are there new use cases that need additional data prep? This is also a good time to review your data governance policies with stakeholders from security, legal, and business teams.

The admin community over at salesforcedictionary.com has been discussing these governance patterns quite a bit lately, and the consensus is clear: the orgs that treat data quality as an ongoing practice rather than a project are the ones seeing real ROI from Agentforce.

Practical Steps to Get Started This Week

If you're planning an Agentforce rollout (or you've already started and things aren't going great), here's what I'd do right now:

Pick one use case. Don't try to boil the ocean. Choose a single agent use case - maybe case deflection in Service Cloud or lead qualification in Sales Cloud. Companies that start focused see results in 60 to 90 days, including faster response times and lower costs.

Audit the data that use case touches. If your first agent handles support cases, go look at your Case, Contact, and Knowledge Article objects. How many duplicate contacts do you have? Are your Knowledge Articles up to date? Is the data your agent needs actually populated?

Set guardrails before you go live. Configure Max Turn limits in Agent Builder - 10 back-and-forth turns per session is a good starting point. Use the test mode to run through typical scenarios, edge cases, and restricted scenarios. Refine your prompts based on what you find.

Document everything. Maintain an agent inventory that tracks what each agent does, who owns it, and what data it accesses. Version control your agent configurations. This sounds like overkill now, but when you have five agents running across different clouds, you'll be glad you started organized.

Get your team aligned. Admins need a seat at the table with security, legal, and business leadership. This isn't just a tech project - it's a business transformation. The teams that invest early in skills, architecture, and governance are building a lasting competitive advantage.

The Bottom Line

Agentforce is genuinely powerful. Autonomous AI agents performing mission-critical tasks across Sales Cloud and Service Cloud, triaging cases, writing outreach, analyzing opportunities, recommending next steps in real time - that's not a future promise anymore, it's happening right now.

But the technology is only as good as what you feed it. Organizations that try to deploy AI agents on fragmented, messy data consistently see poor response quality and low user satisfaction. The ones who do the unglamorous work of cleaning, standardizing, and governing their data first? They're the ones actually getting value from this.

So before you get too deep into agent configuration and prompt engineering, take an honest look at your data. It might not be the most exciting work, but it's the work that actually matters.

What's your experience been? Have you hit data quality walls with Agentforce, or found good strategies for getting your org ready? Drop a comment - I'd love to hear what's working (and what isn't) for other teams.

For more Salesforce terminology and concepts explained in plain language, check out salesforcedictionary.com.

Slack's New AI Slackbot: What Salesforce Pros Need to Know

Dipojjal Chakrabarti — Tue, 07 Apr 2026 14:39:32 +0000

Slack's New AI Slackbot: What Salesforce Pros Need to Know

If you've been sleeping on the latest Slack updates, it's time to wake up. Salesforce just dropped 30 new AI features for Slackbot, and this isn't your typical "we added a chatbot" kind of update. They've turned Slackbot into a full-blown agentic work assistant that can transcribe your meetings, update your CRM records, and even follow you around your desktop offering help. Yeah, it's a lot.

I've spent the past week poking around these new capabilities, and honestly? Some of them are going to change how Salesforce teams work on a daily basis. Let me walk you through what matters and what you should actually care about.

Slackbot Is Now an AI Agent, Not Just a Bot

The old Slackbot was basically a notification machine with some quirky auto-responses. The new version runs on Anthropic's Claude and functions as what Salesforce calls "your personal agent for work." That's not just marketing fluff - it actually does things on your behalf.

The biggest shift is that Slackbot now operates as an MCP (Model Context Protocol) client. In plain English, that means it can connect to over 6,000 applications, including Agentforce, Google Workspace, Microsoft 365, Notion, Workday, and ServiceNow. When you ask it to do something, it figures out which tool or agent is best suited for the job and routes the work automatically.

For Salesforce admins and developers who've been building with Agentforce, this is huge. Your custom agents are now accessible right from Slack. No more switching between tabs or training users on yet another interface. If you're not sure what MCP means in the Salesforce context, salesforcedictionary.com has a solid breakdown of newer Salesforce terms like this.

Reusable AI Skills Are the Real Game-Changer

Here's the feature that got me most excited: reusable AI skills. You can define a specific task once - like "summarize this campaign brief" or "create a budget for this event" - and save it as a named skill. Slackbot then recognizes when you're attempting that task and executes it automatically.

Think about what this means for your team. Instead of writing up the same status report format every Friday, you build a skill once. Instead of manually pulling together deal summaries before a pipeline review, you tell Slackbot to do it. The skill persists and works across different contexts.

This is particularly interesting for Salesforce consultants who work across multiple orgs. You could build a library of reusable skills that standardize how you handle common tasks, whether that's data validation, user onboarding checklists, or report generation.

Companies can also customize the default skills or create entirely custom ones. I can see Salesforce admins becoming "skill builders" for their organizations - yet another way to add value without writing a single line of Apex.

Meeting Intelligence That Actually Works

We've all been in that meeting where someone asks "wait, what did we decide?" fifteen minutes after the decision was made. Slackbot's new meeting intelligence tackles this head-on.

It listens to calls across Zoom, Google Meet, and Slack Huddles through desktop audio. But it goes beyond basic transcription. It identifies decisions made during the call, assigns action items to specific participants, and delivers structured summaries automatically when the meeting ends. If you zoned out for five minutes (no judgment), you can ask Slackbot to recap what you missed, including any action items assigned to you.

For Sales Cloud users, this is especially valuable. Imagine every customer call getting automatically summarized with next steps, and those next steps flowing right into your Salesforce opportunity record. That's the kind of workflow that used to require expensive third-party tools and a bunch of integration work.

The Desktop Agent - Powerful but Worth Watching

This is the feature that's getting the most attention, and for good reason. Slackbot can now operate outside of Slack itself, monitoring your desktop activity and proactively offering suggestions based on what you're working on.

Salesforce says it draws on "your deals, your conversations, your calendar, and your habits" to surface relevant help. Working on a proposal? It might pull in relevant case studies. Prepping for a call? It could surface the latest account activity from Salesforce.

Now, I'll be upfront - this is also the feature with the biggest privacy implications. Salesforce has built in adjustable permission controls, so you can dial back what the agent sees and does. If you're an admin, you'll want to get ahead of this with clear policies before your users start enabling it. Check out resources like salesforcedictionary.com for updated Salesforce terminology and feature definitions as these roll out.

Native CRM Built Into Slack

For smaller teams or organizations that don't need the full Salesforce platform, there's now a lightweight CRM built directly into Slack. Slackbot reads your channels, identifies deal mentions and new contacts, and updates records automatically. It logs follow-ups, manages contracts, and essentially eliminates the need to jump into Salesforce for basic CRM tasks.

This is clearly aimed at competing with Microsoft's integrated Copilot strategy across the 365 ecosystem. Slack's argument is that a communication-first interface with broad enterprise integration makes a better home for AI agents than document-centric approaches. It's a solid argument, and for teams already living in Slack, removing that context switch could be a real productivity boost.

Who Gets Access and When

Here's the availability breakdown as of right now:

Business+ and Enterprise+ subscribers have access to all features at no additional cost. Free and Pro plan users will get a limited version starting this month (April 2026). And starting summer 2026, Slack will be automatically bundled with every new Salesforce customer account.

That bundling move is significant. It signals that Salesforce sees Slack as THE interface layer for its entire ecosystem, not just a communication tool bolted on the side.

All of these AI capabilities run on Anthropic's Claude, and Salesforce specifically chose Anthropic because it was "the only AI provider meeting FedRAMP Moderate certification requirements" when they designed the system. That matters a lot for teams in regulated industries like healthcare, finance, and government.

What This Means for Your Salesforce Career

If you're a Salesforce professional, these changes point in a clear direction: the people who thrive will be the ones who understand how to configure, customize, and optimize AI agents within the Salesforce ecosystem. Building Agentforce skills, understanding MCP integrations, and knowing how to design effective AI workflows are becoming core competencies.

My advice? Start experimenting now. If your org is on Business+ or Enterprise+, you already have access. Build a few reusable skills, test the meeting intelligence with your team, and figure out how Agentforce agents can be surfaced through Slack for your specific use cases. The Salesforce professionals who get hands-on with this stuff early will have a serious edge. And if you need to brush up on Salesforce terminology as the platform evolves, salesforcedictionary.com is a handy reference.

What features are you most excited about? Have you already started using the new Slackbot? Drop your thoughts in the comments - I'd love to hear what's working (or not) for your team.

Agentforce Voice: Why Your IVR Is Already Obsolete

Dipojjal Chakrabarti — Mon, 06 Apr 2026 23:05:10 +0000

Agentforce Voice: Why Your IVR Is Already Obsolete

Remember the last time you called a company and had to press 1, then 3, then 0, then pound, just to talk to someone who asked you to repeat everything? Yeah, that experience is finally dying - and Salesforce's Agentforce Voice is holding the pillow.

I've been working with Salesforce contact center solutions for a while now, and I'll be honest: when Agentforce Voice launched in late 2025, I was skeptical. Another AI phone bot? We've all dealt with terrible ones. But after spending real time with it in 2026, I'm convinced this is fundamentally different from anything we've seen before. Here's why it matters and what you need to know to get started.

What Agentforce Voice Actually Does (And Why It's Different)

Let's get the basics out of the way. Agentforce Voice is Salesforce's AI-powered voice agent that replaces traditional IVR menu trees with actual conversational AI. When a customer calls in, here's what happens under the hood:

The customer's speech gets converted to text using a speech-to-text model
A latency-optimized reasoning engine called the Flash Planner figures out intent and context
It crafts a response and converts it back to speech
The whole thing happens fast enough that it feels like a normal conversation

But the real difference isn't the speech recognition - plenty of tools do that. It's the CRM integration. Agentforce Voice sits directly on top of your Salesforce data. It knows who's calling, what their recent cases look like, what products they own, and what their account history says. Traditional IVR systems? They're basically phone trees bolted onto a telephony platform with maybe a thin data connection to your CRM if you're lucky.

If you're new to the terminology around Salesforce AI features, salesforcedictionary.com has solid definitions that can help you get up to speed quickly.

Setting It Up Is Simpler Than You'd Expect

I was pleasantly surprised by the setup process. You don't need to be a developer to get a basic voice agent running. Here's the high-level flow:

First, you need Service Cloud Voice enabled - this is the bridge between your phone system and Salesforce. Head to Setup, search for "Voice," and open Partner Telephony Setup. Agentforce Voice works with Amazon Connect, Five9, Vonage, NiCE, and standard SIP trunks, so you can probably keep your existing telephony provider.

Next, you'll create your voice agent connection. Open your Service Agent, click Connections, hit New, and select Telephony as the connection type. Then you set up a phone number through Unified Number Management - this becomes the actual number customers dial.

The last piece is creating a Voice Channel where you wire up the phone number, routing flow, and your Agentforce Voice agent together.

The whole thing can be piloted in 8-12 weeks for most organizations. That's not marketing fluff either - I've seen teams with decent Salesforce maturity get a proof of concept running in about six weeks. The complexity scales with your use cases and compliance requirements, obviously.

One important note: as of early 2026, Agentforce Voice is only available in the United States and Canada. If you're running a global operation, you'll need to plan around that limitation for now.

Where It Really Shines: Financial Services

While Agentforce Voice works across industries, financial services is where I've seen the most impressive results. Salesforce released Agentforce Voice for Financial Services specifically, and the use cases are compelling:

Banking operations get a huge lift. Balance inquiries, card activations, lost card reports - these are the bread-and-butter calls that eat up agent time. Agentforce Voice handles them instantly. It can even proactively alert customers about suspicious transactions during the call. During payment due dates or outage periods when call volume spikes, having AI handle the routine stuff means your human agents aren't drowning.

Insurance is another natural fit. Automating First Notice of Loss (FNOL) calls with empathetic, guided voice flows is a big deal. The AI handles policy renewals and claims tracking questions without human intervention, and multilingual support means you're covering more customer segments without hiring specialized agents.

Wealth management firms are using it to prep clients before meetings - summarizing portfolio performance and key updates via voice - and offering voice-driven scheduling. The idea is that advisors spend time on relationship building instead of returning calls about account balances.

Some organizations in travel and hospitality are seeing 40-60% containment rates, meaning the voice agent resolves the request without ever needing a human. For financial services, the numbers vary depending on complexity, but even 25-30% containment on routine calls represents massive savings.

For anyone brushing up on Salesforce Financial Services Cloud concepts, salesforcedictionary.com is a handy reference for understanding how these features map to the broader ecosystem.

The Escalation Problem (And How It's Solved)

Here's the thing that always worried me about AI phone agents: what happens when the AI can't help? We've all been stuck in loops with chatbots that refuse to transfer you to a human. Agentforce Voice handles this with what Salesforce calls intelligent escalation.

When a conversation goes beyond the AI's scope - or when it detects emotional distress in the caller's voice - the call gets seamlessly transferred to a human agent. And here's the critical part: the human agent gets the full conversation history and customer context. No "can you please explain your issue again from the beginning."

This matters more than people realize. The biggest complaint about AI customer service isn't that the AI is bad at answering questions. It's that the handoff to a human is terrible. Agentforce Voice keeping full context through the transition is what makes the difference between "this AI is helpful" and "this AI is just another wall between me and a real person."

For compliance-heavy industries, the system also maintains full audit trails of all voice interactions. You can embed firm-level disclosures, scripts, and identity verification steps directly into the conversational flow. That's not optional in financial services - it's table stakes.

Should You Actually Do This?

Look, not every org needs Agentforce Voice right now. If your call volume is low and your team handles it fine, don't fix what isn't broken. But if you're dealing with any of these situations, it's worth a serious look:

High call volumes with a significant percentage of routine inquiries
Long hold times that are hurting customer satisfaction scores
Agent burnout from repetitive calls
Scaling challenges where hiring more agents isn't feasible
Customer expectations for 24/7 availability that you can't currently meet

The Spring '26 release made things even more interesting with the new Agentforce Contact Center unification, which eliminates the traditional seam between CRM and telephony data. Historically, voice was the most disconnected part of contact center stacks - spoken conversations, arguably the richest source of customer intelligence, were largely wasted. That's changing.

My honest advice? Start small. Pick one or two high-volume, low-complexity call types and build a voice agent for those. Measure containment rates, customer satisfaction, and average handle time. Then expand. Trying to boil the ocean on day one is how these projects fail.

If you're still getting familiar with terms like "containment rate" or "Flash Planner" in the Salesforce context, check out salesforcedictionary.com - it's a good place to build your vocabulary before jumping into implementation.

Wrapping Up

Agentforce Voice isn't perfect. The regional limitations are real, the setup requires solid Service Cloud foundations, and the AI will still stumble on edge cases. But compared to where we were even a year ago with rigid IVR trees and disconnected phone systems, this is a massive step forward.

The contact center is the last frontier of CRM that hasn't been truly modernized by AI. Agentforce Voice is Salesforce's big bet on changing that, and from what I've seen so far, it's a bet worth paying attention to.

Have you tried Agentforce Voice yet? I'd love to hear about your experience in the comments - especially if you've hit limitations I haven't covered here.

Slack's New AI Slackbot: 8 Features Salesforce Admins Need to Know

Dipojjal Chakrabarti — Mon, 06 Apr 2026 14:39:55 +0000

Slack's New AI Slackbot: 8 Features Salesforce Admins Need to Know

Remember when Slackbot was just that thing that reminded you about lunch orders and sent you automated channel welcome messages? Those days are officially over.

Salesforce dropped 30 new AI-powered features for Slackbot at the end of March 2026, and honestly, some of these changes are going to reshape how entire teams work inside the Salesforce ecosystem. I've been digging through the announcements, testing what's available so far, and talking to other admins about what this means for us - and there's a lot to unpack here.

If you're a Salesforce admin or developer who uses Slack (so, basically all of us), here's what you actually need to know.

Slackbot Is Now an Agentforce-Connected AI Agent

The biggest shift isn't any single feature - it's the architecture underneath. Slackbot now works as a Model Context Protocol (MCP) client. If that term's new to you, check out the Salesforce Dictionary for a quick breakdown of MCP and other Agentforce terminology.

What this means in practice: Slackbot can now connect directly to Agentforce and route tasks to specialized AI agents without you ever leaving the Slack window. Need to update a case? Ask Slackbot. Want to pull a pipeline report? Slackbot sends that request to the right Agentforce agent and brings the answer back into your conversation.

Parker Harris, Salesforce's CTO, put it this way: "We see it as the future interface for work. Slack is where you can get the work done."

That's not just marketing talk. When your messaging platform can orchestrate AI agents across your entire Customer 360 setup, the way you interact with Salesforce data fundamentally changes.

Reusable AI Skills Are a Big Deal for Admins

This is the feature I'm most excited about. Salesforce introduced "Reusable AI Skills" - basically, you can define a workflow once and then trigger it with a simple chat command.

Here's an example: say your team runs quarterly business reviews and you always need to pull together a budget from multiple sources. You create a skill called "create QBR budget," and Slackbot knows to pull data from specific Slack channels, connected apps, your calendar, and Salesforce reports to build the thing automatically.

There's a built-in library of default skills that come ready to use, plus you can build custom ones. For admins who've spent years building Flows and automation in Salesforce, this feels like a natural extension of that mindset - but now it lives right inside Slack where your users already spend their day.

Meeting Intelligence That Actually Works

I've tried a lot of meeting transcription tools over the years, and most of them generate massive walls of text that nobody reads. Slackbot's meeting intelligence takes a different approach.

It transcribes meetings from Zoom, Google Meet, and Slack Huddles, but the real value is in what happens after: it identifies decisions, pulls out action items, assigns them to specific people, and can even log those items back into Salesforce CRM. If someone missed a meeting, they can ask Slackbot for a personalized recap that only shows the action items assigned to them.

For Service Cloud teams running daily standups or Sales Cloud teams doing deal reviews, this eliminates the "what did we decide last Tuesday?" problem entirely.

The Desktop Agent Goes Beyond Slack

Here's where things get interesting - and maybe a little futuristic. Slackbot can now operate outside of the Slack application itself, following you across your desktop. It watches your calendar, monitors active deals, and tracks your communication patterns to offer proactive suggestions.

Before anyone panics about privacy: everything is user-initiated and optional. You control what it sees and when it chimes in. But the potential here is significant. Imagine finishing a customer call and having Slackbot automatically suggest updating the Opportunity stage, drafting a follow-up email, and scheduling the next meeting - all based on context it gathered from your calendar and the CRM record.

This is Agentforce's vision playing out in real time: AI that doesn't wait for you to remember what needs doing.

Native CRM Inside Slack for Smaller Teams

Not every Salesforce shop is an enterprise with a 50-seat license. Salesforce clearly knows this, because they've built a lightweight CRM directly into Slack. It reads your Slack conversations, identifies deals and contacts, and lets you manage a basic sales pipeline without ever opening the full Salesforce app.

The clever part? When your team outgrows it, you can graduate to full Salesforce CRM with your data already structured and ready to go. It's a smart onboarding ramp, and it means small teams no longer need to choose between "Slack for communication" and "Salesforce for CRM." They get both in one place.

If you're working with startups or SMB clients, this is worth bookmarking. The Salesforce Dictionary has a solid explainer on Sales Cloud vs. the new native CRM capabilities if you want to compare the two.

Slackbot Memory and Voice Commands

Two smaller but meaningful additions: Slackbot now has memory, and it accepts voice input.

The memory feature means Slackbot learns your preferences and communication patterns over time. If you always ask for pipeline reports filtered by your region on Monday mornings, it starts anticipating that. You keep full control and can delete stored preferences anytime.

Voice commands let you talk to Slackbot instead of typing. Combined with the "Deep Research" skill - which synthesizes information across multiple enterprise data sources into a single summary - you can essentially ask Slackbot a question out loud and get a researched answer pulled from your org's data. It's like having a junior analyst on speed dial.

Who Gets Access and When

Here's the rollout timeline as of April 2026:

Business+ and Enterprise+ subscribers already have the initial agentic capabilities. Free and Pro plan users are getting limited access this month. By summer 2026, all new Salesforce customers will receive a pre-configured Slack instance with AI features baked in. The full suite of 30+ features will roll out progressively through mid-to-late summer.

If you're on an older Slack plan, now might be the time to talk to your account executive about upgrading. The gap between what Business+ users get and what Free tier users get is going to be pretty noticeable.

What This Means for the Salesforce Ecosystem

The numbers tell a story: Agentforce hit $800M in annual recurring revenue, up 169% year-over-year. Salesforce is targeting $3B in Slack revenue for FY2027. Their own sales team logged over 21,000 agent interactions and saved roughly 44,000 hours in a year.

This isn't an experiment anymore. Salesforce is betting heavily that Slack becomes the primary interface for how people interact with AI agents, CRM data, and business workflows. For admins and developers, that means the skills we build in Slack are becoming just as important as the Flows and Apex we write in Salesforce itself.

If you haven't already started exploring Agentforce concepts, I'd recommend brushing up on the basics at salesforcedictionary.com and getting hands-on with the Slack AI features that are available today. The teams that figure this out early are going to have a serious advantage.

What feature are you most excited about? Drop a comment below - I'd love to hear how other admins are planning to use these new capabilities.

Slack Just Got 30 AI Features and It Changes Everything

Dipojjal Chakrabarti — Sun, 05 Apr 2026 23:06:08 +0000

Slack Just Got 30 AI Features and It Changes Everything

If you blinked last week, you might have missed one of the biggest Slack updates since Salesforce bought the platform back in 2021. On March 31st, Salesforce rolled out 30 new AI-powered features for Slack, and honestly? This isn't just a product update. It's a signal about where the entire Salesforce ecosystem is heading.

I've been watching Salesforce slowly weave AI into every corner of its platform for the past couple of years. But turning Slackbot into what CTO Parker Harris calls "the future interface for work" - that's a move that affects practically every admin, developer, and end user in the ecosystem.

Let's break down what actually matters here.

Reusable AI Skills Are the Real Story

The headline number is 30 features, but the one that caught my attention is "reusable AI skills." Think of these as little task templates you can teach Slackbot to perform, and then reuse them across different situations.

Say your team runs a lot of product launches. You could build a skill called "create launch budget" that tells Slackbot to pull data from specific Slack channels, check connected apps for historical spend, and generate a budget template. Once you've built that skill, anyone on the team can trigger it. No code required.

Salesforce ships a default library of these skills out of the box, but the real power is in customization. Companies can tweak the defaults or build entirely new ones that fit their workflows. If you're a Salesforce admin, this is the kind of thing that'll make your users actually love you - because you're giving them shortcuts that feel magical.

For anyone getting familiar with these new AI terms and concepts, salesforcedictionary.com is a solid reference for understanding how Salesforce-specific terminology maps to these newer AI capabilities.

Slackbot as an MCP Client - Why That's a Big Deal

Here's the technical bit that developers should pay attention to. Slackbot now functions as a Model Context Protocol (MCP) client. If you haven't been following MCP, it's basically a standard that lets AI agents connect to and coordinate with outside services and tools.

What this means in practice: Slackbot can now route work requests to Agentforce or any other agent or app in your enterprise. It figures out the most relevant and efficient path to get you answers without you needing to manually hop between systems.

Picture this. You're in a Slack channel and you ask, "What's the status of the Acme deal?" Instead of Slackbot just searching Slack messages, it can now reach out to your CRM data through Agentforce, pull the latest opportunity info, check recent email threads, and come back with a full picture. All within the Slack conversation.

This is what "agentic" actually means when it's not just marketing fluff. The agent decides which tools to use and connects the dots for you.

Meeting Transcription and Summaries That Actually Work

I know, I know - every platform promises AI meeting summaries these days. But Slack's implementation has a nice twist. Slackbot doesn't just transcribe your meetings and spit out a generic summary. It can identify action items and track who they're assigned to.

Missed the first 15 minutes of a standup? Ask Slackbot for a recap and it'll tell you specifically what action items were assigned to you. That's different from getting a wall of text you still have to read through.

This feature alone is going to save teams hours every week. If you've ever scrolled through a 45-minute meeting recording trying to find the one thing your manager asked you to do, you'll appreciate this.

Native CRM Inside Slack for Smaller Teams

This one's aimed at smaller businesses, and it's clever. Slackbot can now read your Slack channels, understand customer conversations happening there, and automatically update deals, contacts, and call notes in your CRM. It logs follow-ups and even reminds you of commitments you made.

For a 10-person sales team that lives in Slack, this means they might not need to constantly switch over to the full Salesforce UI just to keep their pipeline current. Slackbot handles the CRM busywork in the background while the team focuses on actually selling.

It's worth noting that this kind of conversational CRM is something a lot of startups have tried to build as standalone products. Salesforce just baked it right into the platform everyone's already using.

Desktop Monitoring - Helpful or Creepy?

Okay, this one's going to be controversial. Slackbot can now operate outside of Slack itself, monitoring desktop activities to provide contextual suggestions. It draws on data from deals, conversations, calendars, and your work habits.

The pitch is proactive assistance. Slackbot might notice you have a big client call in 30 minutes and automatically pull up relevant deal history, recent support tickets, and prep notes. That's useful.

But "desktop monitoring" is going to make some people uncomfortable, and rightfully so. I'd expect most organizations to be cautious about rolling this out and to have clear policies about what data is and isn't being tracked. If you're an admin evaluating this, make sure you understand the privacy controls before you flip the switch.

For a deeper look at how these AI-related Salesforce features work and what the terminology means, check out the glossary at salesforcedictionary.com - it's been helpful for keeping up with the flood of new terms.

What This Means for the Salesforce Ecosystem

Starting this summer, every new Salesforce customer will get Slack automatically provisioned with AI features turned on from day one. That's a massive distribution play. It means Slack isn't just a "nice to have" add-on anymore - it's becoming the default front door to the Salesforce platform.

For admins, this means you need to start thinking about Slack governance now if you haven't already. Who can create AI skills? What data sources can Slackbot access? How do you handle the MCP connections to external tools?

For developers, the MCP integration opens up a whole new surface area for building. If your custom apps or AppExchange products can speak MCP, they can now be part of the Slackbot workflow. That's a big opportunity.

And for end users, the message is simple: Slack is about to get a lot more useful. The days of it being "just a chat app" are officially over.

Rob Seaman, Slack's General Manager, summed it up pretty well: "Slackbot is the ultimate teammate." Whether that turns out to be true depends on execution, but the ambition is real.

Getting Ready

Most of these features will roll out over the coming months, so you've got time to prepare. Here's what I'd do right now:

Start by auditing your current Slack setup. Know which channels exist, who has access, and what integrations are already in place. Then identify two or three workflows that could benefit from reusable AI skills - think repetitive tasks that follow a predictable pattern. Finally, get familiar with MCP basics if you're on the developer side, because that's clearly the direction Salesforce is pushing.

If you want to stay sharp on all the Salesforce terms flying around - from Agentforce to Atlas Reasoning Engine to MCP - salesforcedictionary.com keeps a running glossary that's actually up to date.

This Slack update isn't just about productivity features. It's Salesforce planting a flag and saying, "This is where work happens now." And based on what I've seen so far, they might be right.

What do you think - are you excited about Slackbot becoming an AI-powered work hub, or does the desktop monitoring piece give you pause? Drop your thoughts in the comments.

Salesforce Agent Script: What It Is and Why You Should Care

Dipojjal Chakrabarti — Sun, 05 Apr 2026 14:41:15 +0000

Salesforce Agent Script: What It Is and Why You Should Care

If you've been following the Agentforce hype since Dreamforce, you've probably noticed something: building AI agents in Salesforce is getting easier with every release. But there's always been a tension between letting AI be creative and making sure it actually does what you need it to do. That's exactly the problem Agent Script is designed to solve.

Released as a beta in the Spring '26 release, Agent Script is a new scripting language that gives you precise control over how your Agentforce agents behave - without sacrificing the flexibility that makes AI useful in the first place. I've spent some time digging into it, and honestly, it's one of the most interesting things Salesforce has shipped for developers in a while.

What Exactly Is Agent Script?

Think of Agent Script as a middle ground between clicking through a UI builder and writing full-blown Apex code. It's a lightweight scripting language designed specifically for defining agent behavior. You write instructions that mix natural language with structured logic - things like if/else conditions, variable checks, and hand-off rules.

Here's why that matters. Before Agent Script, you had two options for controlling Agentforce agents. You could use the declarative builder (great for simple cases, but limiting when logic gets complex) or you could build custom actions in Apex (powerful, but overkill for many scenarios). Agent Script sits right in between. You get the predictability of code with the readability of plain English instructions.

The syntax lets you define conditional chaining and variable-based context control. So instead of hoping the AI interprets your topic description correctly, you can spell out exactly what should happen when a customer mentions billing vs. when they ask about a product return. It's deterministic where you need it to be and flexible everywhere else.

Why This Matters for Salesforce Teams

I've talked to a few admins and developers who were hesitant about Agentforce adoption, and the concern was almost always the same: "How do I make sure the agent doesn't go off-script?" That's a fair worry. When you're deploying AI that talks to customers or handles internal processes, unpredictable behavior isn't just annoying - it's a liability.

Agent Script addresses this head-on. You can define strict rules for sensitive interactions while leaving room for the AI to handle routine conversations naturally. Think of it like giving a new employee a detailed playbook for handling tricky situations but trusting them to handle everyday small talk on their own.

For teams that are still on the fence about Agentforce, this could be the feature that tips the scale. If you're exploring Salesforce terminology around Agentforce and AI agents, salesforcedictionary.com has some solid definitions that help break down the jargon.

How Agent Script Works With the New Canvas View

Here's where it gets really practical. Spring '26 also introduced the Agentforce Canvas View in beta - a visual drag-and-drop interface for building agent flows. And Agent Script is designed to work right alongside it.

The Canvas View lets you see the entire agent flow visually. You can connect topics, manage escalation paths, and understand how your agent moves through a conversation. Then you can drop into Agent Script to fine-tune specific decision points with precise logic.

It's a lot like how Flow Builder works with Apex invocable actions. You build the big picture visually, and when you need more control at a specific step, you write a script for it. The combination of Canvas View and Agent Script means you don't have to choose between visual building and code-level control - you get both.

Getting Started: What You Need to Know

Since Agent Script is currently in beta, there are a few things to keep in mind before you start experimenting:

You'll need Agentforce DX. This is the pro-code development experience that runs in VS Code and the Salesforce CLI. The Agent Script language server gives you syntax highlighting, error detection, and even live preview modes so you can test your scripts against actual CRM data. If you're already comfortable with VS Code for Salesforce development, the learning curve is minimal.

Start with Agent Grid for testing. Agent Grid is another Spring '26 beta feature - it's basically a spreadsheet-like testing environment where you can iterate on AI workflows quickly. Feed it different scenarios and see how your Agent Script logic handles each one. It's way faster than testing in a sandbox with live conversations.

Keep your scripts focused. Each script should handle a specific decision point or escalation path. Don't try to write one massive script that covers every possible scenario. Break your agent logic into modular pieces, just like you would with any good code architecture.

Mix instructions with rules. The beauty of Agent Script is that you can combine natural language guidance ("Be helpful and empathetic when the customer is frustrated") with hard-coded logic ("If the refund amount exceeds $500, always escalate to a supervisor"). Use each approach where it makes the most sense.

If you want to brush up on terms like "topics," "actions," and "escalation paths" in the Agentforce context, salesforcedictionary.com keeps an updated glossary that's worth bookmarking.

What This Means for the Salesforce Ecosystem

Agent Script signals something bigger about where Salesforce is headed. The platform is clearly betting that the future isn't just declarative or just code - it's a blend. We're seeing this pattern across the Spring '26 release: AI-powered flow drafts that generate flows from natural language descriptions, complex template expressions in LWC that eliminate boilerplate code, and now a scripting language that bridges natural language and deterministic logic.

For developers, this is great news. Your Apex and LWC skills aren't going anywhere, and now you have another tool in the toolkit that plays nicely with AI. For admins who've been nervous about the "developer-only" perception of Agentforce customization, Agent Script is approachable enough that you can start writing basic conditional logic without a computer science degree.

The broader trend here is what Salesforce calls the "Agentic Enterprise" - organizations where human expertise and AI agents work together. Agent Script is the kind of practical tooling that actually makes that vision achievable instead of just being a marketing slide.

Should You Try It Now?

Since it's still in beta, I wouldn't build production workflows on Agent Script just yet. But I'd absolutely recommend spinning up a scratch org or developer edition and experimenting. Here's a simple approach:

Pick one simple use case - maybe a lead qualification agent that routes hot leads to sales and sends cold leads into a nurture sequence. Build the basic agent with the Canvas View, then use Agent Script to define the qualification criteria with if/else logic. Test it in Agent Grid. You'll get a feel for the syntax and the development workflow in an afternoon.

The beta will likely evolve before going GA, so the specific syntax might change. But the concepts - mixing natural language with structured logic, modular script design, visual-plus-code workflows - those are here to stay.

If you're already invested in the Salesforce ecosystem, keeping up with features like Agent Script is essential. Resources like salesforcedictionary.com can help you stay current with the ever-growing vocabulary that comes with each release.

Wrapping Up

Agent Script is one of those features that doesn't make a flashy demo but solves a real problem. It gives teams the confidence to deploy AI agents knowing they'll behave predictably when it counts. Combined with Canvas View, Agent Grid, and the rest of the Spring '26 Agentforce updates, Salesforce is making it genuinely easier to build agents that work in the real world - not just in a demo environment.

I'm curious to hear from anyone who's already been testing the beta. What use cases are you building? Drop a comment below and let's compare notes.

Agent Script: Build Reliable Agentforce Agents

Dipojjal Chakrabarti — Sat, 04 Apr 2026 23:05:39 +0000

Agent Script changed how I build Agentforce agents. If you've been fighting with overloaded system prompts and unpredictable LLM behavior, this new scripting language is exactly what you need.

I spent years wrestling with prompt engineering to get AI agents to behave consistently. One day the agent follows the right steps, the next day it skips half of them. Sound familiar? Salesforce clearly heard the frustration, because Agent Script solves this problem in a way that actually makes sense for people who build on the platform.

Let me walk you through what Agent Script is, why it matters, and how to start using it in your own Agentforce projects.

What Exactly Is Agent Script?

Agent Script is a new scripting language built specifically for Agentforce Builder. It's not Apex, it's not JavaScript, and it's not just another prompt template. Think of it as a hybrid - it combines deterministic, code-like logic (conditionals, variables, transitions) with natural language instructions that get sent to the LLM.

The core idea is simple: you shouldn't have to rely on an AI model to "remember" your business rules. Instead, you write those rules as actual logic that executes predictably every single time. The AI still handles the conversational parts - understanding what a customer is saying, generating natural responses - but the workflow logic is locked down.

If you're not familiar with some of these Agentforce terms, salesforcedictionary.com is a solid place to brush up on Salesforce terminology before jumping in.

The Syntax Is Surprisingly Simple

Here's what makes Agent Script approachable: you don't need to be a hardcore developer to pick it up. The language uses a few key conventions that are easy to learn.

Arrow syntax (->) switches a block from declarative mode to procedural mode. This is where you write your step-by-step logic - conditionals, action calls, variable assignments.

Pipe syntax (|) marks text that gets sent to the LLM as part of the prompt. This is your natural language layer.

Variables come in two flavors. Mutable variables (@variables.name) can be read and written during the conversation - great for tracking things like case status or customer intent. Linked variables are read-only and pull values from external context like the current session.

Conditionals use straightforward if/else blocks. One thing to note: else if isn't supported yet, so you'll need to use separate if statements for multi-branch logic. Not ideal, but workable.

Template expressions use the {!expression} syntax inside pipe strings. At runtime, Agent Script swaps these out for actual values. If you've ever used merge fields in Salesforce formulas, this will feel natural.

Here's a quick mental model: the arrow blocks handle your "what to do" logic, and the pipe blocks handle your "what to say" instructions.

Why This Beats Prompt Engineering Alone

I've talked to dozens of admins and developers who tried building Agentforce agents using nothing but natural language prompts. The results were... inconsistent. You'd write a prompt like "always check the customer's account status before creating a case," and half the time the agent would skip that step entirely.

The problem is fundamental to how LLMs work. When you stuff too many rules into a system prompt, the model starts dropping things. It's not being lazy - it's just the nature of how attention mechanisms prioritize information. The more rules you add, the less reliable each individual rule becomes.

Agent Script fixes this by pulling your business logic OUT of the prompt layer entirely. Conditionals, transitions between topics, and action sequencing all happen deterministically. The LLM only handles what it's actually good at: understanding natural language and generating conversational responses.

The real-world numbers back this up. Datasite, a financial services company, saw their case deflection rate jump from the low 60s to an average of 82% after implementing Agent Script. Their customer satisfaction scores hit 4.8 out of 5. That's not a marginal improvement - that's a fundamentally different level of performance.

Getting Started: Practical Tips

If you want to start building with Agent Script, here's my recommended approach.

Start in Canvas Mode. Agentforce Builder gives you multiple views: Canvas, Script, and a conversational AI-guided mode. I'd suggest starting in Canvas Mode to sketch out your agent's structure - topics, actions, and the general flow. It's visual and intuitive. Once the skeleton looks right, switch to Script Mode to add your precise logic.

Keep your topics focused. Each topic should handle one clear area of responsibility. A "Check Order Status" topic shouldn't also be handling returns. When topics stay focused, your scripts stay clean, and debugging becomes way easier.

Use variables strategically. Don't just track everything - think about what information actually needs to persist across conversation turns. Remember, mutable variables should have default values, and linked variables are your friends for pulling in session context without extra API calls.

Test with edge cases. Empty values, unclear requests, extreme numbers - throw all of it at your agent. Agent Script makes the happy path reliable, but you still need to make sure your conditionals handle the weird stuff gracefully.

Treat scripts as modular components. Once you've built a solid script for one agent, you can copy and reuse blocks across other agents. Trim out what you don't need for each new use case. This approach lets you spin up new agents fast while keeping your logic consistent.

For a deeper look at Salesforce terminology around topics, actions, and the Atlas Reasoning Engine, check out the glossary at salesforcedictionary.com - it's been really helpful for keeping up with all the new Agentforce vocabulary.

What's Coming Next

Agent Script is still evolving. The current version doesn't support multiplication, division, or modulo operators - if you need complex math, you'll still want to call out to a Flow or Apex action. And the lack of else if means some conditional trees get a bit verbose.

But Salesforce is clearly investing heavily here. The Agent Script Recipes sample app on the Salesforce Developers site is a great resource for learning patterns, and the unofficial documentation at agentforce.guide fills in a lot of gaps. With Summer '26 sandbox previews expected around May 9th, there's likely even more coming.

The bigger picture is that Agent Script represents a shift in how Salesforce thinks about AI reliability. Instead of treating LLMs as magic black boxes, they're giving builders real tools to control agent behavior. That's a much healthier approach for enterprise use cases where consistency matters.

Time to Start Building

If you've been on the fence about Agentforce, Agent Script is the feature that should push you over. It addresses the single biggest complaint people had about AI agents: unpredictability. With a language that's simple enough for admins to learn but powerful enough for developers to build serious workflows, it hits a sweet spot that not many platforms have figured out yet.

My suggestion? Grab the Agent Script Recipes sample app, spin up a sandbox, and start experimenting. Even if you're not planning to deploy an agent tomorrow, understanding this scripting language now will put you ahead of the curve.

Drop a comment if you've already started building with Agent Script - I'd love to hear what use cases you're tackling and what patterns are working well for you.

Want to stay current with Salesforce terminology and features? Visit salesforcedictionary.com for clear definitions of the latest platform concepts.

Agentforce Builder: A Practical Guide for Salesforce Admins

Dipojjal Chakrabarti — Sat, 04 Apr 2026 14:39:21 +0000

Agentforce Builder: A Practical Guide for Salesforce Admins

You've probably heard the buzz around Agentforce by now. Salesforce has been pushing AI agents hard, and with the Spring '26 release, they shipped something that actually changes how we build them. The new Agentforce Builder isn't just a facelift - it's a completely rethought experience that moves agent creation out of Setup and into a dedicated workspace where admins, developers, and business users can all collaborate.

I've been spending time with the new builder over the past few weeks, and here's what you need to know to get started.

What Changed with the New Agentforce Builder?

The original agent building experience lived inside Setup, which meant only admins with the right permissions could touch it. That's fine for initial configuration, but it created a bottleneck when business teams wanted to iterate on agent behavior.

The new Agentforce Builder lives in Agentforce Studio, a standalone app that's accessible to a wider group of users. It unifies drafting, testing, and deployment into one conversational workspace. Instead of bouncing between Setup pages, testing in a separate window, and then going back to tweak things, you do it all in one place.

The builder gives you three different ways to work with your agent, depending on your comfort level. There's a Canvas View that breaks the agent's logic into visual blocks you can drag around and connect. There's a document-style editor with autocomplete if you prefer writing instructions more naturally. And for developers, there's a full script view where you can write Agent Script directly.

That flexibility is the real win here. Your admin can start building in Canvas View, and your developer can drop into script view to fine-tune the logic - all on the same agent, in the same workspace.

Agent Script: Where Predictability Meets AI

If I had to pick the single most important feature in Agentforce 360, it's Agent Script. Before this, you were mostly relying on the AI's reasoning engine to figure out what to do based on your topic descriptions and action configurations. That works for simple use cases, but once you need precise control - like making sure an agent always verifies a customer's identity before pulling up account details - you need something more deterministic.

Agent Script is a human-readable scripting language that lets you define exactly how your agent should behave. You can set up conditional logic, specify which tools to use and when, and create guardrails that the AI can't skip over. It's the best of both worlds: the creativity and natural language understanding of LLMs combined with the predictability of structured business logic.

Here's what makes it click for me. In practice, you might have a support agent that uses AI reasoning to understand what a customer is asking about, but then follows a strict Agent Script to handle the actual resolution steps. The conversational part stays flexible; the business process part stays locked down. Salesforce calls this "hybrid reasoning," and honestly, it solves a problem that's been nagging at everyone building production agents.

If you're not familiar with the terminology around agents and topics, salesforcedictionary.com is a solid reference for getting up to speed on Agentforce-specific terms.

Intelligent Context and Data Libraries

One of the biggest complaints about early Agentforce implementations was that agents felt disconnected from the broader business context. They could work with Salesforce records, sure, but they struggled with unstructured data like PDFs, internal documentation, or complex tables.

Intelligent Context fixes this. Powered by Data 360, it automatically extracts and structures information from your unstructured content - PDFs, images, flowcharts, you name it - and makes it available to your agents through Data Libraries.

When you're building an agent in the new builder, you can assign specific Data Libraries to it. So instead of the agent only knowing what's in your CRM records, it can also reference your knowledge base articles, product documentation, policy documents, and more. This makes a huge difference for service agents that need to answer questions about things that don't live neatly in a Salesforce object.

The setup isn't complicated either. You create a Data Library, point it at your content sources, and the system indexes everything with AI. Then you just assign the library to your agent's topics. I've found this to be one of the fastest ways to make an agent actually useful rather than just a demo.

Testing and Previewing Your Agents

Here's where the new builder really pulls ahead of the old experience. Agent Previews let you simulate conversations with mock data so you're not testing against your live org. You can set specific conditions, define the customer scenario, and watch exactly how the agent reasons through the problem.

The preview panel shows you the agent's reasoning chain step by step. You can see which topics it matched, which actions it chose, and why. When something goes wrong, you don't have to guess - the reasoning trace tells you exactly where the logic broke down.

There's also built-in validation that catches configuration issues before you deploy. Missing actions, incomplete connections, potential runtime errors - the builder flags them all. It's the kind of quality-of-life improvement that saves you from those frustrating "it worked in my head" moments.

For anyone building their first agent, I'd recommend checking out the Trailhead modules on Agentforce Builder basics. And if you run into Salesforce terms you're not sure about while going through the material, salesforcedictionary.com has clear definitions for most of the platform vocabulary.

Getting Started: Practical Tips

If you're ready to build your first agent with the new builder (or migrate an existing one), here are some things I've learned that might save you time.

Start with Canvas View, even if you're a developer. The visual representation helps you think through the conversation flow before you start writing script. It's easy to over-engineer things when you jump straight into code.

Keep your topics focused. Each topic should handle one clear intent. If you find yourself cramming too many actions into a single topic, break it up. The agent's reasoning engine performs better when topics are specific.

Use Agent Script for your critical paths. Not everything needs to be scripted - let the AI handle the conversational parts naturally. But for anything involving data updates, financial transactions, or compliance-sensitive processes, script it. You'll sleep better.

Test with edge cases early. The preview feature makes this easy, so there's no excuse to skip it. Think about what happens when a customer asks something your agent wasn't designed for. Does it escalate gracefully, or does it hallucinate an answer?

And finally, assign Data Libraries from day one. Even if your agent is simple, giving it access to your knowledge base content makes a noticeable difference in answer quality.

What This Means for Salesforce Pros

The new Agentforce Builder is a signal of where Salesforce is heading. Agents aren't a side feature anymore - they're becoming central to how the platform works. The job market is already reflecting this, with Agentforce skills showing up in more and more Salesforce job postings.

Whether you're an admin looking to expand your skill set or a developer exploring AI capabilities, now is a good time to start building. The tools are mature enough to produce real results, and the learning curve with the new builder is genuinely lower than it was six months ago.

If you're new to the Agentforce ecosystem, start with the basics on salesforcedictionary.com and the Trailhead quick-start projects. Then fire up Agentforce Studio and start experimenting. The best way to learn this stuff is by building.

What are you building with Agentforce? Drop a comment - I'd love to hear about your use cases and any gotchas you've run into.

Agentforce Builder in Spring '26: What Developers Actually Need to Know

Dipojjal Chakrabarti — Fri, 03 Apr 2026 23:05:44 +0000

Agentforce Builder in Spring '26: What Developers Actually Need to Know

If you've been keeping up with Salesforce releases, you know the Spring '26 drop is one of the meatiest we've gotten in a while. And at the center of it all? The completely redesigned Agentforce Builder. I've been poking around it since the beta dropped, and honestly, it changes how we think about building AI agents on the platform.

But there's a lot of noise out there, so let me cut through it and focus on what actually matters for folks building on Salesforce day to day.

The New Agentforce Builder Isn't Just a UI Refresh

Let's get this out of the way first - this isn't Salesforce slapping a coat of paint on the old agent setup screens. The new Agentforce Builder is a full rethink of how you create, test, and deploy AI agents.

The builder now gives you three distinct ways to work. There's a conversational mode where you describe what you want in plain English and let AI help scaffold it out. Then there's a Canvas view - think of it like a visual flow builder specifically for agent logic. And for the developers in the room, there's Script view, which introduces a brand new language called Agent Script.

Agent Script is what really caught my attention. It sits in this sweet spot between natural language prompts and traditional Apex code. You get conditional logic, variable management, and deterministic control - but written in a way that's more readable than pure code. If you've ever wished you could combine the flexibility of prompt engineering with the reliability of programmatic logic, this is that.

You can also use Agentforce DX to build agents directly in VS Code, with both simulated and live preview modes. That's a big deal for teams that have mature CI/CD pipelines and don't want to context-switch into the browser for everything.

Federated Data Grounding Changes the Game

Here's something that doesn't get enough attention: Federated Data Grounding with External Objects.

Previously, if you wanted your agents to be smart about data from outside Salesforce - your ERP, warehouse management system, accounting platform - you had two bad options. You could replicate that data into Salesforce (expensive, stale), or you could build custom integrations that the agent would call (complex, fragile).

Spring '26 introduces a third path. External Objects now connect directly to Prompt Builder through retrieval-augmented generation (RAG). Your agents query live data from external systems in real time, without duplicating anything.

Why does this matter? Because AI agents are only as good as the data they can access. If your agent is answering customer questions based on data that's six hours old, you're going to have problems. With federated data grounding, the agent always works with current information. And because there's no data replication, you're saving on storage costs too.

For anyone building agents that need to pull from multiple systems - which is basically everyone in an enterprise setting - this feature alone justifies paying close attention to the Spring '26 release. If you need a refresher on how External Objects work in Salesforce, salesforcedictionary.com has solid breakdowns of the terminology.

LWC and Apex Updates You Shouldn't Sleep On

The Agentforce stuff is flashy, but there are some serious quality-of-life improvements for developers working with Lightning Web Components and Apex.

Dynamic Event Listeners in LWC - The new lwc:on directive lets you attach event listeners programmatically. Instead of hardcoding handlers in your HTML template, you can swap behaviors entirely in JavaScript. It sounds small, but it makes components way more reusable and flexible.

GraphQL Mutations - LWCs can now do create, update, and delete operations through the executeMutation method. Until now, GraphQL in LWC was read-only, which limited its usefulness. This opens up a lot of possibilities for building more sophisticated client-side experiences.

TypeScript Support - Full TypeScript is finally here for base components through the @salesforce/lightning-types package. You get IntelliSense, compile-time error detection, and all the safety nets TypeScript developers expect. If your team has been holding off on TypeScript adoption, now's the time.

On the Apex side, Apex Cursors are now generally available. They let you process massive SOQL result sets in manageable chunks with bidirectional traversal. They serialize nicely for Queueable jobs and work well with LWC pagination patterns. For anyone dealing with large data volumes, this is a lifesaver.

There's also a new Named Query API that's hit GA. You can define custom SOQL queries and expose them as scalable REST API actions. It's a much cleaner pattern than building custom REST endpoints for every data access need.

Security Changes That Could Break Your Stuff

I want to flag two security changes because they could catch teams off guard if you're not prepared.

First, session ID transmission in outbound messages is now disabled as of February 2026. If you have integrations that relied on passing session IDs through outbound messages, they're already broken or about to be. You need to migrate those to use named credentials or OAuth flows instead.

Second, new connected app creation is disabled by default. Salesforce wants everyone moving to External Client Apps. If your team still spins up connected apps as part of your integration workflow, you'll need to adjust your process. The Conversational Identity Governance feature in Agentforce for Setup can actually help here - it lets you manage OAuth and External Client App configuration through natural language, which takes some of the pain out of the migration.

For a clear explanation of concepts like OAuth flows and named credentials in the Salesforce context, check out salesforcedictionary.com - it's a handy reference when you're sorting through authentication terminology.

Observability Gets a Real Upgrade

One thing that's always been tricky with Salesforce automation is monitoring it at scale. You could check debug logs, but that's a manual process with size limits. You could build custom logging, but that eats into your org's storage and governor limits.

Spring '26 introduces High-Fidelity Observability through Data 360 Logging. Flow execution data now logs directly to Data 360, capturing completion times, status codes, and error details in a dedicated Flow Run Data Model Object. This offloads monitoring from your transactional systems to an analytical platform designed to handle it.

For teams running mission-critical automations - especially those powered by Agentforce - this is a serious improvement. You can finally monitor at scale without worrying about degrading your org's performance.

There's also a new enableDebugLogsDuringDeployment setting in ApexSettings that gives you org-wide control over debug logs during metadata deployment. It defaults to off for performance, but you can flip it on when troubleshooting specific deployment issues. Small thing, but it matters when you're doing multiple deployments a day.

What This All Means Going Forward

Spring '26 feels like a turning point for how Salesforce expects us to build. The platform is clearly moving toward a world where AI agents are the primary interface layer, and everything else - Flows, Apex, LWC - feeds into making those agents smarter and more capable.

If you haven't started experimenting with Agentforce Builder yet, I'd suggest carving out some time this month. The learning curve is surprisingly gentle if you're already comfortable with Flows, and the Agent Script approach gives developers a familiar-feeling on-ramp.

The federated data grounding piece is what I'm most excited about long term. It solves one of the biggest practical challenges with AI agents - keeping them grounded in accurate, current data without building a massive data pipeline.

For anyone building their Salesforce vocabulary around these new features, salesforcedictionary.com keeps an updated glossary that covers both classic and emerging platform concepts.

What features from Spring '26 are you most looking forward to using? Drop a comment - I'm especially curious if anyone's tried Agent Script in a production context yet.

Fix Your Salesforce Data Before Deploying AI Agents

Dipojjal Chakrabarti — Fri, 03 Apr 2026 17:55:38 +0000

Fix Your Salesforce Data Before Deploying AI Agents

Your Agentforce rollout is only as good as the data behind it. I've watched teams spend months configuring autonomous agents, only to get garbage recommendations because their CRM data was a mess. If you're planning to deploy AI agents in Salesforce this year, the single most important thing you can do right now isn't tweaking prompts or building fancy flows - it's cleaning up your data.

Here's why that matters more than ever, and what you can actually do about it.

Why Data Quality Is the #1 Blocker for AI in Salesforce

According to recent industry research, roughly 60% of AI initiatives are expected to fail or get abandoned because organizations lack AI-ready, high-quality data. That's not a Salesforce-specific number - it's across the board. But Salesforce orgs are especially vulnerable because CRM data tends to accumulate junk over years of use.

Think about it. How many duplicate contacts are sitting in your org right now? How many leads have outdated phone numbers or blank email fields? When Agentforce tries to build a Unified Profile in Data Cloud, it needs to reconcile all of that. If it finds three different records for the same person with conflicting info, it doesn't know which one to trust. And that uncertainty cascades into every recommendation, every automated action, every insight the agent surfaces.

81% of sales teams are already using AI in some form. 92% of sales reps interact with AI tools daily. The adoption is there. But adoption without clean data is like putting premium fuel in a car with a busted engine - you're not going to get the performance you paid for.

Start With a Data Audit (Yes, Really)

I know "data audit" sounds like the most boring task on your backlog. But hear me out - you don't need to boil the ocean here. Start targeted.

Pull a report on your most critical objects: Accounts, Contacts, Leads, and Opportunities. Look for these specific red flags:

Duplicates. Run duplicate rules if you haven't already. Salesforce's built-in duplicate management has gotten pretty solid, but it only works if you've actually configured matching rules. For terminology and setup steps, salesforcedictionary.com is a great quick reference if you need to brush up on any of the standard objects or field types involved.

Incomplete records. Sort by fields that matter for your AI use case. If Agentforce is doing lead scoring, you need Industry, Company Size, and Source at a minimum. Run a report that filters for blanks on those fields and you'll probably be surprised how many records are missing key data.

Stale data. If a Contact's last activity was three years ago and they're still marked as "Active," that's noise your AI agent will treat as signal. Set up automation to flag or archive records that haven't been touched in 12+ months.

Inconsistent formatting. State fields with a mix of "CA," "California," and "Calif." will trip up any segmentation or matching logic. Picklists are your friend here - if a field should have a finite set of values, make it a picklist, not free text.

Get Your Data Cloud Foundation Right

Data Cloud is where all of this comes together for AI agents. It's the unification layer that creates those 360-degree customer profiles Agentforce relies on. But Data Cloud can only unify what you give it, and if what you give it is messy, your unified profiles will be messy too.

A few things I've found make a real difference:

Map your data streams carefully. Before connecting external data sources to Data Cloud, document what each source contains, how it identifies customers (email? phone? account ID?), and how frequently it updates. Mismatched identity resolution is one of the fastest ways to create phantom profiles.

Use calculated insights intentionally. Data Cloud lets you build calculated insights - basically derived metrics from your unified data. These are powerful, but they're also where garbage-in-garbage-out hits hardest. If your underlying engagement data is unreliable, a calculated "engagement score" will be meaningless.

Set up data quality dashboards. Build a simple dashboard that tracks completeness rates, duplicate counts, and record freshness across your key objects. Review it weekly. I've seen teams catch data decay early just by glancing at a completeness trend line every Monday morning. If you're not sure what fields or metrics to track, the glossary at salesforcedictionary.com can help you identify which standard and custom fields are most relevant for your specific Cloud setup.

Build Guardrails Before You Scale

Here's something a lot of teams skip: setting up guardrails before they let AI agents loose on production data. Salesforce gives you tools for this - use them.

Einstein Trust Layer. This is your safety net. It handles prompt injection protection, data masking for sensitive fields, and audit logging so you can see exactly what your agents are doing with customer data. If you haven't activated it, do that before you deploy any agent to production. Period.

Field-level security. Review which fields your AI agents can actually access. Not every field in your org should be available to Agentforce. Restrict access to sensitive data like SSNs, payment info, or internal notes that could leak into customer-facing responses.

Prompt and response logging. Turn this on. You want a paper trail of what your agents are saying to customers and what data they're pulling to generate those responses. When something goes wrong (and eventually it will), you'll be glad you can trace it back.

The organizations that are succeeding with Agentforce right now aren't the ones with the fanciest agent configurations. They're the ones that spent time on governance and data hygiene first. It's less glamorous, but it's what separates a useful AI deployment from one that gets rolled back after a quarter.

A Practical 30-Day Cleanup Plan

If you're feeling overwhelmed, here's a simple framework I'd recommend. You don't need a massive data governance initiative to make meaningful progress.

Week 1: Assess. Run duplicate reports, completeness reports, and identify your top 5 dirtiest objects. Prioritize based on which objects your AI agents will touch first.

Week 2: Clean. Merge duplicates, fill critical blanks (or archive records that can't be salvaged), and standardize picklist values. Lean on Data Loader or third-party tools like DemandTools if volume is high.

Week 3: Prevent. Set up validation rules, required fields on page layouts, and duplicate rules to stop new junk from flowing in. This is where most teams fail - they clean once and never prevent recontamination.

Week 4: Monitor. Build your data quality dashboard and schedule a weekly 15-minute review. Set up alerts for when completeness drops below your threshold.

By the end of the month, you'll have a noticeably cleaner org and a foundation that will actually support your AI agents instead of undermining them.

The Bottom Line

Agentforce and Data Cloud are genuinely powerful tools. I'm excited about where autonomous agents are heading in the Salesforce ecosystem. But the teams that will get the most value from them in 2026 are the ones investing in data quality right now - not after their first agent deployment falls flat.

Don't skip the boring stuff. Clean your data, set up governance, build monitoring, and then let your AI agents do their thing on a foundation they can actually trust.

If you found this useful, drop a comment below with your biggest data quality challenge. I'd love to hear what other Salesforce pros are running into. And if you're looking for a quick reference on any Salesforce terms or concepts mentioned here, check out salesforcedictionary.com - it's a solid resource for keeping your terminology straight.

Build Your First Salesforce Agentforce Agent

Dipojjal Chakrabarti — Thu, 02 Apr 2026 23:06:25 +0000

Build Your First Salesforce Agentforce Agent

If you've been following the Salesforce ecosystem at all this year, you already know Agentforce is everywhere. It dominated TrailblazerDX, it's all over the Spring '26 release notes, and every Salesforce recruiter on LinkedIn suddenly wants people with "Agentforce experience." But here's the thing - most admins and developers I talk to still haven't actually built one yet.

I get it. New platform features can feel intimidating, especially when Salesforce markets them with the intensity of a product launch at Dreamforce. But after spending the last few months building agents for clients, I can tell you: getting your first one up and running is way more approachable than you'd think.

Let me walk you through what it actually takes to build your first Agentforce agent, from prerequisites to deployment.

What Agentforce Actually Is (Skip the Marketing Speak)

Before we get into the build, let's cut through the noise. Agentforce is Salesforce's platform for creating AI agents that can take actions inside your org. These aren't chatbots that spit out canned responses. They're autonomous agents that can read your data, follow instructions you define, and execute multi-step tasks.

Under the hood, there are three layers doing the heavy lifting. The Atlas Reasoning Engine processes your instructions and figures out what the user actually wants. Data Cloud Grounding connects the agent to your live CRM data so it's working with real records, not generic training data. And the Einstein Trust Layer handles security - it masks PII before anything reaches the LLM and makes sure your data stays safe.

If you're new to any of these terms, salesforcedictionary.com has solid definitions for Agentforce-related terminology that'll help you get up to speed fast.

Prerequisites: What You Need Before You Start

Here's where a lot of people get tripped up. You can't just flip a switch and start building agents. There are a few boxes to check first.

Data Cloud must be enabled. Agentforce relies on Data Cloud for grounding, which is how agents pull from actual customer records instead of hallucinating answers. If your org doesn't have Data Cloud activated, that's step zero.

Your data needs to be clean. I can't stress this enough. Your agent is only as smart as the data it can access. Duplicate records, stale contact info, outdated knowledge articles - all of that will undermine your agent's performance. Spend time on data hygiene before you spend time on agent configuration.

You need the right permissions. Make sure you have the Agentforce Admin or Agentforce Builder permission sets assigned. Without them, you won't even see the setup options.

Einstein must be turned on. Go to Setup, search for Einstein, and make sure Einstein for Sales or Einstein for Service (depending on your use case) is activated.

Once those boxes are checked, you're ready to actually build something.

Pick Your First Use Case (Keep It Simple)

This is probably the most important advice in this entire post: start small. I've seen teams try to build an agent that handles everything from lead qualification to contract generation on day one. It never works.

The smartest approach is to pick one high-volume, low-complexity task. Think about what eats up the most time for your team but follows a fairly predictable pattern. Here are some first-agent ideas that work really well:

Order status inquiries - Customers asking "where's my order?" is one of the highest-volume support requests for most companies. An agent can pull tracking info, check shipment status, and respond without a human ever getting involved.

Password resets and account lockouts - These are repetitive, simple, and take up way too much of your support team's time. Perfect agent material.

FAQ responses - If your support team answers the same 20 questions over and over, an agent can handle those using your Knowledge articles.

Appointment scheduling - Agents can check availability, book time slots, send confirmations, and handle rescheduling.

Pick one. Just one. You can always expand later.

Building the Agent Step by Step

With the Spring '26 release, Salesforce introduced the Agentforce Builder, which honestly makes this process much smoother than it was six months ago. Here's the actual workflow:

1. Open Agent Builder. Navigate to Setup and search for "Agentforce." Click into the Agent Builder workspace. You'll see a conversational interface where you can start defining your agent.

2. Define the agent's role. Write a clear, specific description of what this agent does. Don't be vague. Instead of "helps customers," write something like "resolves order status inquiries by checking the Order and Shipment objects and providing tracking information to the customer." The more specific your instructions, the better the agent performs.

3. Create topics. Topics are how you organize the different things your agent can handle. For an order status agent, you might have topics like "Check Order Status," "Report Missing Package," and "Request Refund." Each topic gets its own set of instructions and actions.

4. Define actions. Actions are the actual things the agent can do - query records, update fields, send emails, trigger flows. You can connect existing Flows, Apex classes, or use the built-in action types. This is where the real power comes in. If you've already built Flows for common processes, you can wire those right into your agent.

5. Set up guardrails. This is the part people skip and regret later. Define what the agent should NOT do. Set escalation rules so it hands off to a human when it's unsure. Configure the topics it should decline to address. The Einstein Trust Layer helps here, but you still need to set boundaries.

6. Test in the builder. The Agentforce Builder has a built-in testing panel where you can simulate conversations. Use it. A lot. Try to break your agent. Ask it weird questions. Feed it edge cases. This is way cheaper than finding bugs in production.

7. Deploy. Once you're happy with testing, you can deploy the agent to your preferred channel - your website, a customer portal, Slack, or even phone (with Agentforce Voice).

Mistakes I've Seen (So You Don't Repeat Them)

After building agents across several orgs, here are the patterns I keep seeing go wrong:

Skipping the data prep. I mentioned this already, but it's worth repeating. One client had 40,000 duplicate contacts in their org. Their agent kept pulling the wrong contact records and giving customers someone else's order information. Nightmare scenario. Clean your data first.

Writing vague instructions. The Atlas Reasoning Engine is smart, but it's not a mind reader. If your topic instructions say "help the customer with their issue," the agent will flounder. Be specific about what data to check, what actions to take, and when to escalate.

Not setting up escalation paths. Your agent will encounter situations it can't handle. That's expected. What's not okay is leaving the customer stuck in a loop with no way to reach a human. Always configure a smooth handoff to a live agent.

Trying to do too much at once. Build one use case. Prove it works. Measure the impact. Then expand. The teams that take this incremental approach consistently get better results than the ones trying to boil the ocean.

For more Salesforce terminology and concepts that come up during agent configuration, salesforcedictionary.com is a handy reference to keep bookmarked.

Measuring Success

Once your agent is live, you need to track whether it's actually helping. Here are the metrics that matter:

Resolution rate - What percentage of conversations does the agent resolve without human intervention? For a well-built FAQ or order status agent, you should be hitting 60-80% within the first month.

Customer satisfaction - Are customers happy with the agent's responses? Salesforce gives you built-in CSAT survey options for agent interactions.

Average handle time - How long does each conversation take? Agents should be resolving straightforward inquiries in under two minutes.

Escalation rate - How often does the agent hand off to a human? A high escalation rate means your instructions or data need work.

Error rate - Track how often the agent gives incorrect information. This is where Data Cloud observability comes in. With Spring '26, you can now offload Flow execution logs to Data Cloud for deeper analysis of what's happening under the hood.

What's Next After Your First Agent

Once you've got your first agent running smoothly, the natural next step is expanding its capabilities. Add new topics to handle adjacent use cases. Connect it to more data sources using External Objects for real-time data from systems outside Salesforce. Look into Agentforce Voice if phone support is a big part of your business.

The Spring '26 release also introduced some powerful new features worth exploring. The new conversational identity governance lets you set up OAuth and External Client Apps through natural language instead of clicking through a dozen configuration screens. And the Agent Script language gives you fine-grained control over agent behavior when you need something more predictable than pure AI reasoning.

The Agentforce ecosystem is moving fast, and the best way to keep up is to start building. Don't wait until you've read every blog post and watched every Trailhead module. Get your hands dirty with a simple use case, learn from the experience, and iterate from there.

If you've been putting off your first Agentforce build, consider this your sign to start this week. Pick a use case, check your prerequisites, and open up Agent Builder. You might be surprised how quickly you can get something useful running.

Drop a comment below if you've built your first agent - I'd love to hear what use case you picked and how it went. And if you're still figuring out the terminology, check out salesforcedictionary.com for clear definitions of all the Agentforce and AI terms flying around right now.

Salesforce Sales Workspace: Your New Home in Spring '26

Dipojjal Chakrabarti — Thu, 02 Apr 2026 14:40:02 +0000

Salesforce Sales Workspace: Your New Home in Spring '26

If you're a Salesforce Sales Cloud user who's tired of bouncing between tabs, reports, and dashboards just to figure out what to work on next - Sales Workspace is about to change your morning routine.

Salesforce quietly dropped one of the most practical features in the Spring '26 release, and honestly, I think it's not getting enough attention. Sales Workspace is a centralized hub built for individual reps, and it pulls together performance data, AI-driven recommendations, and action items into a single screen. No more opening five tabs before your first coffee.

Let me walk you through what it actually does, why it matters, and how to get the most out of it.

What Exactly Is Sales Workspace?

Think of Sales Workspace as your personalized command center inside Sales Cloud. It's not another dashboard you have to build yourself. It's a pre-built, intelligent hub that shows you:

Your pipeline at a glance, with deals ranked by priority
Agentforce activity summaries showing what AI agents have been doing on your behalf
Meeting prep and follow-up items pulled from Einstein Activity Capture
Lead and opportunity insights so you know where to spend your time

The key difference between this and a regular dashboard? Sales Workspace is dynamic. It doesn't just display numbers - it tells you what to do with them. If an opportunity is stalling, it flags it. If Agentforce qualified a new lead overnight, it surfaces that front and center.

For anyone who's ever wondered what terms like "opportunity pipeline" or "lead scoring" actually mean in practice, salesforcedictionary.com is a solid reference to keep bookmarked. It breaks down Salesforce jargon into plain English.

How Agentforce Ties Into Sales Workspace

Here's where it gets interesting. Sales Workspace isn't just a passive display - it's deeply connected to Agentforce, Salesforce's AI agent platform that's been picking up serious momentum in 2026.

Within the Workspace, you can see exactly how Agentforce has been helping you. That includes:

Leads it qualified based on your Ideal Customer Profile
Meetings it helped schedule through the lead nurturing agents
Account research it compiled before your calls
Opportunity insights it generated from email and activity data

This is a big deal because one of the main complaints about AI features has always been the "black box" problem. You don't know what the AI did or why. Sales Workspace gives you that visibility. You can see the agent's work, review its reasoning, and decide whether to act on its suggestions.

Agentforce has reportedly closed over 9,500 paid deals and is approaching $1.4 billion in ARR. Those aren't small numbers. And with the Spring '26 release, these agents are also accessible through Slack, which means you can get nudges and updates where your team already hangs out.

Setting It Up: What Admins Need to Know

If you're an admin wondering how much work this is going to be - the good news is that Sales Workspace comes largely pre-configured. But there are a few things you'll want to set up properly.

First, make sure Einstein Activity Capture is enabled. Sales Workspace pulls heavily from email and calendar data to generate meeting insights and activity summaries. Without it, you're missing a big chunk of the value.

Second, review your Agentforce configuration. The Workspace reflects what your agents are doing, so if you haven't set up lead qualification criteria or enabled the nurturing agents, the Agentforce section will be pretty empty.

Third, check your org's data quality. This is the theme of 2026 in Salesforce, and I can't stress it enough. With the Informatica acquisition complete, Salesforce is pushing hard on data governance and quality. Sales Workspace will only be as good as the data feeding it. If your opportunity stages are a mess or your lead records are full of duplicates, the insights won't be reliable.

One thing I've found helpful is using resources like salesforcedictionary.com to align your team on terminology. When everyone means the same thing by "qualified lead" or "closed-won," your data stays cleaner.

Finally, consider rolling it out gradually. Start with a pilot group of reps, gather feedback, and adjust before going org-wide. The Setup With Agentforce beta (which launched in January 2026) can actually help here - it offers AI-powered setup recommendations right from the Setup home page.

Why Data Cloud Makes This Even Better

You can't talk about Sales Workspace without mentioning Data Cloud, because the two are connected in ways that aren't immediately obvious.

Data Cloud is what unifies your customer data across systems. When Sales Workspace shows you an account insight or a lead priority score, that information often flows through Data Cloud's harmonized data layer. Salesforce processed 32 trillion records through Data Cloud in a recent quarter, and they've made it clear that Data Cloud is moving from "nice to have" to basically required for any org that wants to use AI features effectively.

If your org isn't on Data Cloud yet, Sales Workspace will still work - but you won't get the full picture. The richest insights come from combining CRM data with marketing interactions, support tickets, and external signals that Data Cloud stitches together.

What This Means for Your Daily Workflow

Here's what a typical morning looks like with Sales Workspace:

You log in and immediately see your top priority deals - not because you built a list view, but because the Workspace ranked them based on deal signals, engagement data, and Agentforce analysis. You notice that a lead was qualified overnight by the AI agent. You click into it, review the qualification notes, and decide it's worth a call.

Next, you see that an opportunity you've been working has gone quiet. The Workspace flagged it because email engagement dropped off. You make a mental note to send a follow-up.

Then you check your meeting prep section. You've got a call in an hour, and Agentforce already pulled together the account research, recent support tickets, and a summary of your last conversation.

All of this without building a single report or running a query. That's the promise, and from what I've seen in the Spring '26 beta, it actually delivers.

Getting Started Today

If you're on Spring '26 (which started rolling out February 23), you can start exploring Sales Workspace now. Here's my quick checklist:

Enable Einstein Activity Capture if you haven't already
Set up your Agentforce agents - at minimum, the lead qualification agent
Audit your data - clean up duplicate leads, standardize opportunity stages
Roll out to a pilot group and collect feedback
Check salesforcedictionary.com if your team needs a refresher on any Sales Cloud terminology

Sales Workspace is one of those features that sounds incremental on paper but changes how reps actually spend their time. Less hunting for information, more selling. And isn't that the whole point?

I'd love to hear if you've already started using Sales Workspace. What's your experience been? Drop a comment below and let's compare notes.