service-digital-engagement-channel-configure
Installation
SKILL.md
Configuring Enhanced Chat Channel
Creates MessagingChannel metadata XML for Salesforce Messaging for In-App and Web (MIAW). This skill produces a fully configured enhanced chat channel with routing, user verification, pre-chat, and automated response settings ready for Metadata API deployment.
Scope
- In scope: Creating
MessagingChannelmetadata with Omni-Channel Flow routing, Omni-Channel Queue routing, or Agentforce Service Agent (ASA) routing; enabling User Verification; configuring all channel settings (pre-chat forms, automated responses, consent keywords, file attachments, custom parameters) - Out of scope: Creating the referenced Omni-Channel Flow/Queue definitions (use
automation-flow-generate), creating the Embedded Service Deployment (separate metadata type — useservice-digital-engagement-deployment-configure), creating permission sets for messaging (useplatform-permission-set-generate), configuring the Embedded Service Code Snippet
Entry points and transport
- Delegated (
context.calledFrom == "service-onboarding"): use the suppliedvaluesfor parameter transport only. Before any mutation, verify that the target org and change description match an explicit user authorization obtained by the caller. Ifcontext.userAuthorizationRefis absent, prompt the user to confirm. Returnfailednaming any missing required key. Standalone (nocontext): ask for the Inputs below. - Shell safety: org alias and bot name must match
^[A-Za-z0-9_.@+-]+$before use in a command; otherwise stop and ask (delegated:failed). Pass the channel label single-quoted, escaping any'as'\''. - Transport A (primary): headless-360 MCP
dispatch/dispatch_readonlyon/headless/metadata. Transport B: thesfcommands below, only where a probe shows Transport A unavailable.
Details: references/onboarding_contract.md (§1 entry points, §2 transport, §3 pre-scan, §5 result).