forcedotcom/sf-skills / skills/service-helpagent-coordinate
service-helpagent-coordinate
FlaggedUse to set up, configure, ground, or go live with a Salesforce Help Agent (an Agentforce Service Agent in Service Cloud) via a guided four-checkpoint flow. Use whenever a user says any of: set up / create / build / add a help agent, service agent, or support chat agent; add or embed a chat widget on a website or Experience Cloud / LWR site; put a help agent on a channel (web chat, voice, phone, help portal); ground a help agent on Salesforce Knowledge; or wants an AI to answer customer questions, manage support cases, and escalate to a human. The right skill even when the request names only one part or references help-agent-spec.md or the Agentforce Quick Setup wizard. DO NOT TRIGGER when authoring a brand-new agent with no Help Agent lineage (use agentforce-generate), configuring OAuth/ECAs (use integration-connectivity-connected-app-configure), or only deploying metadata (use platform-metadata-deploy).
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 5.8 KB |
| SKILL.md | skill md | 28.5 KB |
| assets/help-agent-spec.md | markdown | 41.8 KB |
| references/agent-script.md | markdown | 45.4 KB |
| references/channel-voice.md | markdown | 3.6 KB |
| references/channel-web-chat.md | markdown | 19.9 KB |
| references/output-report-format.md | markdown | 16.4 KB |
references/channel-voice.md
View on GitHub# Channel branch — Voice
> **When to read this file.** Load it only when the user has selected **Voice** at Checkpoint 3 of `assets/help-agent-spec.md`. If they selected Web Chat, read `channel-web-chat.md` instead. If they selected Help Portal, delegate to the sibling skill `service-concierge-portal-generate` — do not inline portal steps here.
Voice wires the Help Agent to a `PstnVoice` MessagingChannel via an inbound RoutingFlow. This skill never calls the Number Management API itself — if no `PstnVoice` channel exists yet, it delegates number procurement to `service-agentforce-contact-center-coordinate`, which owns that end-to-end (fetch → procure → verify live → create the channel).
---
## Existing number path
Query existing channels:
```bash
sf data query --target-org $ORG --json \
--query "SELECT Id, DeveloperName, MasterLabel, MessagingPlatformKey, IsActive FROM MessagingChannel WHERE MessageType='PstnVoice' ORDER BY MasterLabel"
```
If any are returned, present them and let the user choose. Capture the channel's `DeveloperName` as `CHANNEL_DEV_NAME`, then continue to **Step 8 — Wire the channel to the agent**. Fallback queue resolution (including the `SobjectType='VoiceCall'` requirement) is owned by `service-agentforce-channel-configure` — do not resolve or create the queue here.
If none are returned, continue to **No existing number** below.
---
## No existing number — delegate provisioning
Ask the user (`AskUserQuestion`): **provision a new number now** (delegate to `service-agentforce-contact-center-coordinate`), or **provision manually in Setup → Feature Settings → Service → Communication Channels** and come back once a `PstnVoice` channel exists.
If they choose to provision now, delegate to `service-agentforce-contact-center-coordinate`, passing `$ORG`. Instruct it to run its full number-procurement flow through channel creation, but steer the routing-model choice (its Step 7) to **Omni Queue**, not Omni Flow — the Help Agent already exists and owns its own agent authoring; Omni Flow's agent/flow-authoring steps would create a second, redundant agent. `service-agentforce-channel-configure` Branch B (this skill's Step 8, below) rewires the created channel's `SessionHandlerId`/`FallbackQueueId` to the Help Agent regardless of which routing model created it, so Omni Queue is the correct, minimal choice here.
Once `service-agentforce-contact-center-coordinate` reports the created `PstnVoice` MessagingChannel, capture its `DeveloperName` as `CHANNEL_DEV_NAME` and continue to **Step 8 — Wire the channel to the agent**.
---
## Step 8 — Wire the channel to the agent
Delegate to `service-agentforce-channel-configure` Branch B. Pass:
- **Agent DeveloperName** — the Help Agent
- **Channel type** — Voice
- **Channel identifier** — `CHANNEL_DEV_NAME`
The delegated skill resolves and configures the fallback queue itself.
---
## Step 9 — Loop
Return to the Checkpoint 3 loop — offer the user the option to add another channel or proceed to go-live.
---
## Rules / constraints
| Rule | Rationale |
|---|---|
| This skill never calls the Number Management API itself | Delegate provisioning to `service-agentforce-contact-center-coordinate` — do not hand-roll fetch/procure/verify-live here |
| When delegating provisioning, steer its routing-model choice to Omni Queue | Omni Flow would author a second, redundant Agentforce agent; Branch B rewires the channel's routing to the Help Agent regardless of which model created it |
| Never resolve or create the fallback queue here | `service-agentforce-channel-configure` owns queue resolution end to end — resolving it twice can double-prompt the user |
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 |