Agentforce Course Module 12: Deploy to Experience Cloud | sfinterviewpro.com
🌍 Agentforce Free Course — Module 12
Deploy to Experience Cloud
Embed your Agentforce AI agent in customer-facing portals, self-service sites, and partner communities using Experience Cloud. Take your agent from internal to customer-facing.
🌎 Experience Cloud🤖 Embedded Agent👥 Customer Portal🌐 Self-Service🎯 XYZ Company
Course Progress
Module 12 of 15 — 80% Complete
💡
What is Experience Cloud Deployment?
Taking your agent from internal tool to customer-facing powerhouse
🌎 Definition
Deploying Agentforce to Experience Cloud means embedding your AI agent into customer-facing Salesforce sites — customer portals, partner communities, self-service help centers. External users (customers, partners) can interact with your agent directly on your website without needing a Salesforce license.
🌟 Deployment Architecture
👥 External UserCustomer/Partner
→
🌎 Experience SiteCustomer Portal
→
🤖 Embedded AgentChat widget
→
👁 AgentforceAI processing
→
✅ ResponseBack to user
🎯 XYZ Company Use Case
XYZ Company wants customers to check their order status, get product specs, and raise support requests — all from the customer portal — without calling a sales rep. Deploy the XYZ Sales Assistant to Experience Cloud and let customers self-serve 24/7.
Unauthenticated agents can only access data you explicitly permit. Never allow guest users to query Account/Contact data without authentication. Use authentication for sensitive queries — agent should prompt login for order history, account details.
👥 Step 4: Configure Authenticated vs Guest Agent Behavior
Your agent should behave differently for logged-in vs guest users — more personalized for authenticated users.
// Topic Instructions — Authentication-Aware BehaviorTopic: Customer Self-ServiceInstructions:
1. Check if user is authenticated (logged in to portal)
- Authenticated: Use {!$User.Name} to personalize greeting
- Guest: Greet generically, limit to public info only
2. For authenticated users:
- Allow order history queries
- Allow case creation
- Allow profile/account info queries
- Full agent capabilities enabled
3. For guest (unauthenticated) users:
- ONLY answer product questions from knowledge base
- ONLY provide general company information
- For order/account queries: prompt to login first
- Message: "Please log in to access your order details"
4. Session context:
- Store conversation context across page navigations
- Clear sensitive data from context after session ends
Guest-safe Topics (public):
✓ Product specifications
✓ Company contact information
✓ General FAQs
✓ Office locations and hours
Authenticated-only Topics:
✗ Order history
✗ Account details
✗ Invoice queries
✗ Personal data
🌟 Step 5: Customize Agent Appearance
Match the agent’s look and feel to your Experience Cloud site branding.
1Setup → Embedded Service Deployments → New or Edit existing deployment
2Branding & Appearance: • Primary Color: #6D28D9 • Secondary Color: #EC4899 • Agent Avatar: Upload XYZ Company logo or robot icon • Chat Window Title: “XYZ AI Assistant” • Welcome Message: “Hi! I’m XYZ’s AI assistant. How can I help you today?”
Once logged in, I can show you real-time order status, tracking information, and complete order history!
✅ Agent correctly blocked order query for guest user and prompted login. Security instruction working!
🎯 Test 3 — Authenticated Customer
Ravi Kumar (logged in, MedTech Solutions): Hi, any updates on my recent orders?
XYZ AI Agent: Hi Ravi! Welcome back. Here’s a quick update on MedTech Solutions’ recent orders:
📋 ERP-28947 — Delivered on 20 May ✅ 📋 ERP-28651 — In Transit — ETA: 26 May 🚙
Your next scheduled order is due on 5 June. Would you like to modify quantities or confirm it?
✅ Authenticated user: personalized greeting using {!$User.Name}, full ERP + Salesforce data access, proactive upsell opportunity!
🔒
Security Best Practices for Public Agents
Critical for production deployments
Risk
Prevention
Implementation
Prompt injection attacks
Einstein Trust Layer filters inputs
Auto-enabled in Agentforce
Data leakage to guests
Topic Instructions + Guest Profile FLS
Explicit auth check in instructions
PII exposure
Trust Layer PII masking
Configure in Trust Layer settings
Unlimited API usage
Rate limiting + session management
Embedded Service deployment settings
Cross-site data bleed
Session isolation per user
Auto-handled by Salesforce
Bot abuse
CAPTCHA + rate limiting
Embedded Service security settings
🚨 Never Do This in Public Agents
❌Allow guest users to query Customer/Account data
❌Return Salesforce record IDs in agent responses (use names/labels)
❌Allow agent to execute DML (create/update/delete) for unauthenticated users
❌Skip testing with guest profile before publishing
🎤
Interview Q&A — Experience Cloud Deployment
Real questions from Agentforce interviews 2026
Q1
How do you deploy an Agentforce agent to an Experience Cloud site?
✅ Answer
1) Create Experience Cloud site (Digital Experiences → New). 2) Add Embedded Service Chat component to site pages in Experience Builder. 3) Link component to your Agentforce deployment. 4) Configure guest user profile permissions. 5) Add Experience Cloud channel to agent in Setup → Agents. 6) Publish the site.
🎤 One-Line Answer
"Create Experience site → add Embedded Service Chat component → link to Agentforce deployment → configure guest permissions → add Experience Cloud channel to agent → publish."
Q2
What is the difference between how an internal Salesforce user and an Experience Cloud guest user interacts with Agentforce?
✅ Answer
Internal user (M4): full Salesforce session, all Salesforce data accessible, no authentication step needed, agent sees all permitted records. Experience Cloud guest: unauthenticated, limited to publicly allowed data only, no Salesforce record access unless explicitly permitted, must prompt login for sensitive queries.
🎤 One-Line Answer
"Internal: full authenticated Salesforce session, all permitted data. Guest: unauthenticated, public data only, must prompt login for sensitive queries. Topic Instructions control the boundary."
Q3
What are Embedded Service Deployments in Salesforce?
✅ Answer
Embedded Service Deployments configure how the Agentforce chat widget appears and behaves on websites and Experience Cloud sites. Controls: branding (colors, avatar), pre-chat form, offline behavior, routing, authentication settings, rate limiting. One deployment can be used across multiple sites.
🎤 One-Line Answer
"Embedded Service Deployment: configuration for chat widget appearance, branding, pre-chat form, offline behavior, and security settings. Referenced by Experience Cloud components and website embed codes."
Q4
How do you handle security for a public-facing Agentforce agent on Experience Cloud?
✅ Answer
Multi-layer approach: Einstein Trust Layer handles PII masking and prompt injection filtering. Guest User Profile FLS restricts data access at object level. Topic Instructions enforce authentication checks for sensitive queries. Rate limiting in Embedded Service Deployment prevents abuse. Never allow DML for unauthenticated users.
🎤 One-Line Answer
"Trust Layer (PII + injection), Guest User Profile FLS (data access), Topic Instructions (auth checks), Embedded Service rate limiting. Defense in depth — multiple layers, never just one."
Q5
What Experience Cloud templates are best suited for Agentforce deployment?
✅ Answer
Customer Service template (best for support + self-service + Knowledge integration), Help Center template (knowledge-heavy, FAQ-focused), Customer Account Portal (authenticated customers only, full account management). Choose based on use case — Customer Service is most versatile for Agentforce.
Template
Best For
Agentforce Fit
Customer Service
Support + self-service
⭐⭐⭐⭐⭐ Best overall
Help Center
Knowledge articles, FAQs
⭐⭐⭐⭐ Great for grounding
Customer Account Portal
Authenticated only
⭐⭐⭐⭐ Full data access
Partner Central
Partner management
⭐⭐⭐ Good for B2B
🎤 One-Line Answer
"Customer Service template is best for Agentforce deployment — supports both guest and authenticated users, integrates with Knowledge and Cases, most flexible for self-service use cases."