#Agentforce369 discussing

Hi @Alyssa Jenson , I put Agentforce Coworker

to work on a single account and saved serious time. From one screen, I compared two promotions, checked the customer sentiment score and updated contact details instantly.  

It’s a game‑changer for efficiency and customer experience — all in just a few clicks! 

Link:

@KANAKA RANGARAO PARIMI The Agent Access tab isn't part of Agentforce Builder — that's why it's not showing there. It lives inside a Permission Set.

To grant access to your custom agent:

1. Setup → Permission Sets → open one (or create a new one).
2. In the Apps section, click Agent Access → Edit.
3. Add your agent from the list of active agents → Save. (It only appears here if the agent is Activated — if it's missing, activate it in Agentforce Builder first.)
4. Assign that permission set to the users who need the agent.

So the path is Permission Set → Agent Access, not the Builder. Once assigned, those users get access.

if this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂

Hello Amit, 

Yes, this can happen due to backend synchronization/caching. Newly created Flows may take a few minutes before they become available in the Reference Action dropdown for a subagent. It’s not usually an issue with the Flow itself. There doesn’t seem to be a fixed guaranteed propagation time, but in practice, waiting a few minutes and refreshing/reopening the action configuration usually makes the Flow appear. Hope this helps!

 Hi Darren, 

It sounds like the booking was created correctly, but the Trailhead verifier may not be picking up the booking as expected. I’d suggest trying the booking step again and making sure it is for Miko Mitsumi’s family of 5, with the Magical Aquarium Tunnel Tour session and the status set to Confirmed or Completed. 

If everything looks correct and the verification still fails, it could be a syncing or Trailhead issue. If the issue persists, I’d recommend creating a Salesforce Support case so they can check the underlying booking data. 

Hope this helps!

Hi Prathyusha, I recently went through this certification myself and completely understand the frustration with outdated Udemy content. Here is a comprehensive, up-to-date study guide that actually reflects the current Spring '26 state of Agentforce: 

OFFICIAL SALESFORCE RESOURCES (Most Important - Always Current) 

1. Agentforce Specialist Exam Guide:

- search "Agentforce Specialist exam guide" - study every topic listed 

2. Trailhead Trail: "Get Ready for Agentforce" - this is THE official prep trail, updated regularly 

3. Trailhead Trail: "Design and Implement AI Agents with Agentforce" - covers building, testing, deploying 

4. Trailhead Module: "Agentforce for Admins" - foundational concepts 

5. Trailhead Module: "Prompt Builder" - critical for the exam 

KEY EXAM TOPICS TO MASTER (Based on Exam Guide): 

- Agentforce architecture: Agents, Topics, Actions, Instructions 

- Types of agents: Service Agent, Sales Agent, SDR Agent, Internal Agents 

- Agent Builder vs Agentforce Studio 

- How Topics and Actions work together 

- Prompt Templates (Standard, Flex, Sales Email types) 

- Grounding: what it is, how Data Cloud and Knowledge ground agents 

- Testing agents in Agent Builder Preview pane 

- Agentforce for Slack and Agentforce for Mobile 

- Einstein Trust Layer: data masking, toxicity detection, audit trail 

- Agent Analytics and monitoring 

DEV ORG AVAILABILITY ISSUE (Your Main Problem) 

Many Agentforce features require specific Einstein/Agentforce add-on licenses that the standard Developer Edition org does NOT include. Here is how to get proper hands-on access: 

- Request a free Agentforce Developer Edition from:

(look for "Agentforce Dev Org" - these have Einstein licenses included) 

- Use Trailhead Playground orgs created specifically from Agentforce badges/superbadges - these provision the right licenses automatically 

- Look for the "Quick Start: Agentforce" Trailhead project - it provisions a properly licensed scratch org 

SUPERBADGES TO COMPLETE: 

- "Quick Start: Build Your First Agent with Agentforce" (beginner) 

- "Agentforce Service Agent" superbadge 

- "Build Agents with Agentforce" trail 

FREE LIVE RESOURCES: 

- Salesforce Ben's Agentforce certification guide on

(free, very current) 

-

- official community for Agentforce practitioners 

- TDX (Salesforce TrailblazerDX) session recordings on YouTube - March 2026 content is very relevant 

Avoid Udemy entirely for this cert - the platform moves too fast. Stick to official Trailhead and Salesforce Help documentation. 

Good luck with the exam - it is very achievable with the right resources!

@Reno Redaja

Document Processing runs as an Agentforce agent action, so it isn't on a separate meter - it draws from your Agentforce Flex Credits (the same metered pool your agent actions use, billed monthly in arrears). Data Cloud has its own Flex Credits for Data Cloud operations, but the agent-action invocation itself is Agentforce credits. 

To see it, go to Setup > Digital Wallet - that's the central, near-real-time dashboard for Flex Credit consumption (agent actions, usage, balances). You won't find a line literally labelled 'Document Processing'; it shows up as the consuming agent's action usage, so read it there by agent/action. You can also add Consumption Threshold Alerts via a Flow to get notified as usage climbs. 

If this helps, please mark it as the Best Answer so it helps the next person - thanks!

@Manas Datta

Thanks for testing that - a correct id still landing on the bare panel actually rules the id out and points to an enablement gap. open() drives the SAME native Agentforce side panel you'd get manually, and botId is only optional targeting - if that agent isn't the one wired to the panel for your running user, open() falls back to the default panel/picker no matter which id you pass. 

Quick way to confirm: open the native Agentforce panel manually (the Agentforce icon, not your LWC). If it also drops you on a picker or the wrong agent, it's the setup, not your code - check the agent is Active, is the one enabled for the Agentforce panel in that org, and your running user has access to it (permission set + the agent's assigned users). Fix that and open(botId) will land on it. 

If you need a specific agent guaranteed every time regardless of the panel, skip accApi and use the Agent API instead (Connect REST /einstein/ai-agent, or its Apex wrapper): you start a session against the exact agent id server-side and render the replies in your own LWC chat UI - no panel, no picker, fully deterministic.