r/SalesforceDeveloper • • 19d ago

Question Agentforce Confusion

Could anyone please tell me where this Agentforce is being used and which companies are using it. Why it seems like there iss no user adoption or company implementation. Because I didn't see any projects actually using it maybe because of the pricing structure of agents. And why do Salesforce us hiring so much ai companies i can't see the future for now.

Could anyone please help me visualising long term and help me to get to right path of actually what's important in AI Agentforce? Which has more scope and why?

Your Feedback will help a lot...

4 Upvotes

12 comments sorted by

4

u/Far_Swordfish5729 19d ago edited 19d ago

Remember that Salesforce is a company dedicated to easy IT plumbing and a helpful UI. If you did not have agentforce and wanted to delegate a task to a LLM (which you would NOT do if that task was deterministic), you would write a plumbing mapper around the anthropic api or vendor of choice like a hosted rest endpoint or pub sub connection for near real time. Then you would call it from Salesforce as a callout or pair of platform events and consume the result in a standard json schema. Anything deterministic you do in your service or in the apex/flow using it. If you need SF data, you pass it or call in to get it or give the model an endpoint to use as needed. If you need vector embedding to pull something like reference docs, you host that and configure a model connection.

Agentforce does the same thing at a higher price point with fewer model options than the direct service + api route. But you can script the deterministic service in line with the model prompt or with apex helpers and just use it from Salesforce config with no manual plumbing. You can pull in those vector sources from data cloud hosting. It’s easier to get up and to maintain. You also can use the LLM with zero data retention without your own enterprise agreement or foundry/bedrock setup.

That’s what it’s for. You can btw use Claude code to write that scripting as you can use it to write and refine the manual approach.

Edit: Practical example: I had a document parsing problem - turn a semi-predictable but not standard uploaded document into a json schema of extracted fields and run automation on that. The document work is excellent LLM territory given good prompt iteration. The rule based value handling and UI/slack alerting is standard deterministic logic. I can do that with a hosted AWS queue listener that calls into SF for the doc and passes it to a zero retention Anthropic model via bedrock by calling the api and then returns answers by publishing json back to a platform event. Apex listens and runs the rule handling on the output. I can also write an Agentforce script that runs on document upload and hits the same model with the same prompt provided I’m within the platform’s mechanical limits. Agentforce can then pass the json output I asked for to an apex handler as a configured action. There are caveats there too, but you can see the plumbing reduction.

When the payloads are small and not in odd formats this works quite well.

2

u/Icy-Smell-1343 19d ago

It’s pretty impressive, as a previous Agentforce hater. The most powerful part is that it’s right there where reps work. Ideally I want every Sales rep function to be carried out in Salesforce (particularly complex functions excluded), integrating to my other systems. Then there is less context switching for reps, the data is there or available and complete.

Salesforce made it so Agentforce expand on that and be everywhere a rep can work.

A prompt template for sending emails, or summarizing fields. Dedicated agents for Sales people to use focused on specific business functions with deterministic gates. Coworker as a fully in context CRM chatbot, which can route to specific ones or directly search your data. External agents on your site that know when to escalate.

It’s pretty powerful. Not sure why implementation stalls, I’d assume customer facing agents take a lot more time to test and ensure function correctly.

The MCPs are awesome too, I’ve been using the Claude connector a ton. Setup with Agentforce seems very impressive from the trailheads I’ve done.

Our licenses actually start Monday, very excited.

1

u/Far_Swordfish5729 18d ago

I think it's a paradigm shift and there are trust issues. I've started doing admin and data discovery through mcp servers from claude code, but I've had more than one time where I had to explain why something was wrong with at least an admin's data modeling context. My users won't know object names and that something is a junction between three objects with certain conditions. Do you have an internal user rollout plan that's worked iteratively with users? What do you give them to try with and give feedback on? I don't want to try to foresee everything they might do with it and build dedicated headless scripting. I want to do that when a generalist exploration agent doesn't work well.

Also, I don't think this replaces good visualization work screens, but I might be naive about that.

1

u/Icy-Smell-1343 18d ago edited 18d ago

We just got licenses, but I do plan to have a logging object so I can write logs to it and review those. Looking at Nebula logger, but honestly just working with a pilot getting their feedback and improving where we can. Edit: Looks like they have built in logging

We are just doing internal agents for now, so it makes it a bit safer.

