Skip to content

PranavNagrecha/AwesomeSalesforceSkills / skills/admin/fsl-scheduling-policies

fsl-scheduling-policies

Verified

Use this skill to create, configure, or tune Field Service Lightning scheduling policies — including work rules (pass/fail filters) and service objectives (weighted ranking criteria). Covers the four default policies, custom policy design, work rule type selection, and objective weighting strategy. NOT for running or tuning the Optimizer itself — use admin/fsl-scheduling-optimization-design. NOT for resource skills and preferences — use admin/fsl-resource-management. NOT for resource capacity records — use admin/fsl-capacity-planning.

templates/fsl-scheduling-policies-template.md

View on GitHub
# FSL Scheduling Policies — Work Template

Use this template when configuring or revising a Field Service Lightning scheduling policy.

## Scope

**Skill:** `fsl-scheduling-policies`

**Request summary:** (describe the scheduling problem or configuration task the user asked for)

## Context Gathered

Record the answers to the Before Starting questions from SKILL.md here before proceeding.

- **Field Service enabled?** Yes / No — verified in Setup > Field Service Settings
- **Managed package installed?** Yes / No — verified in Setup > Installed Packages
- **Optimizer in use?** Salesforce Optimizer / Dispatcher Console / Both
- **Current active policy:** (name of the policy currently applied to relevant territories)
- **Primary business priority:** Customer satisfaction / Travel efficiency / SLA compliance / Overtime control
- **Skills/certifications in use on work orders?** Yes / No — (list if yes)
- **Territory boundary enforcement required?** Hard Boundary / Soft / None

## Policy Design

**Policy name:** (descriptive name reflecting use case — not a default policy name)

**Cloned from:** Customer First / High Intensity / Soft Boundaries / Emergency / Built from scratch

**Use case:** (one sentence describing when this policy applies)

### Work Rules

| Work Rule Name | Type | Required? | Notes |
|---|---|---|---|
| Service Resource Availability | Service Resource Availability | MANDATORY | Always include |
| (add rows as needed) | | | |

**Checklist:**
- [ ] Service Resource Availability is present
- [ ] Match Skills or Match Required Skills is present (if work types use skills)
- [ ] Territory boundary rule (Hard Boundary or Match Territory) is present if required
- [ ] Maximum Appointments is present if daily dispatch cap is needed
- [ ] Match Time Slot is present if customer preferred windows must be respected

### Service Objectives

| Objective | Weight (%) | Justification |
|---|---|---|
| ASAP | | |
| Minimize Travel | | |
| Minimize Overtime | | |
| Preferred Resource | | |
| Skill Level | | |
| **Total** | **100%** | Must sum to 100% |

## Policy Assignment

**Assigned to territories:**
- [ ] (territory name)
- [ ] (territory name)

**Applied via automation (if appointment-level override):**
- [ ] Flow rule: (describe trigger condition)
- [ ] Apex logic: (describe trigger condition)
- [ ] No automation — territory-level default only

## Validation Checklist

Copy and complete before marking the policy ready for production.

- [ ] Policy is a custom clone — the four default policies (Customer First, High Intensity, Soft Boundaries, Emergency) are unmodified
- [ ] Service Resource Availability work rule is present
- [ ] Service objective weights sum to 100%
- [ ] Policy has been tested by scheduling a representative test appointment
- [ ] Candidate ranking matches expected business priority (reviewed in Dispatcher Console or optimizer results)
- [ ] Yellow triangle rate post-deployment is acceptable (reviewed after initial live traffic)
- [ ] Policy name is descriptive and does not duplicate a default policy name

## Test Results

**Test appointment details:**
- Work Order: (Id or description)
- Territory: (territory name)
- Required skills: (list)
- Scheduled date/time: (expected window)

**Scheduling result:**
- Candidates surfaced: (number)
- Top-ranked candidate: (name or role)
- Work rules passed: (list)
- Work rules violated: (list)
- Yellow triangles shown: Yes / No

## Notes

Record any deviations from the standard pattern, edge cases encountered, or open questions.

- (note)
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 323kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall