Agent skill · forcedotcom
service-omni-presence-status-deploy
Create the standard Available and Busy presence statuses needed for Omni-Channel routing. TRIGGER when users ask to deploy Omni presence statuses, configure agent availability, deploy Omni status metadata, create an Available status for Case, Incident, Messaging, or Voice, or add the standard Busy status. DO NOT TRIGGER for custom status designs, unsupported objects, or PresenceUserConfig capacity.
What it needs
About 3k tokens when loaded.
What this skill does
service-omni-presence-status-deploy Deploy the sObject-specific Available<X> ServicePresenceStatus bound to that sObject's ServiceChannel, and ensure a universal Busy status exists, in one atomic Metadata API deploy. Every Omni agent needs an "available for work" status carrying a channel (so incoming work routes) and an "off-work" status (so they can step away). A presence status binds to exactly one ServiceChannel by DeveloperName, so each routing target needs its own Available status. It pairs with service-omni-permission-set-assign, which grants agents access to the statuses this skill deploys, and is invoked once per routing target by service-omni-channel-setup-coordinate. Target sObject Available status Bound channel --- --- --- Case AvailableCase Cases Incident AvailableIncident Incidents MessagingSession AvailableMessaging sfdclivemessage VoiceCall AvailableVoice sfdcphone Busy is UI-defined, not metadata-defined. The Omni "Busy vs Online" option is not expressible via the Metadata API — a ServicePresenceStatus carries only <label> and <channels>, and a status with no channels is treated as busy. The conventional busy DeveloperName is simply Busy, and most orgs already have one, so this skill reuses an existing Busy and deploys the bundled asset only when none exists. A busy status is not required to receive work — the Available status carrying the channel is what routes it. Inputs org-alias (required). sobjecttype (optional, default Case). Preconditions and safety Target org authenticated via sf CLI (My Domain URL), Service Cloud license, sf CLI ≥ 2.139.6. Omni-Channel base settings enabled (service-omni-base-settings-configure) — otherwise the deploy fails with INVALIDTYPE. The target sObject's ServiceChannel exists (service-omni-service-channel-configure) — otherwise the deploy fails with Value '<channel>' is not valid. Incident requires the Incident Management feature enabled; MessagingSession requires Enhanced Messaging. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/service-omni-presence-status-deploy