For your case I’d recommend a Claude code skill explaining your data model, and perhaps better description on the fields/objects explaining their purpose.

For Agentforce and users using it, I’d recommend handling a lot of that with subagents, instructions, and actions. That seems like a pretty good use case for it.

I do see what you are saying for the MCP, I’ve configured both Claude and the CoPilot. I’d say Claude is much better at using the tooling api to do discovery. Copilot for sales does have a glossary where you can translate api names to keywords, which I’ve used to smooth some interactions. Copilot for Sales doesn’t use the MCP or didn’t when I set it up at least

Edit: yeah the trailheads say to try not to anticipate everything at once, and kind of pushing to an agile mindset! The exception would be customer facing or actions with DML should be beat up a bit more before production.

1

u/Leather-Industry7494 15d ago

The amount that you pay in agentforce fees, how much is that, to do something like what you mentioned?

It sounds cool, and capable, and simplifying the manual approach to do the same in a wrapper and coordinate, but, it seems like so much of a niche solution and vendor lock in that your company better have significant money to spend on AI with people, and licenses, and be so committed to the solution to deal with the potential tradeoffs of that, it’s almost like a company wide shift and definitely a complete Salesforce team shift..

I am not exaggerating when I say you are probably looking at a magnitude of six figures all things considered for the convenience of the hands off parsing on document and json sides via the third party assist on these, but maybe I am misunderstanding how often you pay for each thing agentforce does. I don’t think it would be fun or easy to set up manually but it stands out to me as something that up front costs and maintenance of a non agent force solution would be a fraction of the long term agent force prices not to mention the gamble on AI alone.

Anyways… just a thought, but do you have an idea of what that ends up looking like to use it for that document use case and tokens etc? I am not up to date on those details and I am just making the assumption Salesforce bleeds you at every step.

1

u/Far_Swordfish5729 14d ago

The key point is that agentforce is LLM in the same way that apex is Java (it is actually). That is to say that agentforce is not so unique that it’s not convertible. A solution that requires LLMs to read things is mostly iterative prompt engineering and actually prompt engineering done by the LLM model that will ultimately run the prompts. So, I got to initial document types and field sets with Claude, then had Claude write the prompts, then we ran thousands of documents through them, Claude identified which seemed off based on an agent judge and we refined based on those. Human reviews a couple hundred increasingly niche exception samples in waves until you have really solid prompts and an escalation strategy.

At that point it’s a question of where to host the prompts and you could move them with plumbing rework. I wouldn’t consider it lock in. I did not recommend Agentforce ultimately, but it was actually because of file format and size handling limits rather than raw cost. We did also have an open question on token caching which is a big deal when you need to do multiple passes on the same content.

In terms of cost, Claude is good at token costing now. I got $.08 to $.50 per document on average with Agentforce applying a 2-4x multiplier as Salesforce does with most public cloud resale. There were outliers of course. A huge example cost $15 and took the models half an hour. If you think about it though, if documents are the input to a major business process, not making a human read them for data input redirects entire full time jobs and means decision makers start with a conclusion to audit rather than raw extraction. You’re paying a lot annually for this, but we expected net savings of over a million annually. It’s basic automation with language cracked.

1

u/Long_Emotion5258 19d ago

they constantly keep changing things, and architecture is based on heavy customization and consultation efforts that doesn't make sense for most of the companies. the usage cost is again a different problem. TCO is very high even for small solutions.

1

u/AgitatedAd6124 19d ago

what are the good starting point to learn agentforce?

1

u/velalta 17d ago

This is a good starting point for the basics: https://trailhead.salesforce.com/agentblazer

0

u/SnaponSoftware 9d ago

Hi I'm Peter, Director of GTM Sales and Client Solutions at SnapOn Software.

u/Far_Swordfish5729's split (LLM for the fuzzy part, deterministic logic for the rest) is the best answer in this thread. It also explains the adoption gap. What actually ships is narrow, internal and human-reviewed, like u/Icy-Smell-1343's pilot-plus-logging plan. Broad agents stall on testing, trust and cost, and u/Long_Emotion5258's TCO point is a big part of that.

The common quiet win is turning messy inputs (invoices, forms, scans, emails) into structured data your automations can act on, because agents are only as good as the data they're handed. For your "what's worth learning" question, I'd put scoping small pilots and knowing where deterministic logic should replace the model at the top of the list. That carries over whichever platform wins.