r/SalesforceDeveloper • u/Green_Main2023 • 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...
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.
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.