Salesforce Support SLAs
What a good Salesforce support SLA actually specifies: response vs resolution, priority definitions, escalation paths and the numbers you should hold any provider to.
The framework
Most disputes about managed services come down to two things being undefined: what counts as urgent, and whether "response" means an auto-reply or a human working the issue. A strong SLA closes both gaps.
Response is when a qualified human engages and confirms ownership. Resolution is when the fix or workaround is live. Any provider quoting only one of the two is hiding something ask for both, per priority level.
Each priority level needs concrete examples: P1 as a revenue-blocker (org down, logins failing, forecast pipeline broken), P2 as degraded operations (broken automation, permission errors), P3 as standard requests. Examples stop the "everything is urgent" argument.
A named escalation contact with a time bound: if a P1 misses its response target, it escalates automatically to a senior architect not into the same queue.
| Priority | Typical definition | Good response target | Good resolution target |
|---|---|---|---|
| P1 Critical | Revenue-blocker: outage, login failures, broken forecast pipeline | Same day 4 business hours is the standard for office-hours support | Workaround same day; fix within 1-2 business days |
| P2 High | Degraded: broken automation, permission errors blocking a team | Next business day | Within 3 business days |
| P3 Standard | Requests: reports, fields, layouts, small enhancements | Within 2-3 business days | Agreed sprint or release |
Benchmarks
Use these ranges when you compare providers or when you benchmark your incumbent at renewal. Watch for the asterisks.
Office-hours retainers commonly quote 4-8 business hours for critical issues. Anything vaguer than a named number of hours "best efforts", "as soon as possible" is not an SLA.
Check the timezone and the definition. UK 9:00-17:30 Monday-Friday is typical; 24/7 critical cover costs materially more and is rarely needed unless your org serves customers around the clock.
Mature agreements include remedies for repeated misses typically a credit against the next month. If a provider refuses any remedy clause, weight that in your evaluation.
A monthly service report showing volumes, SLA attainment per priority, and trend commentary should be included not an upsell. It is also your evidence pack at renewal time.
Standard changes deployed within an agreed release cadence (weekly or fortnightly) with sandbox-first testing. Emergency changes for P1s bypass the calendar with documented approval.
Providers cannot SLA Salesforce's own platform uptime do not accept blame for platform outages, and do not let a provider hide behind them either. The SLA should carve this out explicitly.
Checklist
A qualified engineer acknowledging and taking ownership not an auto-reply from a ticketing system.
You want both numbers for each of P1/P2/P3, in writing, in the contract.
Match them to when your revenue teams actually work including US hours if you run transatlantic GTM.
A named senior contact with an automatic trigger, not a "please reply to this thread" process.
Coverage plans for leave and a team-based model rather than a single named admin.
Per-priority attainment in a monthly report, included in the retainer.
Some remedy mechanism credits, a free month, or an exit right for sustained underperformance.
Explicit carve-outs both ways: providers are not liable for platform outages, and must still communicate and work around them.
Major projects, new product builds and migrations are usually out of scope make sure the boundary is written down.
Prudentia's standard
Every Prudentia support retainer carries these commitments as standard they are the same numbers we publish on our managed services and support retainer pages.
| Priority | Response | Resolution target |
|---|---|---|
| P1 Critical | Within 4 business hours | Workaround same day, fix within 1-2 business days |
| P2 High | Next business day | Within 3 business days |
| P3 Standard | Within 3 business days | Agreed sprint or release |
Book a discovery call and we will walk through the SLA framework line by line then put it in the contract.
Book Discovery Call