#Agentforce321 人がディスカッション中

Hi @Mudit Chandwani,  

there are several possible ways for you to try to get vouchers :  

Take monthly trailhead quests to try to win gifts/swags and even vouchers : 

https://trailhead.salesforce.com/quests

If your company is Salesforce partner, you may have free vouchers (or discounted ones) according to your partnership level. See with your Salesforce's Partner Account Manager, or the person in charge in your company. 

Good luck for your certification exam preparation ! 

The behavior points more toward a voice-channel serialization or rendering issue with the Custom Lightning Type rather than the Apex action itself. Since the same action works through text and succeeds when the CLT is removed, I’d isolate the CLT schema and test a simple structured output first, then add fields back one at a time. I’d also check the voice action payload and supported output types in Enhanced Chat v2. 

For related troubleshooting discussions, community resources and practical solutions, these types of developer communities can also be useful references.

Hi Ebony, 

Good news: these are pre-built actions that should already exist in the special superbadge org — you're not meant to build them in Challenge 1 (that's Exercise 2, where you create an Invocable Apex class). If they're not showing up, this points to one specific likely cause: you may not be using the special Developer Edition org that comes with this superbadge's pre-loaded Coral Cloud Resorts configuration and sample data. 

To check/fix: 

1. Confirm you signed up for the org through the "Sign up for a free Developer Edition org with special configuration" link on the superbadge unit page itself (Step I), not a generic playground or an existing DE org. This superbadge requires that specific special-config org — a regular org won't have these actions or the underlying Booking/Experience data at all. 

2. If you already have a different org connected, disconnect it and sign up fresh via that link, then reconnect. 

Once you're in the correct org, here's where to find them (per the official exercise walkthrough): in Agent Builder, when adding an action to your topic, use the Add Action search box: 

- Search "Recent" → select Get Most Recent Bookings by Contact 

- Search "Lookup" → select Lookup Experience 

- (Lookup Contact by Email should appear the same way — search "Lookup" or "Contact") 

These are found via search in that dialog, not browsed from a list — if you're clicking through a list instead of typing into the search field, that's worth double-checking too. 

If you've confirmed you're in the correct special-config org and searching properly and they still don't appear, that would point to an org provisioning issue worth reporting via Trailhead Help with your org details. 

Reference:

Hi Josiah, 

There are three prerequisites that are easy to miss even when Agentforce/Einstein look "on": 

1. Agentforce entitlement specifically. Salesforce's own doc flags this separately from just having Agentforce features turned on — "Without the Agentforce entitlement, Builder Central won't load even when the beta setting is turned on." This is an org-level entitlement Salesforce provisions, not just a feature toggle you flip yourself. 

2. Amazon Bedrock Models (Amazon and Anthropic) setting, in Einstein Setup. Builder Central's Build Agent specifically runs through Anthropic models via Amazon Bedrock — this is a separate checkbox from general Einstein enablement, and if your org restricts model providers, this is the one most likely to be missed. 

3. Einstein Setup must be on — until it is, the doc says the Access Builder Central permission doesn't even appear as assignable, which would explain why nothing shows up for you. 

The actual setup path is: Setup → Quick Find → "Builder Central" → Enable Builder Central (Beta), then assign the Access Builder Central permission via a permission set. 

One gotcha specific to your sandbox test: if that sandbox was cloned from another, Einstein settings don't carry over in a clone — the doc explicitly calls this out, so if it's a cloned sandbox, re-enable Einstein Setup there and reassign the permission. 

Given you've already got Customize Application and Agentforce/Einstein generally on in both Prod and a sandbox, but the Setup menu item itself isn't appearing at all (not just failing to load) — that points more toward #1: the Agentforce entitlement for Builder Central specifically may not be provisioned on your org yet, since it's still Beta and rollout isn't universal even for orgs with Agentforce otherwise enabled. Worth confirming with your Salesforce account team whether Builder Central Beta has been enabled for your org, since that's a Salesforce-side provisioning step, not something visible/toggleable from Setup alone if it hasn't been granted. 

Reference:

Hi Tuan, 

I faced the same issue in the Trailhead challenge “Refine Your Prompt Template for Accurate Agent Replies.” 

