Agent skill · forcedotcom
service-omni-presence-user-config-deploy
Use to deploy an Omni PresenceUserConfig (presence configuration) as one whole-record Metadata write with the decline/ACW fields set consistently: Auto-Accept off, Decline on, Decline Reason on (with a PresenceDeclineReason deployed in the same package), and an After-Conversation-Work wrap-up timer. Agents are assigned by username. Idempotent via the Metadata API files[].state signal. Triggers: create presence configuration, enable decline + decline reason + ACW wrap-up timer for agents, assign presence config to users. Do not use for ServicePresenceStatus (separate skill), for permission-set access to statuses, or to set the channel-level ACW timer on a ServiceChannel.
What it needs
About 3k tokens when loaded.
What this skill does
service-omni-presence-user-config-deploy Deploy an Omni PresenceUserConfig (the "presence configuration" that governs how work is offered to agents) together with the PresenceDeclineReason it references, in one atomic Metadata API package. The decline / auto-accept / decline-reason / ACW fields have cross-field validators — enabling Decline requires Auto-Accept off, Decline Reason requires Decline on, and the ACW timer must be paired with its max time — so they can only be set correctly as a single whole-record write, not field-by-field. This skill encodes that consistent record and assigns it to the given agents. It runs after service-omni-agent-users-create / service-omni-presence-status-deploy and is invoked by service-omni-channel-setup-coordinate as a rep-experience step. Inputs org-alias (required). configdevelopername (optional, default OmniDemoPresenceConfig). agentusernamescsv (optional). Comma-separated Usernames (…@…) and/or 15/18-char User Ids (005…) to assign; Ids are resolved to usernames (metadata assigns by username). May also be set via AGENTUSERNAMESCSV. Empty → the config deploys with no user assignments. Env overrides: DECLINEREASONLABEL (default Training), DECLINEREASONDEVELOPERNAME (default derived from the label), CAPACITY (default 5, 1–100), ACWSECONDS (default 60, 10–3600), PRESENCESTATUSONDECLINE (optional ServicePresenceStatus DeveloperName). Preconditions and safety Target org authenticated via sf CLI, Service Cloud license, sf CLI ≥ 2.139.6. Omni-Channel base settings enabled (service-omni-base-settings-configure). Any PRESENCESTATUSONDECLINE must already exist (service-omni-presence-status-deploy). The three-way safetowrite production guard applies. Run deploy-and-report.sh materializes two components into a temp DX project and deploys them in one call: 1. PresenceDeclineReason:<reason> — the decline reason (label only). 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/service-omni-presence-user-config-deploy--18f762