Agent skill · forcedotcom
service-digital-engagement-channel-configure
Configures and deploys enhanced chat Messaging Channels for Messaging for In-App and Web (MIAW). Use when the user needs to create, deploy, and activate a messaging channel configured with Omni-Channel Flow, Omni-Channel Queue, User, or Agentforce Service Agent routing. Generates MessagingChannel metadata, deploys it to the target org, and activates the channel with User Verification, pre-chat forms, automated responses, consent settings, and all customizable channel options via Metadata API. TRIGGER when the user mentions messaging channel, MIAW, enhanced chat, in-app messaging, web messaging setup, or references a .messagingChannel-meta.xml file. DO NOT TRIGGER when the user is configuring legacy Live Agent chat, Embedded Service deployments without messaging, or standard Omni-Channel routing rules without a messaging channel.
What it needs
About 11k tokens when loaded.
What this skill does
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 MessagingChannel metadata 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 — use service-digital-engagement-deployment-configure), creating permission sets for messaging (use platform-permission-set-generate), configuring the Embedded Service Code Snippet --- Clarifying Questions Before generating, ask the user if not already clear: What is the channel name / label? (used for masterLabel and file name) What routing type? (Omni-Channel Flow, Omni-Channel Queue, User, or Agentforce Service Agent) What is the routing target? (Flow API name, Queue developer name, User ID, or ASA bot name) For Flow, User, or ASA routing: What is the fallback queue name? Should User Verification be enabled? (defaults to true per this skill) Are there pre-chat form fields required? If so, which fields and types? --- Required Inputs Gather or infer before proceeding: Channel name: Used for masterLabel and the file name (<Name>.messagingChannel-meta.xml) Routing type: One of Queue, Flow, User, or AgentforceServiceAgent Routing target: The developer name of the queue, flow, user, or ASA bot Fallback queue (Flow, User, and ASA): The developer name of the fallback queue for escalation User verification: Whether to require JWT-based identity verification (default: true) Defaults unless specified: messagingChan …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/service-digital-engagement-channel-configure--93d260