My Agentforce preview was working correctly, but Trailhead was still showing:

“Challenge not yet complete. Whoops, looks like there was a problem. Please try again.” 

I fixed it by checking the following steps: 

1. Go to Setup → Flows.
2. Search for Get Open Cases for Contact.
3. Open the flow and make sure it is Active.
4. Go to Setup → Prompt Builder.
5. Open the prompt template Guest Experience Compensation.
6. Make sure you are working on the latest version of the prompt template.
7. In the prompt, after Case Details:, insert: Insert Resource → Flow → Get Open Cases for Contact
8. After Complaint:, insert: Insert Resource → Free Text → Complaint
9. Do not manually type the resource names. Insert them using the Insert Resource option.
10. Save the prompt template.
11. Test it in Preview with Sofia Rodriguez.
12. Confirm that the resolved prompt contains:
    • Contact details
    • Open case details
    • Complaint
    • Compensation instructions
13. Click Activate for the latest version of the Guest Experience Compensation prompt template.
14. Go back to the Coral Cloud Experience Agent.
15. Refresh the agent preview and test again.
16. Use: The White Water Rafting experience my family and I booked was unexpectedly cancelled.
17. When the agent asks for customer details, enter:  I'm sofiarodriguez@example.com and my membership number is 10008155.
18. If the agent response is working correctly, go back to Trailhead and click Check Challenge again.

The main things to verify are: 

Get Open Cases for Contact Flow → Active

Guest Experience Compensation → Latest Version Active

Case Details → Flow resource inserted correctly

Complaint → Free Text resource inserted correctly

Thank You, 

Venkat Yadav.

Hi Jayashree, 

Creating/activating an Agentforce Employee Agent needs two specific user permissions you haven't listed — 

To create an Agentforce Employee agent: 

- Manage AI Agents 

- Manage Agentforce Employee Agents 

These are separate from Agent Platform Builder and Execute Prompt Templates, which only cover general Agentforce/prompt usage — not specifically the AgentforceEmployeeAgent template type. Your error message text ("access to agent templates associated with the AgentforceEmployeeAgent agent type") maps directly to these two permissions being missing. 

To fix: 

1. Setup → Permission Sets → check if your assigned permission set(s) include Manage AI Agents and Manage Agentforce Employee Agents as user permissions (search under App Permissions or AI-related permissions in the permission set editor) 

2. If missing, either add them to your existing permission set or create a new one with both checked, and assign it to your user 

3. Retry the Commit/Activate action on the agent 

This is likely why the error is specific to activation and not the earlier steps (enabling the feature, creating from template) — those work with Agent Platform Builder alone, but committing/activating an Employee Agent specifically checks for the two Manage permissions above. 

Reference:

Hi Bijay, 

On Q1: this has actually changed. Einstein Knowledge Creation now supports custom Prompt Templates via the "Knowledge Generation" type in Prompt Builder — not limited to the single default case-only template anymore. Build a custom template tailored to your use case; that's the current recommended path. 

For pulling in Comments/Emails/Work Notes without manual concatenation: 

- Flow-based grounding: attach a Flow as a grounding resource in Prompt Builder — it queries related records and feeds them in structured, instead of one giant merge field. 

- Retrievers (Data Cloud): for larger/unstructured volumes, index content into a Data Library and use a Retriever (via Einstein Studio) for semantic retrieval instead of dumping everything into one flow output. 

For grounding accuracy / avoiding invented resolution steps: 

- Add an explicit negative instruction in the prompt: "Only use information present in the provided context. Do not infer steps not explicitly stated." This measurably reduces over-inference. 

- Split classification from generation — use a separate Field Generation prompt just to classify Final Solution/Workaround/Improvement/Enhancement (same context), then pass that result into the Knowledge Generation prompt. Two narrow prompts outperform one prompt doing both. 

- Add 2–3 labeled few-shot examples of each resolution category in the prompt instructions — this taxonomy is business-specific, so there's no built-in classifier; examples are what actually stabilize classification. 

No native accelerator exists for the resolution-type classification specifically — that part is custom prompt engineering, not a toggle. 

Reference: