PranavNagrecha/AwesomeSalesforceSkills / skills/admin/entitlements-and-milestones
entitlements-and-milestones
UnverifiedUse this skill to design, configure, and troubleshoot Salesforce Entitlement Management on Cases: entitlement processes, milestone definitions, recurrence types, milestone actions (success/warning/violation), business hours assignment, and entitlement templates. Covers the deployable EntitlementProcess / MilestoneType / EntitlementTemplate / EntitlementSettings metadata, signed timeLength time triggers, recurrenceType semantics, process versioning, and how a milestone actually completes. Trigger keywords: entitlement process, milestone, SLA timer, milestone tracker, first response SLA, time trigger, recursChained, CaseMilestone, EntitlementId, SlaProcess, stopped clock. NOT for SLA milestones on Field Service work orders — use admin/fsl-sla-configuration-requirements. NOT for time-based case escalation rules — use admin/escalation-rules. NOT for the business-hours calendar itself — use admin/business-hours-and-holidays.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 29.4 KB |
| references/examples.md | markdown | 7.5 KB |
| references/gotchas.md | markdown | 16.1 KB |
| references/llm-anti-patterns.md | markdown | 9.9 KB |
| references/metadata-examples.md | markdown | 33.8 KB |
| references/well-architected.md | markdown | 9.2 KB |
| scripts/check_entitlements_and_milestones.pyexecutable | script | 23.3 KB |
| templates/entitlements-and-milestones-template.md | markdown | 5.3 KB |
templates/entitlements-and-milestones-template.md
View on GitHub# Entitlements and Milestones — Work Template
Use this template when designing or configuring Salesforce Entitlement Management for an org.
## Scope
**Skill:** `entitlements-and-milestones`
**Request summary:** (fill in what the user asked for — e.g., "configure 3-tier SLA entitlements for Acme Corp with email alerts at 75% and 100% elapsed")
---
## Context Gathered
Answer these questions before starting any configuration:
- **Entitlement Management enabled?** Yes / No — (verify in Setup > Entitlement Settings)
- **Business Hours objects configured?** List names and coverage windows (e.g., "24/7 Platinum", "M–F 8am–5pm Standard")
- **Support tiers in scope:** (e.g., Platinum, Gold, Standard)
- **SLA commitments per tier:**
| Tier | First Response | Resolution | Coverage |
|---|---|---|---|
| | | | |
- **Intake channels creating cases:** Email-to-Case / Web-to-Case / API / UI (mark all that apply)
- **Products & Price Books in use for support contracts?** Yes / No
- **Lightning Experience or Classic?** (affects entitlement template product attachment)
- **Existing entitlement records on accounts?** Yes / No / Partial
- **`enableEntitlementVersioning` on?** Yes / No — (must be on *before* the first versioned process)
- **`enableMilestoneStoppedTime` on?** Yes / No — (must be on *before* go-live to explain stopped cases)
- **Does anything set `Case.IsStopped`?** Yes / No — if yes, who, and under what policy?
---
## Entitlement Process Design
Fill in one block per support tier:
### Tier: _______________
- **Process name:** _______________
- **`versionMaster`:** _______________ (identical across every version of this process)
- **`versionNumber`:** _______________ **`isVersionDefault`:** Yes / No
- **`SObjectType`:** Case / Work Order
- **`entryStartDateField`:** SlaStartDate / CreatedDate / ClosedDate / LastModifiedDate / StopStartDate
- **Business hours (process level):** _______________
- **Start condition:** Case Created / Status Change / (other: _______)
- **Exit condition:** Case Closed / (other: _______)
#### Milestones
Record the deployable values, not the percentages. `minutesToComplete` is always minutes;
`timeLength` is a signed offset from the target with its own unit (negative = warning,
positive = violation). Re-derive every `timeLength` whenever `minutesToComplete` changes.
| Milestone Name (must match a MilestoneType) | `minutesToComplete` | `recurrenceType` | `businessHours` override | `useCriteriaStartTime` | Warning `timeLength` / unit | Violation `timeLength` / unit | `successActions` |
|---|---|---|---|---|---|---|---|
| First Response | | `none` | | `false` | | `1` Minutes | Stamp First_Response_Met__c |
| Resolution | | `none` | | | `1` Minutes | Stamp Resolution_Met__c |
**Milestone completion — who writes `CaseMilestone.CompletionDate`?**
| Milestone | Completion mechanism | Owner |
|---|---|---|
| First Response | Completion criteria the platform can satisfy / Apex / Flow | |
| Resolution | | |
---
## Entitlement Template Plan (if applicable)
- **Template name:** _______________
- **Process referenced:** _______________
- **Business hours referenced:** _______________
- **Duration (days):** _______________
- **Creation mechanism:** Classic product attachment / Lightning Record-Triggered Flow
- **Flow name (if Lightning):** _______________
- **Flow trigger:** OpportunityLineItem insert (Opportunity.StageName = Closed Won) / Order activation / (other: _______)
---
## Entitlement Lookup Automation
- **Flow name:** _______________
- **Trigger:** Case Before Save (Create)
- **Logic:** Query Entitlement WHERE AccountId = Case.AccountId AND Status = Active, LIMIT 1; set Case.EntitlementId
- **Fallback for no-account cases:** (default entitlement name: _______)
---
## Approach
- Which pattern from SKILL.md applies?
- [ ] Multi-tier SLA process with progressive warning actions
- [ ] Entitlement templates for automatic entitlement creation
- [ ] Independent recurrence for ongoing response SLA
- [ ] Other: _______________
- Reason for choice: _______________
---
## Review Checklist
- [ ] Entitlement Management is enabled in Setup
- [ ] Business Hours objects are active and correctly scoped (24/7 vs. business hours per tier)
- [ ] One entitlement process created per support tier
- [ ] Each process has at least one warning action per milestone (not only violation actions)
- [ ] Recurrence type confirmed correct for each milestone
- [ ] Entitlement and Milestone Tracker related lists/components added to Case page layouts
- [ ] Before-Save Flow populates Case.EntitlementId on all automated case creation channels
- [ ] Entitlement template creation mechanism confirmed (Flow for Lightning, Classic UI for Classic)
- [ ] Milestone timer behavior tested in sandbox with shortened time limit
- [ ] Process versioning strategy documented for future SLA term changes
- [ ] Every `timeLength` re-derived after the last change to `minutesToComplete`
- [ ] Exactly one file per `versionMaster` has `isVersionDefault` true
- [ ] `python3 skills/admin/entitlements-and-milestones/scripts/check_entitlements_and_milestones.py --manifest-dir <dir>` reports no ERROR (exit 0), and no `W6` — a `W6` means the tree has no BusinessHours settings file, so the calendar names were never checked
---
## Notes
Record any deviations from the standard pattern and the reason:
- _______________
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |