Individual skill
service-agentforce-channel-configure
Wires an existing, active Agentforce agent to a channel by resolving a fallback queue, setting up inbound routing (either PATCH SessionHandlerId on the MessagingChannel, or an inbound RoutingFlow for Voice/Email), and optionally configuring outbound escalation. Use when the user wants to add a channel to an existing agent, connect an agent to a messaging or voice channel, route Voice or Email-to-Case to an Agentforce agent, or set up a fallback queue for an agent channel. Also applies to an existing Help Agent. The channel infrastructure must already exist — this skill adds routing. DO NOT TRIGGER when the agent does not yet exist or still needs Help Agent setup (use agentforce-generate or service-helpagent-coordinate), when setting up Email-to-Case with an agent end-to-end (use service-email-to-case-configure), when creating the MessagingChannel itself (use service-digital-engagement-channel-configure), or when creating an Embedded Service Deployment (use service-digital-engagement-deployment-configure).
skills/service-agentforce-channel-configure/SKILL.md
Source commit a8a18ce1e4ba12e69b4073eab98ce31bfbd8271e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,151
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- devops Derived category
- testing Derived category
- testing-browser Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 21,644 bytesSKILL.mdcore · 21,644 bytesSKILL.mdcore · 21,644 bytesSKILL.mdcore · 21,644 bytesSKILL.mdcore · 21,644 bytesSKILL.mdcore · 21,644 bytesSKILL.mdcore · 21,644 bytesSKILL.mdcore · 21,644 bytesassets/BotEmailDefinition.botEmailDefinition-meta.xmlasset · 2,156 bytesassets/email/unfiled$public/AgentforceForServiceEmailTemplate.emailasset · 780 bytesassets/email/unfiled$public/AgentforceForServiceEmailTemplate.email-meta.xmlasset · 1,492 bytesassets/mdapi-package.xmlasset · 1,122 bytesassets/settings-mdapi-package.xmlasset · 1,415 bytesreferences/agent-wiring.mddoc · 5,844 bytesreferences/botemaildefinition.mddoc · 8,668 bytesreferences/channel-branch-email.mddoc · 23,818 bytesreferences/channel-branch-voice.mddoc · 3,597 bytesreferences/channel-types.mddoc · 5,417 bytesreferences/live-traffic-gate.mddoc · 5,840 bytesreferences/queue-resolution.mddoc · 6,626 bytesreferences/routing-flow.mddoc · 17,489 bytesscripts/validate-botemaildefinition.pyruns · 4,927 bytesscripts/validate-emailtemplate.pyruns · 5,042 bytes
Read excerpt
# service-agentforce-channel-configure: Wire an Agentforce agent to a channel
Adds inbound routing between an existing channel and an existing Agentforce agent. The agent receives work items from the channel; a fallback queue handles overflow when the agent is unavailable.
This skill is generic — it works for any Agentforce agent, not just the Help Agent template.
## Scope
**In scope:**
- Resolving or creating a fallback queue with the correct `QueueSobject` SobjectType
- Branch A (Enhanced Chat / Enhanced Messaging): deploying `sessionHandlerType=AgentforceServiceAgent` + `sessionHandlerQueue` on an existing MessagingChannel, then binding `SessionHandlerId` via Data API PATCH
- Branch B (Voice): assumes the phone number and `PstnVoice` MessagingChannel already exist (provisioned by the caller, e.g. `service-helpagent-coordinate`), then creating an inbound RoutingFlow (`routingType: Copilot`) that routes to the agent with the queue as fallback
- Branch C (Email-to-Case): inbound routing via direct case-owner assignment or an Omni-Channel RoutingFlow, plus deploying a `BotEmailDefinition` (Email Configuration) that links the agent to Service Email and binding it to the routing address
- Optional outbound escalation: delegating the verified agent-to-human handoff contract to `service-agentforce-human-escalation-configure`