forcedotcom/sf-skills / skills/service-de-channel-settings-configure
service-de-channel-settings-configure
VerifiedConfigure settings on an already-existing Enhanced `MessagingChannel` (any type — WhatsApp, Text/SMS, LINE, Apple, Facebook, EmbeddedMessaging), given its `{CHANNEL_ID}`. Covers five facets: consent (ConsentType + per-language keyword records), automated responses, messaging keywords, session-inactivity timeouts, and pre-chat parameters. Consent + a matching language-keyword record are required for activation's readiness check. TRIGGER when setting or changing settings on a channel that already exists (opt-out keyword, consent type, double opt-in confirmation, initial/help auto-responses, OptIn/OptOut keywords, session-inactivity timeout) — typically between insertion/routing and activation, or on a live channel. DO NOT TRIGGER for creating a new channel (`service-de-channel-create`), deploying a MIAW/EmbeddedMessaging channel from metadata XML (`service-digital-engagement-channel-configure`), setting routing (`service-de-channel-routing-configure`), or activating a channel (`service-de-channel-activate`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.1 KB |
| references/channel-settings-facets.md | markdown | 7.9 KB |
| references/gotchas.md | markdown | 10.8 KB |
| references/language-keywords.md | markdown | 5.7 KB |
| references/worked-examples.md | markdown | 6.2 KB |
references/worked-examples.md
View on GitHub# Worked examples: consent facet (`service-de-channel-settings-configure`)
Reference runs for the three ConsentType paths — all sub-steps of **Stage 2 (Facet 1 — Consent)** in the current skill (read state → choose ConsentType → collect prompts → write channel + keyword record), verified against **Stage 5 (verify)**. The step labels below describe that consent sub-flow, not separate top-level SKILL.md stages. The ExplicitOptIn channel-side write, the read model, and the WhatsApp restriction below were verified live on `messaging_sdb6c` 2026-08-13.
---
## Worked example: ImplicitOptIn (opt-out only)
Input:
- `{CHANNEL_ID}` = `0MjSG00000030wL0AQ` (Enhanced WhatsApp channel `DummyChannelForTesting`)
- `{LANGUAGE}` = `en_US`
The **Stage 1** channel read shows `PlatformType=Enhanced`, `ConsentType=ImplicitOptIn`, and the **Stage 2** keyword read finds one existing `MsgChannelLanguageKeyword` (`3OrSG0000002kUz0AI`, `MasterLanguage=en_US`) with:
```text
OptOutKeywords = unsubscribe_en_US,stopall_en_US,cancel_en_US,quit_en_US,stop_en_US,end_en_US
OptOutConfirmation = You've opted out of receiving messages from us, so we won't contact you again.
```
That record already satisfies the ImplicitOptIn readiness rule (`OptOutKeywords` + `OptOutConfirmation` both non-null), so the skill takes the **no-op path**:
```json
{"ok": true, "noop": true, "consentType": "ImplicitOptIn",
"languageKeywordIds": ["3OrSG0000002kUz0AI"],
"message": "Consent already configured and activation-ready"}
```
If instead there were **no** keyword record, the skill would create one:
```bash
sf data create record --sobject MsgChannelLanguageKeyword \
--values "MessagingChannelId=0MjSG00000030wL0AQ MasterLanguage=en_US \
OptOutKeywords=stop,unsubscribe,cancel OptOutConfirmation='You have been unsubscribed.'"
```
and report `Success — Consent configured — channel 0MjSG00000030wL0AQ is now ImplicitOptIn with an en_US keyword record. Activation-ready.`
---
## Worked example: ExplicitOptIn (channel-side write verified live)
Input:
- `{CHANNEL_ID}` = `0MjSG0000000D9V0AU` (Enhanced Facebook channel `FACEBOOK_null_101192609043587`)
- `{CONSENT_TYPE}` = `ExplicitOptIn`
- `{LANGUAGE}` = `en_US`
**Stage 1**: `PlatformType=Enhanced`, `ConsentType=ImplicitOptIn`, `OptInPrompt=null`. Continue.
**Stage 2 (Facet 1) — choose ConsentType**: ExplicitOptIn chosen. Facebook accepts it (unlike WhatsApp rich content — see below).
**Stage 2 — collect prompts**: `OptInPrompt` = `Reply YES to receive messages`.
**Stage 2 — channel PATCH** — verified live, note the single-quoting of the multi-word prompt:
```bash
$ sf data update record --sobject MessagingChannel --record-id 0MjSG0000000D9V0AU \
--values "ConsentType=ExplicitOptIn OptInPrompt='Reply YES to receive messages'"
# → {"id":"0MjSG0000000D9V0AU","success":true,"errors":[]}
```
Re-read confirmed `ConsentType=ExplicitOptIn`, `OptInPrompt=Reply YES to receive messages`.
**Stage 2 — keyword record** — the record must also carry `OptInKeywords` (plus the ImplicitOptIn opt-out fields). Create or update the `en_US` record:
```bash
sf data update record --sobject MsgChannelLanguageKeyword --record-id <3Or...> \
--values "OptInKeywords='yes,start,subscribe' OptInConfirmation='You are subscribed'"
```
(Live keyword shape confirmed on sdb6c: e.g. Facebook channel `0MjSG0000000Beb0AE` carries `OptInKeywords=yes,sure` — multiple opt-in keywords as a comma-separated string.)
**Stage 5 (verify)**: re-read channel + keyword record; `OptInPrompt` non-null on the channel and `OptInKeywords`+`OptOutKeywords`+`OptOutConfirmation` non-null on the keyword record → activation-ready.
**Stage 5 (report)**:
```json
{"ok": true, "consentType": "ExplicitOptIn", "channelFieldsSet": ["ConsentType","OptInPrompt"],
"languageKeywordId": "3Or...", "language": "en_US", "created": false, "activationReady": true}
```
*(The test channel was restored afterward to `ConsentType=ImplicitOptIn, OptInPrompt=null` — passing `OptInPrompt=''` nulls the field.)*
---
## Worked example: DoubleOptIn
Input:
- `{CHANNEL_ID}` = an Enhanced Text (SMS) channel
- `{CONSENT_TYPE}` = `DoubleOptIn`
**Stage 2 — collect prompts**: both `OptInPrompt` and `DoubleOptInPrompt`.
**Stage 2 — channel PATCH** — all three fields in one write:
```bash
sf data update record --sobject MessagingChannel --record-id '{CHANNEL_ID}' \
--values "ConsentType=DoubleOptIn OptInPrompt='Reply YES to subscribe' \
DoubleOptInPrompt='Reply CONFIRM to confirm your subscription' IsRequireDoubleOptIn=true"
```
**Stage 2 — keyword record** — needs `OptInKeywords`, `DoubleOptInKeywords`, `OptOutKeywords`, `OptOutConfirmation`:
```bash
sf data update record --sobject MsgChannelLanguageKeyword --record-id <3Or...> \
--values "OptInKeywords=yes,start DoubleOptInKeywords=confirm \
OptOutKeywords=stop,unsubscribe OptOutConfirmation='You have been unsubscribed.'"
```
(Live example on sdb6c: keyword record `3OrSG00000002rR0AQ` has both `OptInKeywords=yes` and `DoubleOptInKeywords=yes`, confirming DoubleOptIn uses both keyword fields.)
**Stage 5 (verify)** confirms `OptInPrompt` + `DoubleOptInPrompt` non-null on the channel and `OptInKeywords` + `DoubleOptInKeywords` + opt-out fields non-null on the keyword record.
---
## Worked example: WhatsApp rich-content rejects ExplicitOptIn (verified live)
Input:
- `{CHANNEL_ID}` = `0MjSG00000030wL0AQ` (Enhanced WhatsApp channel with rich content)
- User asks for `ExplicitOptIn`
**Stage 2 — channel PATCH** is rejected server-side:
```bash
$ sf data update record --sobject MessagingChannel --record-id 0MjSG00000030wL0AQ \
--values "ConsentType=ExplicitOptIn OptInPrompt='Reply YES to receive messages'"
# → INVALID_INPUT: Consent Type for WhatsApp Messaging Channel with rich content
# cannot be set to EXPLICIT_OPT_IN(db=1,api=ExplicitOptIn).
```
The skill surfaces this rather than retrying:
```json
{"ok": false, "kind": "channel-patch-failed",
"message": "Consent Type for WhatsApp Messaging Channel with rich content cannot be set to EXPLICIT_OPT_IN. WhatsApp rich-content channels support ImplicitOptIn only."}
```
User-facing: `Error: This WhatsApp channel has rich content and only supports ImplicitOptIn — the server rejected ExplicitOptIn. Configure opt-out keywords under ImplicitOptIn instead.`
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: 322k | 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 |