AgentforceAdvancedauthenticationidentitysecurity
Design authentication flows for guest vs logged-in agent users
Real World Scenario
Guest web chat users request order status while logged-in portal users expect account-level actions without re-verification.
Expected Answer
• Leverage authenticated messaging sessions tied to Experience Cloud identity
• OTP or order-number + email verification for guests before PII disclosure
• Progressive trust: more actions unlocked after stronger authentication
• Session binding to prevent order lookup with guessed numbers
• Clear UX messaging on why verification is required
• Audit failed auth attempts for fraud patterns
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Leverage authenticated messaging sessions tied to Experience Cloud identity Also consider: OTP or order-number + email verification for guests before PII disclosure In practice: Progressive trust: more actions unlocked after stronger authentication Optimize for scale and operational observability.
Architect Perspective
Authentication is part of agent UX design—architect flows before action catalog, not after incidents.