Quick answer
A business-day SLA is different from a strict hour-based SLA. Define working days, time zone, holidays, and when the clock starts to avoid disputes.
Key takeaways
- Two business days is not always 48 hours.
- Time zone and office hours matter.
- Clear wording reduces customer confusion.
Why SLAs often use business days
Business-day SLAs are common where support teams operate mainly Monday to Friday. A promise to respond within two business days is different from a promise to respond within 48 hours.
Avoid ambiguity
Good SLA wording should explain what counts as a business day, what time zone applies, and whether public holidays are excluded.
Operational uses
- Estimating response deadlines
- Planning support queues
- Checking overdue work
- Explaining timelines to customers
- Avoiding weekend-related confusion
A simple calculator can help teams check dates quickly without building a custom spreadsheet.
Common SLA tiers for customer service
Most support teams map response targets to business-day tiers. Here’s how typical SLA levels translate into real-world deadlines:
| SLA tier | Typical target | Example (ticket Mon 10am) | Who uses it |
|---|---|---|---|
| Critical / Priority 1 | 4 business hours | Response by Mon 2pm | IT support, hosting platforms, mission-critical SaaS |
| High / Priority 2 | 8 business hours | Response by Tue 10am (if submitted at 2pm Mon) | Enterprise support, managed services |
| Standard / Priority 3 | 1 business day | Response by Tue 5pm | General customer service, e-commerce support |
| Non-urgent / Priority 4 | 2–3 business days | Response by Wed–Thu 5pm | Feature requests, billing queries, general enquiries |
| Low / Priority 5 | 5 business days | Response by the following Monday 5pm | Feedback forms, documentation requests |
Notice that hour-based SLAs (4h, 8h) use business hours, not clock hours. A 4-business-hour SLA on a ticket received at 3pm Friday has no meaningful response window until Monday morning, effectively making the deadline Monday 11am if business hours are 9am–5pm.
Worked example: ticket received Friday at 4pm
This is the scenario that causes the most confusion in SLA tracking. Let’s walk through it:
Scenario: A customer submits a support ticket on Friday at 4:00pm. The SLA promises a response within 1 business day. Business hours are 9am–5pm, Monday to Friday.
| Time | Event | Clock status |
|---|---|---|
| Friday 4:00pm | Ticket received | Clock starts (1 business hour remaining today) |
| Friday 5:00pm | Business hours end | 1 hour elapsed; 7 business hours remaining if the SLA is 8 business hours |
| Saturday–Sunday | Weekend | Clock paused — these are not business hours |
| Monday 9:00am | Business hours resume | Clock restarts; deadline depends on the SLA tier |
| Monday 5:00pm | 1 business day deadline met | Response must be sent by end of Monday |
The customer sees the response on Monday — three calendar days after they submitted the ticket. If you’d misread “1 business day” as “24 calendar hours,” you would have expected a response by Saturday 4pm and marked the ticket as overdue. This is why the business-day vs calendar-day distinction matters enormously in support workflows.
Now apply a 4-business-hour SLA to the same ticket. The clock ticks for 1 hour on Friday (4pm–5pm), then pauses for the weekend. On Monday at 9am, the clock resumes and the remaining 3 hours run until Monday 12:00pm — the deadline.
What “next business day” really means
“Next business day” is one of the most frequently used SLA phrases, but it contains hidden complexity:
- If a ticket arrives before the cut-off time (e.g., before 5pm on Monday), “next business day” means Tuesday.
- If a ticket arrives after the cut-off time (e.g., 5:01pm on Monday), it is treated as received on Tuesday. “Next business day” then means Wednesday.
- If a ticket arrives on Friday after the cut-off, it is treated as received on Monday. “Next business day” means Tuesday — a full four calendar days after the customer pressed send.
- If Monday is a bank holiday, the effective receipt date becomes Tuesday, and “next business day” means Wednesday.
The lesson: always document both the business-day SLA and the cut-off policy in your terms. “We respond within 1 business day” is ambiguous without knowing whether Friday 4:30pm counts as Friday or Monday for clock-start purposes.
Excel and Sheets formulas for SLA dashboards
If you track SLAs in a spreadsheet, these formulas can help automate business-day deadline calculations:
| What you need | Excel formula | Google Sheets formula |
|---|---|---|
| Add N business days to a date | =WORKDAY(A2, N, holidays_range) | =WORKDAY(A2, N, holidays_range) |
| Count business days between two dates | =NETWORKDAYS(A2, B2, holidays_range) | =NETWORKDAYS(A2, B2, holidays_range) |
| Days remaining until SLA deadline | =NETWORKDAYS(TODAY(), C2, holidays_range) | =NETWORKDAYS(TODAY(), C2, holidays_range) |
| Flag overdue items | =IF(AND(TODAY()>C2, C2<>""), "Overdue", "On track") | =IF(AND(TODAY()>C2, C2<>""), "Overdue", "On track") |
| Next business day after a date | =WORKDAY(A2, 1, holidays_range) | =WORKDAY(A2, 1, holidays_range) |
Practical tip: Maintain a separate sheet tab named “Holidays” listing all UK bank holidays for the current and next year. Reference this range in every WORKDAY and NETWORKDAYS formula. Update it annually when the GOV.UK bank holiday list is published. For hourly SLAs, combine WORKDAY with time arithmetic: =WORKDAY(A2, INT((B2+TIME(8,0,0))/8), holidays_range) + MOD((B2+TIME(8,0,0))/8,1)*8/24 gives you a rough business-hours-aware deadline, though for mission-critical SLA tracking, a dedicated tool or script is safer.
Frequently asked questions
Is a 1-business-day SLA the same as a 24-hour SLA?
No. A 24-hour SLA runs continuously from the moment the ticket is received — a ticket at 4pm Friday has a deadline of 4pm Saturday. A 1-business-day SLA runs only during business hours — the same ticket has a deadline of Monday 5pm (or earlier, depending on cut-off). 24-hour SLAs favour 24/7 operations; business-day SLAs suit office-hours teams.
How do I handle SLAs when we operate across multiple time zones?
Define the SLA in terms of a single reference time zone (e.g., GMT/BST for UK-based teams). State it clearly: “Business days are Monday to Friday, 9am–5pm GMT, excluding UK bank holidays.” For global teams, you may need to define business hours per region or use a “follow-the-sun” model where the clock never pauses.
Can I customise WORKDAY to skip different weekend days?
Yes. Excel’s WORKDAY.INTL function lets you specify which days count as weekends. For example, =WORKDAY.INTL(A2, 5, "0000011", holidays_range) treats only Saturday and Sunday as weekends (the default). Use "0000001" to treat only Sunday as a weekend, which is useful for Middle Eastern markets where Friday–Saturday are the weekend.
Useful official resources
These sources are directly relevant to the date, public holiday, delivery, SLA, or complaint-handling topic covered in this article.
Related video searches
If you prefer a video explanation, these searches can help you find relevant explainers on YouTube.
Use the calculator as a quick reference for customer service deadline planning.
Loading comments...