Skip to content

forcedotcom/sf-skills / skills/service-agentforce-contact-center-coordinate

service-agentforce-contact-center-coordinate

Verified

Coordinates 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.

references/agentforce-prerequisite.md

View on GitHub
# Prerequisite — Einstein Setup + Agentforce Agents toggle

The **Omni Flow** path (routing a voice channel to an Agentforce agent) requires **Einstein** and **Agentforce / Einstein Service Agents to be enabled** in the org. When they're on, the org can provide an **Einstein Agent User** — the `--agent-user` that `sf agent generate agent-spec` and publish require. When they're off, or when no Agentforce Service Agent User license is available, agent authoring/publish fails with a licensing, Agent API access, or "couldn't find the default agent user" error.

This prerequisite does **not** apply to the Omni Queue path.

## Enable it (org admin, one time)

In the target org, in the Setup UI:

1. **Setup → Einstein Setup** → turn **Einstein** **On** (this must be enabled before the Agentforce toggle appears/works).
2. **Setup → Einstein → Agentforce (Agents)** (a.k.a. *Einstein Agent* / *Agentforce Service Agents*) → turn the setting **On**.
3. Confirm an **Einstein Agent User** exists (Setup → Users), or let `scripts/check-agentforce-prereq.sh` provision one with `sf org create agent-user`.

Enablement is an org preference, not part of this skill's scope — the operator flips it in Setup.

## Preflight check

```bash
scripts/check-agentforce-prereq.sh <alias>
```

- **Exit 0** — prints a user whose profile is exactly `Einstein Agent User`. Use it as `--agent-user` for `sf agent generate agent-spec`. The script reuses an existing user, or provisions one with `sf org create agent-user`.
- **Exit 3** — no canonical Einstein Agent User could be found or provisioned; the toggle is likely off or the org has no available Agentforce Service Agent User license.

The profile-name check is intentionally strict. Do not use a broad fallback such as `Profile.Name LIKE '%Agent%'` or `Profile.Name LIKE '%Bot%'`: those users can make spec generation/validation appear healthy, then fail `sf agent publish authoring-bundle` with Agent API access or default-agent-user errors.

## When the toggle is off

1. **Prompt the user** to enable it or free/provision an Agentforce Service Agent User license, then re-run the check.
2. If it still can't be confirmed — or agent/flow creation later fails on licensing — stop and report unless the user explicitly accepts the Omni Queue fallback.
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: 472kUpdated Claude CodeCodexUnverifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall