Agentforce Coworker: Salesforce Just Put an AI Teammate in Every Search Bar

I was three sips into an overpriced flat white in a Sydney café last week when an old client pinged me on Slack with one of my favourite questions of the year so far. "Mate, is this Coworker thing real, or are we back on the renaming carousel?"

Fair question. And one I suspect a few hundred CIOs around APAC are quietly asking each other right now.

So here we go.

On 21 May, Marc Benioff announced Agentforce Coworker, pitched as an AI teammate that lives inside every Salesforce search bar. The claim isn't that it finds things faster. It's that it reasons across your CRM data, workflows, customer history, opportunities and cases, and then takes action in real time. Coworker is in beta now for every Agentforce customer across Enterprise, Unlimited and Agentforce1 editions, and Salesforce says it follows you across Salesforce, Slack, Teams and even ChatGPT. You type into a search field the way you always have. Instead of a list of records to click through, you get an agent that does the thing.

My first reaction was the eye-roll I keep on standby for launch day. We've all sat through eighteen months of Agentforce-branded releases by now, and it's become genuinely hard to separate what moves the needle from what's slideware. Salesforce has earned a chunk of that scepticism by renaming products at a pace that would embarrass a witness protection programme.

Then I read Andrew Russo's write-up. If you don't know Andrew, he's one of the sharper technical voices in the ecosystem and not a bloke prone to gushing. He sat down expecting to write a takedown and couldn't find one to write. He described Coworker stitching together complex sales and ERP data to answer questions that, the day before, would have meant the better part of an hour swivel-chairing between systems.

What it actually is

Coworker is a search-led front door to agentic action. You search, it reasons across your data, it acts. Setup is mostly automated. Flip it on in Setup, confirm, and Salesforce provisions the search agent, connects your CRM, and stands up the infrastructure for you. You'll need a Data 360 Admin or Architect and the right permission set licences, but the plumbing is largely done for you. Mehul Sharma's setup walkthrough is the cleanest practical guide I've seen so far if you want to peek under the bonnet.

Here's the part the coverage is honest enough to admit. The community can't quite agree on whether this is a genuinely new product or a tidy repackaging of things already in flight. The in-app Help Agent, AI-powered search, the broader UI reinvention that's been running since the Slack CRM news. There's a live thread on r/Salesforce asking exactly that, and given the rename history, the question is more than fair. Salesforce Ben has gone back to Salesforce for clarification, which tells you the positioning wasn't crystal clear even to the people whose job it is to cover this stuff.

I'm not raising this to be cute. How you classify Coworker changes how you plan for it. If it's a new agentic surface, you architect for it. If it's a repackage of capability you already pay for, you audit what you've already got before someone sells you the same horse twice.

Why the search bar is genuinely clever

Set the naming circus aside. The move underneath it is smart.

For years, the friction in Salesforce hasn't been a lack of power. It's been the swivel chair. Open a record, copy a number, switch tabs, paste it elsewhere, hunt for the related case, switch back, swear quietly, repeat. Anyone who's watched a service agent work a complex inquiry knows the real productivity tax isn't thinking. It's navigating. Salesforce has started counting the alternative explicitly. The company claims 2.4 billion "agentic work units" delivered across Agentforce and Slack so far. Strip the marketing veneer off that and what you're really looking at is a measure of swivel-chair minutes eliminated.

Putting the agent in the search bar attacks the problem head-on. The search bar is the one piece of universal real estate every user already touches a hundred times a day. Nobody needs training to find a new app. The behaviour is already there. You're only changing what happens after they type.

That's what most "AI transformation" launches get wrong. They add a surface. Another panel, another assistant, another place to go. Coworker subtracts one.

The bit that won't make the keynote

Now the role nobody at the launch wants to play.

An agent that lives in your search bar and acts across your CRM is only ever as good as the data underneath it. Coworker doesn't change that maths. It raises the stakes. The blast radius of bad data scales with the surface area of the agent, and Coworker has enormous surface area.

I was working with a financial services client earlier this year who wanted autonomous agents across customer service by end of quarter. A reasonable ambition. Then we looked under the bonnet. Forty-odd record types hanging off the Account object, case routing held together with sticky tape and three generations of half-documented Flows, and knowledge articles last touched during the pandemic. Put a Coworker-style agent on top of that and you don't get a miracle. You get wrong answers, delivered faster, with more confidence, to more people, in more places.

The economics sharpen the point. Agentforce reasoning isn't a flat licence. It's metered consumption, and the bill scales with how hard the agent works. Salesforce's own numbers show the trajectory. Agentforce ARR hit $800 million at the close of FY26, up 169 per cent year on year, and more than 60 per cent of Agentforce and Data 360 bookings last quarter came from existing customers expanding. The meter is already running in orgs that look an awful lot like yours.

So before anyone flips it on, here's the order of operations I'd run.

None of that is glamorous. It's the same unsexy foundation work I've been banging on about for years. But it's the entire difference between the orgs that get real value out of this and the ones that spend next year wondering why their shiny new teammate keeps embarrassing them in front of customers.

Worth your attention?

Yes. Genuinely, and more than I expected.

If Coworker delivers even half of what the early reactions suggest, it's the most meaningful step yet in Salesforce's campaign to make the platform something you act through rather than something you log into. The search bar is the right surface. Automating the setup is the right call. And a hardened sceptic failing to break it is worth more than any number of executive posts.

But it's a beta, the positioning is fuzzy, and the value is entirely downstream of how clean your foundation is. Worth noting too that Salesforce itself guided FY27 a touch below where Wall Street wanted it. Even the company building this knows adoption gets paced against proof of value. The technology is ready. The real question, as always, is whether you are.

The Bottom Line

If you're running Salesforce in Sydney, Auckland, or Singapore, two things matter more than the demo.

First, your data model is almost certainly messier than the one in the launch video. I have yet to see an APAC enterprise org where Sales, Service and Marketing agree on what a "customer" is without an argument, a whiteboard, and at least one biscuit. Coworker will not paper over that. It will exhibit it.

Second, regional regulators are paying attention. APRA in Australia, MAS in Singapore, the FSA in Japan, none of them are going to be charmed by "the agent did it, your honour." Have your audit trail, your data residency story and your human-in-the-loop boundaries written down in plain English before someone asks. Bonus points if it's also written in the language of the regulator who's about to ask.

Fix the boring stuff first. Then go and meet your new teammate.

Or don't. Hand it broken data and free rein across the org, and I'm sure that'll go brilliantly.

Sources

---

Robin Leonard is a Partner at Xenai Digital, an APAC enterprise Salesforce and AI consultancy. 9x Salesforce certified, with form leading enterprise transformations across Australia, New Zealand, Singapore, Japan, and the broader Pacific. Splits his time between Auckland, Sydney and Tokyo, and rides a Royal Enfield Himalayan 450 when the weather agrees with him. linkedin.com/in/robinleonard1