share one way agents are impacting your business.
Agents are impacting business by completing routine tasks, answering the repeated questions from customer. By doing these, it gives more time for the team to work on other important tasks and build new things.
I have an interesting Salesforce use case to share.
It’s about connecting Salesforce Revenue Cloud with WhatsApp, so parts of the ordering process can happen directly in chat.
For example, a customer can send an order request in WhatsApp, receive pricing options, confirm billing and shipping details, and then have the order created in Salesforce Revenue Cloud
I think this is a cool example of where AI and Headless CRM can be genuinely useful. Not just as a fancy add-on, but as something that removes a few extra steps from the process.
We’ve been exploring this approach, and it’s exciting to see how much simpler some Revenue Cloud processes can become when you bring them into a chat experience.
Has anyone else tried something similar with Salesforce and messaging apps?
Hi everyone,
I am hitting a brick wall with the Local_Info_Agent simulation in VS Code. Despite following the "manual permission assignment" fix mentioned by Eduardo and Swati and by Bhoopesh, I am still receiving the generic "Something went wrong. Internal Error, try again later" message every time I click "Start Simulation."
Here is everything I have verified and executed so far:
Despite a 100% successful environment setup and manual permission overrides, the simulation server still fails. Is there a known issue with the LLM gateway for this specific module, or a hidden permission (perhaps related to the Einstein Agent profile itself) that the setup script is failing to bridge?
Any insights would be greatly appreciated!
AI agents are transforming how our team works — from synthesizing vendor research and tracking action items across multiple workstreams, to keeping documentation up to date in real time. Tasks that used to take hours of manual effort now happen instantly, freeing us up to focus on strategy and decision-making. Agentforce is making our team faster, more aligned, and better informed every day.
Hello Everyone! 👋
I'm excited to be part of this community.
One way agents are impacting business is by helping automate common customer requests and providing faster support. This saves time for support teams, improves customer experience, and allows employees to focus on more important tasks.
Looking forward to learning from everyone and exploring more about Agentforce!
Thanks and Regards.
Pooja Bhattacharya
Hi everyone,
If you are testing your agents locally using Agentforce DX / Vibes and hitting a generic "Something went wrong" error pointing to missing permission sets (like AgentforceServiceAgentBase or EinsteinGPTPromptTemplateUser) during live test execution, check your sub-agents.
The Issue: This often happens due to an unpopulated reference in the agent script under Local Events. The Fix: Look at your Check Events action under your local sub-agent. If the Reference action type is blank, manually select or set it as a Prompt Template. You can right-click the script and run AFDX: Validate This Agent to verify your structure before starting the simulation server again.
Hope this saves some troubleshooting time!
#Agentforce #VSCODE #Apex
If you’re testing locally with Agentforce DX / Vibes and get a generic “Something went wrong”
error mentioning missing permission sets like AgentforceServiceAgentBase or EinsteinGPTPromptTemplateUser, don’t only check permissions.
In some cases, the real issue is an unpopulated reference in the agent script.
Go to your Local Events sub-agent and check the Check Events action. If the Reference action type is blank, set it to Prompt Template.
Then right-click the agent script and run
AFDX: Validate This Agent before restarting the simulation server.I'm getting a "No JSON found in AI response" error when using planner mode in agentforce vibes 2.0.
I've encountered this error in both the PRD and the Tasks steps of the planner. I tried both available models (Claude Sonnet 4.5, GPT 5-mini) and different project ideas, but I always get this error.
In the PRD step it failed while creating the file tree, and in the task step failed while generating the last task.
Any idea what could be the problem?
Two things to try:
Smaller project idea first. Fewer tasks, simpler scope. Confirm planner works end to end, then scale up. This tells you whether it's a size problem or a config problem.
Try the Chat tab instead of Planner for the failing steps. Chat doesn't enforce JSON structure so it won't break the same way. Use it to generate the PRD or task list manually, then feed results back in.
If it fails on even small projects, log a GitHub issue at forcedotcom/Einstein-GPT-for-Developers. Include your Salesforce Telemetry ID from the error. That's the fastest path to a fix since this is an extension bug, not an org config issue. The Salesforce team actively monitors that repo.
One more thing: make sure the extension is on the latest version. Check VS Code Extensions panel, find Agentforce Vibes 2.0, confirm no update is pending. A patch may already exist.
share one way agents are impacting your business.
We are Agentforce to get customer service up and running with a new business line. Agentforce is assisting customer service to understand process and complete tasks on be half of them.
Agentforce is impacting our business is by helping us stand up customer service for a new business line faster.
Instead of expecting every service rep to fully learn a new process from day one, Agentforce can guide them through the right steps, surface relevant information, and assist with routine tasks. That helps the team respond more consistently while still keeping humans involved for judgment, exceptions, and customer relationship moments.
This is where I see the value: not replacing the service team, but helping them ramp faster and spend less time figuring out the process. Salesforce describes Agentforce for Service in a similar way, as an AI agent grounded in trusted business data and knowledge that can support customer service teams and automate common tasks.
We are trying to explore the Agentforce Vibes 2.0 (in the preview mode). There are lots of changes from the previous versions. However, the Vibes documentation has not been updated with the 2.0 features and changes. The VS code Marketplace gives very high level overview of the key features. When can we expect to have a detailed documentation for Agentforce Vibes 2.0?
Two things I didn't like, first there wont be any free usage, which completely kills the main objective of using Agentforce Vibes.
Secondly the IDE is assuming we will work only on one project.
I've setup in a dev org a custom agent that works fine in back-end. I was also able to build and publish an experience site among with all the necessary configurations: setup Messaging for In-App, Routing configuration, Omnichannel flow, add "Embedded messaging" component etc..).
On Experience builder side, I can see the logo to initiate chat:
However, when I click preview to test the chat and launch agent, I don't see the icon for initate the chat:
Does anyone have any idea what can possibly be the reason?
I know this should work because I'm recreating a similar excercise as project "
Quick Start: Build a Service Agent with Agentforce
".
Thanks in advance for your help,
Hi @Jai Yadav
,
Apologies for my late reply.
It's been a while I've implemented the custom agent in experience cloud site. Did you check my previous comment on my reported issues ? Maybe the following can help:
I hope this will help you.
BR