service-de-channel-settings-configure
Configuring Channel Settings
What this skill does
Configures settings on an already-existing Enhanced MessagingChannel (identified by {CHANNEL_ID}), for any message type. It groups five facets; you only run the ones the caller asks for.
| # | Facet | Write surface | Applies to |
|---|---|---|---|
| 1 | Consent — ConsentType + OptInPrompt/DoubleOptInPrompt on the channel, plus per-language MsgChannelLanguageKeyword records |
Data/SObjects API (sf data update/create record) |
all Enhanced types |
| 2 | Automated responses — <automatedResponses> (initial, agent-engaged/-ended, opt-in prompt/confirmation, help, opt-out, inactive/idle) |
Metadata API deploy | all Enhanced types |
| 3 | Messaging keywords — <messagingKeywords> (OptIn/OptOut/Help keyword groups per language) |
Metadata API deploy | all Enhanced types |
| 4 | Session inactivity — endUserIdleTimeOut, endUserIdleAction, endInactiveSessionTimeOut, isAgentMessageResetInactivityEnabled |
Metadata API deploy | MIAW-only (reset-flag also Apple/Facebook) |
| 5 | Pre-chat parameters — <customParameters> / <standardParameters> |
Metadata API deploy | MIAW pre-chat only (rare) |
This skill is mixed-surface. Consent (facet 1) is written with the Data API on the live record. Facets 2–5 live only in the channel's metadata and are configured by retrieving the channel's .messagingChannel-meta.xml, editing it, and deploying it back. Verified live on sdb6 (2026-09): every Data/Connect/Tooling read of the facet-2–5 fields fails INVALID_TYPE/"No such column" — they are Metadata-API-only.
Per-type applicability is verified, not assumed (from a live retrieve of real channels of each type). Facets 2 and 3 are genuinely type-agnostic. Facet 4's four timeout fields appear only on MIAW; only isAgentMessageResetInactivityEnabled extends to Apple/Facebook, and SMS/WhatsApp/LINE carry no inactivity fields at all. Facet 5 appears only on MIAW channels that use pre-chat. Scope per-type accordingly — do not deploy a facet a type doesn't support.