forcedotcom/sf-skills / skills/service-agentforce-contact-center-coordinate
service-agentforce-contact-center-coordinate
VerifiedCoordinates end-to-end setup of an Agentforce Contact Center voice channel: gathers country and phone-number-type selections, procures a chosen number, resolves its CommunicationChannelLine, verifies the number is live, and creates an active PstnVoice MessagingChannel. The user picks the routing model: Omni Queue (route to the contact center queue) or Omni Flow (route to an Agentforce agent, creating or reusing the agent plus its routing flows). Use when the user asks to set up an Agentforce Contact Center, provision a contact center phone number and voice channel together, or put an Agentforce agent on native voice. TRIGGER when the user says set up agentforce contact center, configure contact center voice, or create a voice channel with omni flow and an agentforce agent. DO NOT TRIGGER when only wiring an existing channel to an existing agent with no number to procure, or creating a non-voice messaging channel.
assets/report-template.md
View on GitHub# Agentforce Contact Center Setup Report
## Setup
| Item | Value |
|------|-------|
| Org alias | `<alias>` |
| Org confirmed | `sf org display --target-org <alias>` → `<instanceUrl>` |
| Country | `<US\|CA>` |
| Phone number type | `<10DLC\|Toll Free>` |
| Routing model | `<Omni Queue \| Omni Flow>` |
## Commands run
Each API call went through `sf api request rest` (no raw access token was extracted).
1. Fetch numbers — `GET /services/data/v68.0/connect/number-management/v1/numbers?countryCode=<country>&phoneNumberType=<type>`
2. Procure number — `POST /services/data/v68.0/connect/number-management/v1/number` with `country=<country>`, `phoneNumberType=<type>`
3. Resolve ChannelLine — SOQL: `<query used>`
4. Verify live status — Tooling API `CodeStatus`<, numberStateReconcile if not live>
5. Resolve queue by name — SOQL: `SELECT Id FROM Group WHERE Type='Queue' AND Name='<queue-name>'`
6. Create channel — `POST` MessagingChannel (`PstnVoice`, `ChannelLineId=<channel-line-id>`, `IsActive=true`)
**Omni Flow only** — additional steps (omit for Omni Queue):
7. Agentforce prerequisite — `scripts/check-agentforce-prereq.sh` → canonical Einstein Agent User `<agent-user>` <reused/provisioned>
8. Agent — created/reused `<agent-api-name>` (`<agent-label>`), status Active
9. RoutingFlows — deployed `<agent-api-name>_Voice_Omni_Flow` (Copilot) + `<agent-api-name>_Voice_Escalation` (QueueBased)
## Result
| Field | Value |
|-------|-------|
| Routing model | `<Omni Queue \| Omni Flow>` |
| Procured phone number | `<number>` |
| CommunicationChannelLine Id | `<channel-line-id>` |
| CommunicationChannelLine status | `<code-status>` |
| Queue resolved by name | `<queue-name>` → `<queue-id>` |
| Agentforce agent (Omni Flow) | `<agent-api-name>` (`<agent-label>`) — Active |
| Inbound FlowDefinition (Omni Flow) | `<flow-dev-name>` → `<300-id>` |
| MessagingChannel Id | `<channel-id>` |
| MessagingChannel DeveloperName | `<dev-name>` |
| MessagingChannel ChannelLineId | `<channel-line-id>` |
| MessagingChannel IsActive | `true` |
| MessagingChannel SessionHandlerId | `<queue-id \| 300-flowdefinition-id>` |
| MessagingChannel FallbackQueueId | `<queue-id (Omni Flow) \| null>` |
Fill the Omni Flow rows only when that path was taken; leave them out for Omni Queue.
## Outcome
<One line: SUCCESS — active PstnVoice channel `<channel-id>` routed to `<queue `<queue-name>` (Omni Queue) | agent `<agent-label>` via Omni Flow, fallback queue `<queue-name>`>`; OR the exact error encountered and the step it failed at.>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |