forcedotcom/sf-skills / skills/service-itsm-agentic-setup-incident-management
service-itsm-agentic-setup-incident-management
VerifiedOrchestrator for Incident Management setup in Service Cloud ITSM: presents the features with live org status, and configures each — Incident preferences, Incident persona PSG assignment, Priority Matrix, SLA & Milestones, Incident dashboards, Email-to-Incident, Major Incident Management (approval group + MIM preferences), Broadcast Communications, Manage Incidents with AI, Service Management Privilege (privilege escalation), and audit tracking. Use for: set up or configure incident management, a walkthrough, what incident features can I configure; the incident preference toggles (default field validations, auto-close child incidents, auto-triage, assign with Einstein, restrict assigned group, rich text descriptions); assigning the Incident Fulfiller or Incident Manager persona PSG. DO NOT TRIGGER for: the master on/off switch alone (use the IncidentMgmt SOR), the Priority Matrix, SLA, or field history tracking alone, the Major Incident Manager PSG, creating/editing PSGs, or Problem/Change/Case Management.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 21.1 KB |
| examples/output-templates.md | markdown | 8.1 KB |
| references/audit-tracking.md | markdown | 3.3 KB |
| references/broadcast-communications.md | markdown | 1.9 KB |
| references/email-to-incident.md | markdown | 1.8 KB |
| references/incident-dashboards.md | markdown | 2.2 KB |
| references/incident-persona-psg.md | markdown | 2.9 KB |
| references/incident-preferences.md | markdown | 3.1 KB |
| references/major-incident-management.md | markdown | 2.9 KB |
| references/manage-incidents-with-ai.md | markdown | 3.2 KB |
| references/priority-matrix.md | markdown | 2.8 KB |
| references/service-mgmt-privilege.md | markdown | 2.9 KB |
| references/sla-milestones.md | markdown | 9.0 KB |
| references/status-checks.md | markdown | 22.4 KB |
references/email-to-incident.md
View on GitHub# Feature: Email-to-Incident (delegated to the `EmailToIncident` SOR)
How the orchestrator runs the **Email-to-Incident** feature, which turns incoming email into Incidents. The
`EmailToIncident` SOR's own steps and guidance decide *how*; the orchestrator runs them itself under its
**SOR hand-off protocol** and owns every user-facing gate. This file adds what is specific to
Email-to-Incident.
1. `discover` the SOR by intent (e.g. "email to incident settings routing address") and `describe` the id
`discover` returns (`EmailToIncident`).
2. **Settings.** Read them (`get-email-to-incident-setting`) and ask which to change. Turning on
Email-to-Incident itself (`enableEmailToIncident`) **can't be undone** — say so before asking. The save
(`save-email-to-incident-setting`) replaces the whole settings map: send back every field the read
returned (the set differs by release), changing only what the user chose, and on releases that have
them, the draft-email, sender-error-notification, and signature settings each need Email-to-Incident on.
Validate any choice-list value against the SOR's value-set reads. Confirm the full before → after
change, save, and read back with `verify-save-setting`.
3. **Routing addresses — only if the user wants them.** List the existing addresses
(`get-all-routing-addresses`) and the assignable queues (`get-incident-queue-ids`, the only source for
the assignee), then create or update one with the user's routing name, email address, and default
Urgency and Impact (the org's picklist values). An update replaces the whole row, so send every field.
Read each change back with its `verify-*-routing-address` step. A delete is **irreversible** — confirm
it explicitly. Re-sending an address's verification email sends a real email: do it only on an explicit
request.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |