Salesforce Decode
Salesforcedecode
Back to questions
Headless 360Architect (Hardest)agentforcemulti-channelwidgetsarchitecture

Coordinate multi-channel Agentforce widgets across web, mobile, and Slack

Real World Scenario

Customers start support in mobile app, continue on website, and internal ops monitor same threads in Slack alerting channel—inconsistent agent configs cause conflicting answers.

Expected Answer

• Single agent topic and action source of truth with channel-specific presentation adapters only • Unified session identity using authenticated customer ID linking cross-channel conversations • Channel capability matrix disabling unsupported actions per surface e.g. file upload on Slack vs mobile • Consistent escalation paths routing to same Omni queues regardless of originating widget • Central analytics dashboard segmenting containment by channel without duplicating agent logic • Feature flag coordinated rollouts across web SDK, mobile SDK, and Slack integration • Governance process preventing channel teams from forking prompt templates independently

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Direct answer: Single agent topic and action source of truth with channel-specific presentation adapters only Also consider: Unified session identity using authenticated customer ID linking cross-channel conversations In practice: Channel capability matrix disabling unsupported actions per surface e.g. file upload on Slack vs mobile Document the decision in an ADR and align with enterprise standards.

Architect Perspective

Multi-channel Agentforce is one brain, many faces—forked configs per channel recreate omnichannel support chaos agents were meant to fix.