Milestone Actions
Milestone Actions are the time-based automated actions Salesforce fires at predefined points in a Case's milestone lifecycle.
Definition
Milestone Actions are the time-based automated actions Salesforce fires at predefined points in a Case's milestone lifecycle. Each Milestone (First Response, Resolution, Escalation) has associated actions that run before the milestone target time, when it is reached, or after it has been violated. The actions are flows, email alerts, field updates, outbound messages, or task creation. Together they turn a passive SLA target into active operational signal: send the rep a warning 30 minutes before First Response is due, escalate to a manager if Resolution is missed, fire a custom flow when a milestone completes.
Milestone Actions live on the Entitlement Process metadata, configured under Setup, Service, Entitlement Processes, in the Milestones section. Each milestone has three action types: Success Actions (fire when the milestone is completed in time), Warning Actions (fire at a configurable time before the target), and Violation Actions (fire when the target time elapses without completion). The trio is what makes SLA enforcement actually enforceable; without actions, milestones are just decorative date fields on the Case.
How Milestone Actions turn passive SLA targets into active operational signal
Success, Warning, and Violation: the three action types
Each Milestone supports three action sets. Success Actions fire when the milestone target is met (case First Response sent before the 1-hour SLA). Warning Actions fire at a configurable offset before the target (15 minutes before the SLA breaches). Violation Actions fire after the target elapses without completion. Each set can contain multiple actions: email the rep, email the manager, update a custom field, fire a flow, create a task, send an outbound message.
Time-based triggering and the timer engine
Milestone Actions are scheduled by Salesforce''s timer engine when the case starts the Entitlement Process. The timer accounts for business hours configured on the Entitlement (24x7, weekdays 9-5, custom). When a milestone is completed, pending Warning and Violation actions for that milestone are cancelled. When the target time elapses, the platform fires Violation actions. The timer engine is what makes Milestone Actions reliable across timezones, business hours, and case-state transitions.
Action types in detail
Email Alerts are the most common Milestone Action. Field Updates change Case fields like Priority or Owner. Tasks create work items for users or queues. Outbound Messages POST to external SLA-tracking systems. Flow actions (since Spring 2022) invoke an autolaunched Flow, opening up arbitrary business logic. The flow-action option is the most powerful; everything else is available via flow plus a single starter Action.
Common SLA Action patterns
Warning at 75% of target: email the rep "your First Response is due in 15 minutes." Violation at target: escalate the case to a supervisor queue and email the customer with an apology. Success: log an SLA-met flag on the case for reporting. The pattern reflects mature service operations; warnings give reps a chance to act, violations trigger recovery workflows, successes get measured.
Business Hours and the timer
The Entitlement defines Business Hours: 24x7, standard 9-5, custom multi-shift. Milestone timers only count business hours, not real-world hours. A case opened Friday at 5pm with a 4-business-hour First Response milestone does not fire Violation until Monday at 10am (assuming 9-5 business hours). This is the right operational model for most service teams but surprises customers who assume the timer is wall-clock-based. Configure Business Hours carefully; they drive every milestone calculation.
Reporting and the MilestoneComplianceState field
The CaseMilestone object holds every milestone instance per case, with fields including TargetDate, CompletionDate, ElapsedTimeInMins, and MilestoneComplianceState (Compliant, Violated). Build reports on MilestoneComplianceState to see SLA compliance trends. Filter by milestone type to see which milestones violate most often. This is the data layer that supports SLA compliance dashboards.
Migration to Flow-based actions
Salesforce ships the Send Custom Notification flow action, the Submit for Approval flow action, and other recently added flow actions that can replace simpler Milestone Action types. Modern service deployments often migrate from per-action Email Alerts to a single flow action that runs richer logic. The legacy action types still work; flow is the path forward for complex Milestone Action workflows.
Configuring Milestone Actions on an Entitlement Process
Milestone Actions configure inside an Entitlement Process. The pattern: define the milestone, set its target time and trigger criteria, then attach Success, Warning, and Violation actions.
- Open the Entitlement Process
Setup, Service Setup, Entitlement Processes. Open an existing process or create a new one. Inside the process, the Milestones section lists each milestone the cases on this process must hit.
- Define the milestone
For each Milestone, configure name (First Response, Resolution, Escalation), Order, MilestoneType (which defines the field that flips to mark completion), TargetDate criteria, and StartDate criteria. Save before adding actions.
- Add Success Actions
From the Milestone detail, click Add Time-Dependent Action under Success Actions. Pick the action type: Email Alert, Field Update, Outbound Message, Task, Flow. Configure the action and save.
- Add Warning and Violation Actions
Same pattern. For Warning, set the offset (-15 minutes, -75% of target time). For Violation, the action fires at the target time. Most production deployments configure multiple actions per type (email rep, email manager, update field).
- Test on a sample case
Create a test case linked to an Entitlement that uses this process. Verify the milestone timer starts, the Warning fires at the right offset, the Violation fires on time, and the Success fires when the milestone is completed.
Success (on completion), Warning (offset before target), Violation (at or after target). Each set supports multiple actions.
Email Alert, Field Update, Outbound Message, Task, Flow. Flow is the most flexible; legacy types are simpler for specific common cases.
Configurable in minutes or as a percentage of target time. Common patterns: 15 minutes before, 25% of target remaining, 50% of target remaining.
Defined on the Entitlement, applied to milestone timers. 24x7 or business-hour-aware. Affects all action timing.
- Milestone timers respect Business Hours, not wall-clock. A 4-hour milestone over a weekend does not violate until the next business day.
- Completing a milestone cancels pending Warning and Violation actions for that milestone. The platform handles this automatically.
- Action limits apply per Entitlement Process. Too many actions per milestone can hit governor limits during peak case volume.
- Field Updates fired by Milestone Actions can recursively trigger flows on the Case. Audit downstream automation for unintended loops.
- Legacy action types (Workflow Email Alert, Workflow Field Update) are still supported but feature-frozen. New work should default to Flow actions.
Trust & references
Cross-checked against the following references.
- Milestone Actions OverviewSalesforce Help
- Milestones in Entitlement ProcessesSalesforce Help
Straight from the source - Salesforce's reference material on Milestone Actions.
- Create an Entitlement ProcessSalesforce Help
- Business HoursSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What are Milestone Actions?
Q2. What are the three action types?
Q3. Why configure milestone actions?
Discussion
Loading discussion…