PranavNagrecha/AwesomeSalesforceSkills / skills/admin/fsl-sla-configuration-requirements
fsl-sla-configuration-requirements
VerifiedUse this skill to configure SLA enforcement for Salesforce Field Service (FSL) using Work Order entitlement processes: designing entitlement processes of type Work Order, defining FSL milestones (response time, on-site arrival, resolution), wiring milestone actions, and aligning Business Hours with service territory Operating Hours. NOT for Case SLAs and Case entitlement processes — use admin/entitlements-and-milestones. NOT for defining the SLA tier table and escalation matrix — use architect/sla-design-and-escalation-matrix.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 19.0 KB |
| references/examples.md | markdown | 4.8 KB |
| references/gotchas.md | markdown | 6.0 KB |
| references/llm-anti-patterns.md | markdown | 7.0 KB |
| references/well-architected.md | markdown | 5.6 KB |
| scripts/check_fsl_sla_configuration_requirements.pyexecutable | script | 9.7 KB |
| templates/fsl-sla-configuration-requirements-template.md | markdown | 4.4 KB |
templates/fsl-sla-configuration-requirements-template.md
View on GitHub# FSL SLA Configuration Requirements — Work Template
Use this template when designing or configuring Salesforce Field Service SLA enforcement using Work Order entitlement processes.
## Scope
**Skill:** `fsl-sla-configuration-requirements`
**Request summary:** (fill in what the user asked for — e.g., "configure 2-hour on-site response SLA for metro territory")
---
## Context Gathered
Answer these before configuring anything:
- **FSL enabled?** Yes / No
- **Entitlement Management enabled?** Yes / No (Setup > Entitlement Settings)
- **Service Territories defined?** Yes / No — list them:
- Territory 1: _________________ | Operating Hours: _________________
- Territory 2: _________________ | Operating Hours: _________________
- **Business Hours records available?** Yes / No — list them:
- BH Record 1: _________________ (windows: _________________)
- BH Record 2: _________________ (windows: _________________)
- **SLA commitments per tier:**
| Tier / Territory | Initial Response | On-Site Arrival | Resolution | Measured In |
|---|---|---|---|---|
| | | | | Business Hours / Calendar |
| | | | | Business Hours / Calendar |
- **Work Order completion status values:** _________________ (e.g., "Completed", "Cannot Complete")
- **Existing entitlement processes?** Yes / No — type (Case / Work Order): _________________
---
## Process Model Design
Fill in one row per entitlement process required:
| Process Name | Type | Business Hours Record | Milestones (Name / Time Limit / Recurrence) |
|---|---|---|---|
| | Work Order | | |
| | Work Order | | |
---
## Milestone Action Design
For each milestone, specify:
| Process | Milestone | Warning 1 (% / action) | Warning 2 (% / action) | Violation (action) | Success (action) |
|---|---|---|---|---|---|
| | Initial Response | 50% / email agent | 75% / email manager | 100% / email VP + field update | Stamp SLA_Met__c |
| | On-Site Arrival | | | | |
| | Resolution | | | | |
---
## Automation Plan
- [ ] **Entitlement Assignment Flow** — Record-Triggered Flow on Work Order (create) that reads ServiceTerritoryId and sets EntitlementId
- Territory → Entitlement mapping: _________________ → _________________
- [ ] **Milestone Completion Flow** — Record-Triggered Flow on Work Order (update) when Status = completion value
- Completion status values: _________________
- Logic: Get WorkOrderMilestone where WOId = this WO AND CompletionDate = null → Update CompletionDate = Now
---
## Layout Checklist
- [ ] WorkOrderMilestone related list added to Work Order page layout
- [ ] Columns customized to include: Milestone Name, TargetDate, CompletionDate, IsViolated, Status
- [ ] Entitlements related list added to Work Order page layout
- [ ] Entitlements related list added to Account page layout
---
## Business Hours / Operating Hours Alignment
Confirm alignment per territory before go-live:
| Territory | Operating Hours | Entitlement Process | Process Business Hours | Aligned? |
|---|---|---|---|---|
| | | | | Yes / No |
| | | | | Yes / No |
---
## Test Plan
Before go-live, test in sandbox:
1. Create a Work Order in a sandbox org with a matching entitlement.
2. Set one milestone time limit to 1 minute.
3. Advance Work Order to a completion status before 1 minute elapses.
4. Verify: `WorkOrderMilestone.CompletionDate` is set and success action fired.
5. Repeat with Work Order advanced after 1 minute to verify violation action fires.
6. Verify warning actions fire at 50% and 75% elapsed time.
---
## Review Checklist
Copy from SKILL.md — tick as complete:
- [ ] Entitlement processes are of type Work Order (not Case)
- [ ] Business Hours records assigned at the process level for each SLA tier
- [ ] Business Hours and Operating Hours are aligned per service territory
- [ ] Each process has at least one warning action before violation
- [ ] Flow populates EntitlementId on Work Orders at creation from Service Territory
- [ ] Flow sets CompletionDate on WorkOrderMilestone records on Work Order completion
- [ ] WorkOrderMilestone related list includes TargetDate, CompletionDate, and IsViolated
- [ ] Tested in sandbox with shortened milestone time limit
- [ ] No Case entitlement processes applied to Work Orders
---
## Notes
Record deviations from the standard pattern and the reason:
- _(e.g., "Using Apex instead of Flow for completion because conditional milestone logic based on WOLI completion — see apex/entitlement-apex-hooks skill")_
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |