forcedotcom/sf-skills / plugins/builder/service-engagement/skills/service-digital-engagement-channel-configure
service-digital-engagement-channel-configure
VerifiedConfigures 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 19.5 KB |
| assets/messaging_channel_template.xml | config | 7.1 KB |
| examples/asa_agent_channel.xml | config | 2.7 KB |
| examples/auth_queue_channel.xml | config | 2.7 KB |
| examples/omni_flow_channel.xml | config | 3.0 KB |
| examples/omni_queue_channel.xml | config | 2.4 KB |
| examples/user_channel.xml | config | 2.5 KB |
| references/channel_settings.md | markdown | 24.2 KB |
| references/onboarding_contract.md | markdown | 9.1 KB |
| references/prechat_params.md | markdown | 674 B |
| references/recaptcha_handoff.md | markdown | 2.5 KB |
| references/routing_transitions.md | markdown | 5.5 KB |
| references/user_verification.md | markdown | 1.2 KB |
| scripts/check-api-version.shexecutable | script | 1.6 KB |
| scripts/normalize-channel-name.shexecutable | script | 868 B |
assets/messaging_channel_template.xml
View on GitHub<?xml version="1.0" encoding="UTF-8"?>
<MessagingChannel xmlns="http://soap.sforce.com/2006/04/metadata">
<!-- Automated Responses (optional, repeat per response) -->
<!-- Shape depends on type — see references/channel_settings.md "Automated Responses" -->
<!-- TextResponse shape: OptOutConfirmation, HelpResponse only -->
<!--
<automatedResponses>
<autoResponseContentType>TextResponse</autoResponseContentType>
<language>en_US</language>
<response>{RESPONSE_TEXT}</response>
<type>{OptOutConfirmation|HelpResponse}</type>
</automatedResponses>
-->
<!-- MessageDefinition shape: InitialResponse, AgentEngagedResponse, AgentEndEngagementResponse, EndUserInactiveResponse, EndUserIdleResponse, RerouteResponse, RoutingUnavailableResponse -->
<!-- messageDefinitionName must reference an existing ConversationMessageDefinition (build via conversation-message-definition-builder first) -->
<!-- Do NOT include language or response on this shape -->
<!-- Optional responseTimeoutInMins (4-30): only for EndUserIdleResponse / EndUserInactiveResponse -->
<!--
<automatedResponses>
<autoResponseContentType>MessageDefinition</autoResponseContentType>
<messageDefinitionName>{CONVERSATION_MESSAGE_DEFINITION_DEV_NAME}</messageDefinitionName>
<type>{InitialResponse|AgentEngagedResponse|AgentEndEngagementResponse|EndUserInactiveResponse|EndUserIdleResponse|RerouteResponse|RoutingUnavailableResponse}</type>
</automatedResponses>
-->
<!-- Standard Parameters (optional, repeat per parameter) -->
<!-- actionParameterMappings is optional — include when using Flow routing to map to flow input variables -->
<!--
<standardParameters>
<actionParameterMappings>
<actionParameterName>{FLOW_INPUT_VARIABLE_NAME}</actionParameterName>
</actionParameterMappings>
<parameterType>FirstName</parameterType>
</standardParameters>
<standardParameters>
<parameterType>LastName</parameterType>
</standardParameters>
<standardParameters>
<parameterType>Email</parameterType>
</standardParameters>
<standardParameters>
<parameterType>Subject</parameterType>
</standardParameters>
-->
<!-- Custom Parameters (optional, repeat per parameter) -->
<!-- actionParameterMappings is optional — include when using Flow routing to map to flow input variables -->
<!--
<customParameters>
<actionParameterMappings>
<actionParameterName>{FLOW_INPUT_VARIABLE_NAME}</actionParameterName>
</actionParameterMappings>
<externalParameterName>city</externalParameterName>
<masterLabel>City</masterLabel>
<maxLength>50</maxLength>
<name>city</name>
<parameterDataType>String</parameterDataType>
</customParameters>
-->
<!-- Embedded Configuration -->
<embeddedConfig>
<allowedFileTypes>{COMMA_SEPARATED_EXTENSIONS}</allowedFileTypes>
<!-- Keep exactly one expiry: anonymousUserJwtExpirationTime for UnAuth (default 360), verifiedUserJwtExpirationTime for Auth (60-240) -->
<anonymousUserJwtExpirationTime>{JWT_EXPIRATION_MINUTES}</anonymousUserJwtExpirationTime>
<!-- <verifiedUserJwtExpirationTime>{VERIFIED_JWT_EXPIRATION_MINUTES}</verifiedUserJwtExpirationTime> -->
<authMode>{UnAuth|Auth}</authMode>
<chatAbandonmentTimeout>{MINUTES}</chatAbandonmentTimeout>
<isAbandonedChatsEnabled>{true|false}</isAbandonedChatsEnabled>
<isAttachmentUploadEnabled>{true|false}</isAttachmentUploadEnabled>
<isEstimatedWaitTimeEnabled>{true|false}</isEstimatedWaitTimeEnabled>
<isFallbackMessageEnabled>{true|false}</isFallbackMessageEnabled>
<isFileAttachmentExtUnrestricted>{true|false}</isFileAttachmentExtUnrestricted>
<isSaveTranscriptEnabled>{true|false}</isSaveTranscriptEnabled>
<maxFileSize>{SIZE_IN_MB}</maxFileSize>
<!-- Messaging Authorizations (only when authMode is Auth; omit entirely for UnAuth) -->
<!--
<messagingAuthorizations>
<authIdentifier>{AUTH_IDENTIFIER}</authIdentifier>
<authorizationType>PublicKeyCertificateSet</authorizationType>
<enabled>{true|false}</enabled>
<publicKeyCertificateSetName>{KEYSET_NAME}</publicKeyCertificateSetName>
</messagingAuthorizations>
-->
</embeddedConfig>
<!-- Session Settings -->
<endUserIdleTimeOut>{IDLE_TIMEOUT_MINUTES}</endUserIdleTimeOut>
<!-- Session Inactivity (optional) — top-level siblings of embeddedConfig, not nested inside it -->
<!-- endUserIdleAction must be Inactivate, End, or InactivateAndEnd -->
<!--
<endUserIdleAction>{Inactivate|End|InactivateAndEnd}</endUserIdleAction>
<endInactiveSessionTimeOut>{MINUTES_AFTER_IDLE_ACTION}</endInactiveSessionTimeOut>
<isAgentMessageResetInactivityEnabled>{true|false}</isAgentMessageResetInactivityEnabled>
-->
<isEstimatedWaitTimeEnabled>{true|false}</isEstimatedWaitTimeEnabled>
<isQueuePositionEnabled>{true|false}</isQueuePositionEnabled>
<isSynchronousChatEnabled>{true|false}</isSynchronousChatEnabled>
<isVoiceModeEnabled>{true|false}</isVoiceModeEnabled>
<masterLabel>{CHANNEL_LABEL}</masterLabel>
<messagingChannelType>EmbeddedMessaging</messagingChannelType>
<!-- Messaging Keywords -->
<messagingKeywords>
<keyword>cancel</keyword>
<keyword>end</keyword>
<keyword>quit</keyword>
<keyword>stop</keyword>
<keyword>stopall</keyword>
<keyword>unsubscribe</keyword>
<keywordType>OptOut</keywordType>
<language>en_US</language>
</messagingKeywords>
<messagingKeywords>
<keyword>help</keyword>
<keywordType>Help</keywordType>
<language>en_US</language>
</messagingKeywords>
<!-- Routing: Queue-based -->
<!-- <sessionHandlerQueue>{QUEUE_NAME}</sessionHandlerQueue> -->
<!-- <sessionHandlerType>Queue</sessionHandlerType> -->
<!-- Routing: Flow-based (requires a fallback queue) -->
<!-- <sessionHandlerFlow>{FLOW_API_NAME}</sessionHandlerFlow> -->
<!-- <sessionHandlerQueue>{FALLBACK_QUEUE_NAME}</sessionHandlerQueue> -->
<!-- <sessionHandlerType>Flow</sessionHandlerType> -->
<!-- Routing: User (requires a routing config; no fallback queue) -->
<!-- <queueRoutingConfig>{QUEUE_ROUTING_CONFIG_NAME}</queueRoutingConfig> -->
<!-- <sessionHandlerType>User</sessionHandlerType> -->
<!-- <sessionHandlerUser>{USERNAME}</sessionHandlerUser> -->
<!-- Routing: Agentforce Service Agent (requires a fallback queue) -->
<!-- NOTE: sessionHandlerAsa is REQUIRED at v67 — deploy fails with "Missing required Agentforce Service Agent" if omitted. -->
<!-- The deploy binds SessionHandlerId automatically; verify it landed with a query (see SKILL.md step 15a). -->
<!-- <sessionHandlerAsa>{ASA_BOT_DEV_NAME}</sessionHandlerAsa> -->
<!-- <sessionHandlerQueue>{FALLBACK_QUEUE_NAME}</sessionHandlerQueue> -->
<!-- <sessionHandlerType>AgentforceServiceAgent</sessionHandlerType> -->
</MessagingChannel>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |