Deploy Agentforce to Experience Cloud — Step by Step 2026
🤖 Free Agentforce Course 2026 — sfinterviewpro.com
🚀 Module 12 of 15
Deployment & Experience Cloud
Launch Agents to Production
Master production deployments. Experience Cloud portals. White-labeling & custom branding. Publishing agents to customers. Pre-launch checklist. Testing in sandbox. Real XYZ deployments. Security & performance considerations. Interview ready!
Sandbox
First!
White
Label
Prod
Ready
Zero
Downtime
📍 Course Progress — Module 12 of 15
✅M1
✅M2
✅M3
✅M4
✅M5
✅M6
✅M7
✅M8
✅M9
✅M10
✅M11
M12Deploy
M13Scale
M14Test
M15Done
🎯 What You’ll Master in This Module
Sandbox testing checklist. Pre-launch validation. Experience Cloud portal setup. White-labeling agents (branding, colors, logo, domain). Publishing to production. Change sets & migration. Monitoring & rollback. Real XYZ deployment workflow (ABC Pharma goes live). Performance considerations. Security checklist. Interview Q&A. By end, you can confidently launch agents to customers!
Part 1: Deployment Fundamentals
Sandbox vs Production. Planning strategy. Testing approach.
Agentforce Deployment = Moving agent from development (sandbox) to production (live customers). Never test in production. Always: Sandbox → UAT → Production. With rollback plan!
1
Sandbox vs. Production Environment
Know the difference
| Environment | Purpose | Data | Users | Deployment |
|---|---|---|---|---|
| Dev Sandbox | Development & testing | Copy of prod (read-only) | Dev team | Manual (build & test) |
| UAT Sandbox | User acceptance testing | Prod-like data | Business users | Via change set / deploy |
| Production | Live customers | Real, current data | All users (restricted) | Via change set, never direct |
⚠️ CRITICAL: Never Deploy Directly to Production
Always: Sandbox (build) → UAT (test with users) → Production (go live). Direct prod deployments risk breaking live agents, losing customer data, downtime. Always use Change Sets for audit trail!
Real XYZ Deployment Flow
Week 1: Build Sales Agent in Dev Sandbox
Week 2: Test thoroughly in Dev Sandbox (functionality, error handling)
Week 3: Deploy to UAT via Change Set
Week 4: Business users test in UAT (Rajesh, sales team validate)
Week 5: Get UAT sign-off
Week 6: Deploy to Production (Friday afternoon, team on call)
Post-deploy: Monitor for 24 hours, have rollback plan ready!
Week 2: Test thoroughly in Dev Sandbox (functionality, error handling)
Week 3: Deploy to UAT via Change Set
Week 4: Business users test in UAT (Rajesh, sales team validate)
Week 5: Get UAT sign-off
Week 6: Deploy to Production (Friday afternoon, team on call)
Post-deploy: Monitor for 24 hours, have rollback plan ready!
2
Change Sets: The Safe Deployment Method
Controlled metadata migration
// Change Set Deployment Process
STEP 1: Create Change Set in Sandbox
Setup > Outbound Change Sets > New
Name: “Sales Agent v1.0 — ABC Pharma”
Includes:
— Agentforce Agent (Sales_Agent)
— Agent Flow (Sales_Agent_Handoff_Flow)
— Standard Actions (6 actions)
— Custom Fields (customer_sentiment)
— Permission Sets (Agent_User_PS)
STEP 2: Upload Change Set
Click “Upload”
Target Org: Production
Change Set in Progress → Ready for Deployment
STEP 3: Validate in Target (Production)
Setup > Inbound Change Sets > Deployment
Click “Validate”
Check:
— No apex errors
— All dependencies present
— Code coverage > 75% (if code included)
If validation passes → green checkmark → ready to deploy!
STEP 4: Deploy to Production
Click “Deploy”
Deployment Starts → Monitor progress → Completion email
New agent “Sales_Agent” now live in production!
STEP 5: Post-Deployment Verification
— Test agent with real data
— Check all actions work
— Verify error handling
— Monitor logs for 24 hours
— Get customer feedback
ROLLBACK (if needed):
If critical issue found:
Setup > Inbound Change Sets > Find deployment
Click “Rollback” → Agent reverted to previous version
Investigate issue in sandbox → Retest → Re-deploy
✅ Change Set Benefits
– Audit trail (who deployed what, when)– Rollback capability (revert if issue)
– Validation before deploy (catch errors early)
– Zero-downtime deployment (background process)
– Dependencies tracked (ensures nothing breaks)
Part 2: Experience Cloud Portals & White-Labeling
Launching agents to customers. Custom branding. Portal setup.
Experience Cloud = Salesforce’s portal platform. Create branded customer/partner portals. Embed Agentforce agents. White-label (your logo, colors, domain). Customers interact with agents in familiar branded interface!
1
Setting Up Experience Cloud Portal with Agent
Step-by-step portal creation
Real XYZ: ABC Pharma Customer Portal with Sales Agent
Step 1: Create Experience Cloud Site
Setup > Experience Cloud > All Sites > New
Name: “ABC Pharma Customer Portal”
Template: Customer Service
Click “Create” → Portal initialized!
Step 2: Customize Branding
Portal Settings > Branding & Appearance
— Logo: Upload ABC_Pharma_Logo.png
— Header Color: #4C7C59 (ABC Pharma corporate teal)
— Primary Color: #E8A000 (corporate gold)
— Font: Plus Jakarta Sans (matches Agentforce)
— Favicon: Upload favicon.ico
— Footer: “© 2026 ABC Pharma Pvt Ltd. All rights reserved.”
Step 3: Add Agentforce Agent to Portal
Portal Home Page > Add Component > Agentforce
Select Agent: “Sales_Agent”
Settings:
— Agent Title: “Welcome! I’m ABC Pharma Sales Assistant”
— Position: Bottom-right chat bubble
— Auto-popup: Yes (on page load)
— Theme: Dark (matches portal)
Step 4: Configure Custom Domain
Portal Settings > Domain
From: experience.salesforce.com/s/123abc
To: customer.amipolymer.com (white-label domain)
Requires DNS CNAME record, SSL cert setup
Step 5: Publish Portal
Portal Status: Development → Live
Click “Publish” → Portal now live!
Customers access at: https://customer.amipolymer.com
See branded interface + Sales Agent!
Setup > Experience Cloud > All Sites > New
Name: “ABC Pharma Customer Portal”
Template: Customer Service
Click “Create” → Portal initialized!
Step 2: Customize Branding
Portal Settings > Branding & Appearance
— Logo: Upload ABC_Pharma_Logo.png
— Header Color: #4C7C59 (ABC Pharma corporate teal)
— Primary Color: #E8A000 (corporate gold)
— Font: Plus Jakarta Sans (matches Agentforce)
— Favicon: Upload favicon.ico
— Footer: “© 2026 ABC Pharma Pvt Ltd. All rights reserved.”
Step 3: Add Agentforce Agent to Portal
Portal Home Page > Add Component > Agentforce
Select Agent: “Sales_Agent”
Settings:
— Agent Title: “Welcome! I’m ABC Pharma Sales Assistant”
— Position: Bottom-right chat bubble
— Auto-popup: Yes (on page load)
— Theme: Dark (matches portal)
Step 4: Configure Custom Domain
Portal Settings > Domain
From: experience.salesforce.com/s/123abc
To: customer.amipolymer.com (white-label domain)
Requires DNS CNAME record, SSL cert setup
Step 5: Publish Portal
Portal Status: Development → Live
Click “Publish” → Portal now live!
Customers access at: https://customer.amipolymer.com
See branded interface + Sales Agent!
💡 White-Labeling: Complete Branding Control
Customers never see “Powered by Salesforce.” Portal is 100% your brand. Logo, colors, domain, messaging — all customized. Customers think they’re using ABC Pharma’s app, not Salesforce!
2
Access Controls & Permission Sets
Who can use the portal?
✅ Controlling Portal Access
- Guest Access: No login needed (anonymous customers)
- Community User: Customer logs in with email (Rajesh sees his own account)
- Permission Sets: Define what portal users can see & do (e.g., “View own orders,” “Submit support tickets”)
- Data Visibility: Customers see only their own data (ABC Pharma account + orders, not other customers’ data)
Real XYZ: Permission Set for Portal Users
Permission Set: “ABC_Pharma_Portal_User”
Assigned to: Community Users in ABC Pharma account
Permissions:
— View Account (own account only)
— View Opportunities (own opportunities)
— View Orders (own orders)
— Create Support Cases (submit new)
— Update Cases (own cases only)
— View Knowledge Articles (read-only)
— Use Agentforce Chat
Restrictions:
✋ Cannot delete anything
✋ Cannot see other customer data
✋ Cannot access admin settings
Result: Rajesh logs in → sees ABC Pharma account & his orders → chats with Sales Agent → creates support case. Secure & scoped!
Assigned to: Community Users in ABC Pharma account
Permissions:
— View Account (own account only)
— View Opportunities (own opportunities)
— View Orders (own orders)
— Create Support Cases (submit new)
— Update Cases (own cases only)
— View Knowledge Articles (read-only)
— Use Agentforce Chat
Restrictions:
✋ Cannot delete anything
✋ Cannot see other customer data
✋ Cannot access admin settings
Result: Rajesh logs in → sees ABC Pharma account & his orders → chats with Sales Agent → creates support case. Secure & scoped!
Part 3: Pre-Launch Checklist & Production Monitoring
Go-live readiness. Testing checklist. Production monitoring. Troubleshooting.
1
Pre-Launch Checklist: 30 Items to Verify
Don’t ship without checking!
✅ Pre-Launch Quality Gates
- Agent Functionality: Agent responds to all expected intents, actions execute correctly, error handling works
- Data Validation: Unified profile loads correctly, external API calls return data, no data corruption
- Actions Testing: All Standard, Flow, Apex, REST actions tested. Timeouts handled. Error messages user-friendly
- Security: No API keys hardcoded, Named Credentials used, permission sets correct, data access scoped
- Performance: Agent response time < 2 seconds, API calls < 5s, no timeout issues, concurrent users tested
- Mobile & Accessibility: Portal works on mobile, Agentforce chat responsive, WCAG accessibility standard met
- Integrations: ServiceNow, Jira, Slack, Data Cloud lookups all working. Test with real API creds
- Localization: If multi-language, all translations correct, date/number formats per region
- Brand Verification: Logo displays correctly, colors match brand guide, domain custom.amipolymer.com works
- Change Set Validation: Deployed to UAT sandbox, all validations passed, no apex errors
💡 Production Deployment Checklist (Day-of)
– Backup: Salesforce auto-backs up before deployment, but verify– Communication: Notify stakeholders “Deployment in progress, expect 10 min pause”
– Rollback Plan: Have roll-back button ready if critical issue
– Change Set Upload: Upload change set to production org
– Validate: Click “Validate” — wait for green check
– Deploy: Click “Deploy” — monitor deployment progress
– Test Immediately: Smoke test agent in production (open chat, send message, verify response)
– Monitor for 1 Hour: Watch debug logs, API call logs, error logs
– Stakeholder Notification: “Deployment successful! Agents live.”
2
Production Monitoring & Troubleshooting
Keeping agents healthy 24/7
| Monitoring Task | What to Check | Alert Threshold | Action |
|---|---|---|---|
| Agent Response Time | Average time to respond | > 5 seconds = slow | Check API calls, optimize flows |
| Error Rate | % of conversations with errors | > 5% = problem | Review logs, check dependencies |
| API Call Success | % of API calls succeeding (ServiceNow, Jira, etc) | < 95% = investigate | Check API availability, auth issues |
| Data Cloud Sync | Last sync timestamp | > 30 min old = stale | Manual sync or check data source |
| Concurrent Users | Users chatting simultaneously | Monitor capacity | Scale if approaching limit |
| System Health | Salesforce status page, service health | Any red status | Check Salesforce Twitter/status page |
🔍 Where to Monitor Logs in Production
Setup > Debug Logs → view real-time agent executionSetup > API Usage → REST API call count & errors
Setup > Event Monitoring → login, data export, agent usage
Setup > Apex Jobs → batch jobs, scheduled actions status
Einstein Analytics → Dashboard with agent metrics (response time, success rate, user count)
Interview Q&A: Deployment & Experience Cloud
Real interview questions. Expected answers. One-liners.
| Interview Question | Expected Answer |
|---|---|
| What’s the correct deployment strategy for Agentforce agents? | Always Sandbox → UAT → Production. Use Change Sets for audit trail. Never deploy directly to production. Have rollback plan ready. |
| What is a Change Set & why use it for deployment? | Metadata migration tool. Includes agent config, flows, actions, permissions. Provides audit trail, validation before deploy, and rollback capability. Safer than direct deployment. |
| Describe Experience Cloud in your own words. | Customer/partner portal platform built on Salesforce. Can embed agents, customize branding (logo, colors, domain), control access via permission sets. Customers interact with agents in branded interface. |
| What is white-labeling & how do you implement it? | Removing Salesforce branding, replacing with customer’s brand. Upload logo, set colors, use custom domain (CNAME). Customers see only your brand, not Salesforce. |
| How do you control what portal users can see? | Permission Sets. Define read/write access per object (Accounts, Orders, Cases). Data Visibility Rules ensure users see only own data. Restrict admin access. |
| What should you check before going live? | Agent response time < 2s, error rate < 5%, API call success > 95%, all actions tested, security validated, mobile-responsive, change set validated. |
| How do you monitor agents in production? | Setup > Debug Logs (real-time), API Usage (call count/errors), Event Monitoring (user activity), Einstein Analytics (dashboards). Alert on slow response time, high error rate, failed API calls. |
| What’s your rollback strategy if deployment fails? | Keep previous version. If critical issue in production, click “Rollback” in change set → agent reverts to prior version. Investigate issue in sandbox → fix → re-deploy. |
🎯 One-Liner for Interview
“Deploy agents via Change Sets (sandbox → UAT → production) to maintain audit trail & rollback capability. Host in Experience Cloud portals with white-labeling. Monitor production logs & metrics continuously.”
Key Points to Remember
Core deployment concepts.
- Sandbox First, Always: Never test in production. Always: Dev Sandbox → UAT Sandbox → Production
- Change Sets = Safe Deployment: Provides audit trail, validation, rollback. Better than direct deployment
- Validate Before Deploy: Run validation, check for apex errors, ensure no dependencies missing. Only deploy if validation passes
- Experience Cloud = Customer Portal: Branded interface for customers. Can embed agents. Full customization (logo, colors, domain)
- White-Labeling Removes Salesforce Branding: Custom domain, logo, colors. Customers see only your brand
- Permission Sets Control Access: Define what portal users can view/edit. Data Visibility ensures they see only own data
- Pre-Launch Checklist Is Non-Negotiable: Test functionality, security, performance, integrations, mobile, accessibility before going live
- Monitor Production Continuously: Watch response time, error rate, API success, sync health. Alert on anomalies. Have rollback ready
Knowledge Check: Deployment & Experience Cloud (5 Questions)
Q1: Why should you always deploy via Change Sets instead of directly to production?
Change Sets provide audit trail (who deployed what, when), validation before deploy (catch errors early), rollback capability (revert if issue), and zero-downtime deployment. Direct deployment risks breaking live agents.
Q2: What’s the correct deployment order?
Sandbox (build & test) → UAT (business users test) → Production (go live). Never skip UAT or deploy directly to production.
Q3: What is white-labeling in Experience Cloud?
Replacing Salesforce branding with customer’s brand. Upload logo, set colors, use custom domain (customer.amipolymer.com). Customers never see “Powered by Salesforce.”
Q4: How do you ensure portal users only see their own data?
Use Permission Sets to define access (e.g., “View own Account,” “View own Orders”). Combine with Data Visibility Rules. Restrict admin access.
Q5: Name 3 things to monitor in production after deploying an agent.
Agent response time (target < 2 seconds), error rate (target < 5%), API call success rate (target > 95%), Data Cloud sync freshness, concurrent user count.
☕ Enjoyed this article?
SF Interview Pro is 100% free and maintained by a Salesforce professional. No ads, no paywalls, and no signup required. If this guide helped you prepare for an interview, earn a certification, or grow your Salesforce career, consider buying me a coffee! ☕💜
🇮🇳 UPI (India)
Pay by QR
GPay · PhonePe · Paytm · BHIM
New interview questions every week
Follow for fresh Salesforce Q&A, free courses, and real interview experiences — straight from the trenches.
Follow Us ↗