Book a. free discovery call with HelloMavens.

Kerry Proksel
AI Officer, Co-Founder & Managing Partner, HelloMavens
How to Set Up SLAs in Salesforce Service Cloud in 5 Steps
Set up SLAs in Salesforce Service Cloud with SLA policies, milestones and Agentforce. Apply them to every case, warn before a breach and track AI agents too.

Your AI agent answers in seconds. Your SLA still starts the clock when a human opens the case.
How do you set up SLAs in Salesforce Service Cloud when AI agents handle part of the work? Build one SLA policy per customer tier, apply it to every case automatically, including cases an Agentforce agent hands off, and let Agentforce send the routine updates that keep the clock on track. Then track people and agents on one dashboard so leaders see risk before the customer does.
Salesforce rebuilt this in 2026. Simplified SLA Setup puts it all in one view, and Agentic Milestones let Agentforce send first responses and status updates for you. Plan on 2 to 3 weeks, mostly agreeing on promises and handoff rules.
Key takeaways
Start the clock when the customer asks, not when a person picks it up. Every channel, including AI agent handoffs, gets an SLA on arrival.
Let Agentforce handle routine SLA updates. Your people should spend their time solving cases, not writing "still working on it."
Measure your AI agent like a team member. Track what it resolves, when it hands off and whether handed-off cases still meet the SLA.
What do SLA policies, milestones and entitlements do now?
Three pieces work together:
SLA policy (formerly the entitlement process): the timeline a case must follow, like first response and resolution.
Milestone: one time-based step in that timeline, like "first response within 2 hours." Milestones can now be marked as agentic, so Agentforce handles the communication.
Entitlement: the link between a policy and the customer, through their account, contact, asset or service contract.
Before you start (what you need)
Admin access to Service Cloud, with Entitlement Management on
Agentforce for Service, with an Agentforce Service Agent live or planned on at least one channel
Your current promises, from contracts, support tiers or your website
Case history (nice to have): recent response and resolution times help you set realistic targets, but you can start without them
A service leader to own the targets, the escalation path and the AI handoff rules
How do you set up SLAs in Salesforce Service Cloud?
Step 1: Decide what the customer is promised, and who keeps the promise
Build a simple grid: customer tiers down the side, case types across the top, and a first response and resolution time in each box. Then add one more column: who handles it first. Password resets and order status can go to the AI agent. A critical outage for a premium customer goes to a person right away.
If you have case history, use it to check that each target is realistic. If you don't, start with your best estimate and adjust after the first month.
Pro tip: Start with two milestones per policy, first response and resolution. Add more once the team trusts the clock.
Step 2: Build SLA policies and apply them to every case automatically
In Setup, open Entitlement Settings and turn on Simplified SLA Setup. In SLA Policies, create one policy per tier, set business hours and add your milestones. Then use Application Rules to attach the right policy based on case fields like origin, tier or type. No custom Flow or trigger needed.
Include every way a case can start: email, web, phone, messaging and cases created when an Agentforce agent escalates to a person. The customer has already been waiting. The clock should know that.
This is where we've seen the biggest change. At one client, customers emailed several inboxes to get a faster answer. We replaced them with one guided front door that answered common questions on the spot and created one case, with one SLA by customer and case type, when a person was needed. More than 30% of the old volume turned out to be duplicates, and the team finally had response metrics. Today, an Agentforce Service Agent can be that front door. We wrote more about the shift in Case Chaos: Why Inboxes and Queues Can't Keep Up.
Watch out for: Activating too early. Once a policy is active, you can't change its milestone actions, and the simplified setup doesn't keep old versions. Test in a sandbox first.
Step 3: Let Agentforce send the first response and status updates
Many SLA misses are just the "still working on it" messages nobody had time to send.
With Agentic Milestones (beta in Summer '26), you mark a milestone in an SLA policy as agentic, and Agentforce drafts and sends the first response and periodic status updates based on how the case is moving. You set the tone and content in Prompt Builder.
The Agentforce Service Agent goes further on routine requests: it answers from your Knowledge articles, resolves what it can and escalates to a person with the conversation attached. Fewer cases reach your team, and the ones that do arrive with context.
Watch out for: Updates that say nothing. Write the prompt so each update says what changed and what happens next.
Step 4: Warn and escalate before the breach
Milestones track time, but on their own they don't tell anyone anything. Add milestone actions:
Warning at 75% of the time: alert the owner, or run a Flow that flags the case for help. For tough cases, agentic Slack swarming (open beta) can open a channel, pull in the right experts and share the case context.
Violation at the deadline: raise the priority so Omni-Channel routes it ahead of routine work, and alert the manager.
Success when it's met: update a field or send data to another system.
Service Rep Assistant reads the case and the customer's sentiment and suggests a plan to the rep who picks it up. And set rule-based milestone pauses (Spring '26) so the clock stops on "Waiting on Customer."
Our take: the warning matters more than the violation. A violation tells you what already went wrong. A warning gives your team, human or AI, time to fix it.
Step 5: Track people and agents on one dashboard
Agents need the clock on the case. Leaders need it across the whole team, including the AI.
On the case: add the Milestones component so reps see time remaining and what's at risk.
For leaders: use the Case Milestones report type for SLA compliance by tier, cases near violation and violations by team and case type. The Command Center adds live customer sentiment and AI agent insights.
For your AI agent: track how many requests it resolves, how often it escalates and whether escalated cases still meet the SLA. Agent Health Monitoring and Agent Optimizer show where the agent is struggling and what to fix.
Pro tip: Put "near violation" at the top left. Leaders should see today's risk before last month's score.
How do you know your SLAs are working?
Check these 30 days after launch:
Every case has an SLA, including AI agent handoffs. A report of open cases with a blank entitlement comes back empty.
First response compliance is near 100% on milestones Agentforce handles.
Escalated cases meet the same SLA as cases that went straight to a person.
Common mistakes
One SLA for every customer. Fix: set clocks by tier and case type from Step 1.
Starting the clock at handoff. Fix: apply SLAs to agent-created cases with Application Rules, so the clock starts the moment the case exists.
Treating the AI agent as outside the SLA. Fix: measure its resolutions and handoffs on the same dashboard.
Only violation actions. Fix: add a warning to every milestone.
The clock runs while you wait on the customer. Fix: add pause rules for waiting statuses.
Thinking about Agentforce for service? Start with our Agentforce FAQ: 10 Questions Leaders Ask Before Turning On AI Agents.
๐ Not sure your service promises match what your team and your AI agents can deliver? Book a free Case Management Readiness consult. We'll look at how cases come in today, where the clock gets lost and where Agentforce can take work off your team.
FAQ
Can Agentforce help meet SLAs in Salesforce? Yes. With Agentic Milestones, Agentforce sends first responses and status updates on the milestones you choose. The Agentforce Service Agent also resolves routine requests and hands off the rest with context.
Do cases escalated by an AI agent get an SLA? They should. Use Application Rules in SLA Policies to apply the right policy based on case origin, tier and type, so a case an agent escalates gets its clock the moment it's created.
Can Salesforce pause an SLA when we're waiting on the customer? Yes. Reps can stop the clock on a case, and since Spring '26 you can set rules that pause milestones automatically based on conditions like case status. The timer also pauses outside business hours.
