Updated: May 2, 2026
How SaaS Contracts Handle the "Support During Business Hours" Clause
The "support during business hours" clause is one of the more often misread parts of a SaaS subscription agreement. The phrase looks simple, but the interaction with response-time SLAs, time zones, holidays, and priority tiers determines whether your vendor actually meets the support commitment you think you are paying for.
The standard structure
A typical SaaS support clause has three parts:
- Coverage hours: when support staff are available to respond.
- Response SLA: how quickly the vendor commits to acknowledging a ticket once submitted.
- Resolution SLA: how quickly the vendor commits to resolving the underlying issue (often softer than response).
Coverage hours are usually defined as "business hours, Monday through Friday, excluding [vendor's local] public holidays" with a specific time range like 9 AM to 5 PM, 8 AM to 6 PM, or 24 hours. Response and resolution SLAs are tied to coverage hours: the clock runs during coverage hours and pauses outside them.
A standard mid-tier SaaS contract might read:
Vendor will provide support during business hours, defined as 9 AM to 6 PM Eastern Time, Monday through Friday, excluding US federal holidays. Support response time for P3 (Medium) issues is 4 business hours. Support response time for P1 (Critical) issues is 1 hour, available 24 hours a day, 7 days a week.
The P1 commitment runs continuously; the P3 commitment runs only during business hours.
Time zone interpretation
The default rule is that "business hours" means the vendor's business hours in the vendor's primary support time zone. A US-based SaaS company default to Eastern Time even if their support team is in Texas or California, because Eastern is the conventional reference. UK vendors default to London time. Australian vendors default to Sydney time.
For multinational customers, this creates a coverage gap. A London customer of a US vendor with 9 AM to 6 PM Eastern coverage has effective coverage from 2 PM to 11 PM London time. A submitted ticket at 8 AM London time waits until 2 PM London (9 AM ET) for the response clock to start.
If you need overlap with your own business hours, three options:
Negotiate explicit coverage: Ask for a coverage exhibit that specifies time-zone overlap with your operations. This costs more but is achievable for enterprise contracts.
Use a follow-the-sun vendor: Larger SaaS vendors offer follow-the-sun as a premium tier. The trade-off is handoffs between regional teams.
Self-service for off-hours: Many vendors offer documentation, community forums, and AI chat for off-hours self-service. The SLA does not apply, but the basic question may resolve without an agent.
Follow-the-sun coverage
Follow-the-sun models stitch together regional teams to provide continuous clock-time coverage. A typical structure:
| Region | Hours covered (UTC) | Typical team location |
|---|---|---|
| APAC | 22:00 to 08:00 | Manila, Bangalore, Sydney |
| EMEA | 06:00 to 16:00 | Dublin, Lisbon, Cape Town |
| Americas | 13:00 to 24:00 | Austin, Toronto, San Jose |
The overlaps (06:00-08:00 UTC and 13:00-16:00 UTC) are where regional handoffs occur. Tickets in flight transition to the next team, with shift-change notes documented in the ticket itself.
For the customer, follow-the-sun means a P2 ticket submitted at 2:00 AM Singapore time (6:00 PM Eastern the prior day) gets immediate APAC response rather than waiting until US morning. The trade-off is that the same ticket may pass through three or four agents over a 24-hour resolution period, with the inevitable context loss between handoffs.
Response time math during business hours
A response time SLA tied to business hours requires careful counting when the trigger event lands near a coverage boundary.
Example: 4-business-hour response SLA, business hours 9 AM to 6 PM Eastern, ticket submitted 4:30 PM Friday.
- Friday 4:30 PM to 6:00 PM = 1.5 business hours.
- Saturday and Sunday: closed, clock paused.
- Monday 9:00 AM to 11:30 AM = 2.5 business hours.
- Total = 4 business hours, deadline reached at 11:30 AM Monday.
For a 4-business-hour SLA submitted 9:00 AM Tuesday with no holiday in the way, the deadline is 1:00 PM the same day. Same SLA, same vendor, dramatically different real-time response window depending on when the ticket lands. This is mathematically correct but operationally surprising for customers.
If holidays fall in the count window, those days are excluded too. A ticket submitted late Wednesday before Thanksgiving (Thursday and Friday closed) with a 4-business-hour SLA can take until Tuesday morning to hit the response commitment if Wednesday afternoon does not contain enough business hours to satisfy it.
For a deeper look at SLA response and resolution mechanics, see the SLA response times guide.
Priority tiers and 24/7 carve-outs
Most SaaS support clauses define three to five priority tiers, with progressively shorter SLAs for higher priority. A common structure:
| Priority | Definition | Response | 24/7? |
|---|---|---|---|
| P1 Critical | Service down | 1 hour | Yes |
| P2 High | Major feature broken, no workaround | 4 hours | Often yes |
| P3 Medium | Issue with workaround | 1 business day | No |
| P4 Low | Question, enhancement | 2 business days | No |
The 24/7 designation for P1 and sometimes P2 means the response clock runs continuously regardless of business hours. Outside business hours, an on-call engineer pages in. For lower priorities, the business-hour clock applies.
Customers often misjudge priority. A bug that does not block production but is annoying is P3, not P1. Marking it P1 to get attention may technically be a contract breach (false escalation) and tends to result in pushback from the vendor's support team.
Holiday handling
Vendors typically exclude their local public holidays from business-hour SLA coverage. A US vendor's support is closed on the 11 federal holidays. A UK vendor's support is closed on England and Wales bank holidays. The contract should list the excluded holidays explicitly; if it does not, the inference is the vendor's local national holidays.
For customers in different jurisdictions, this creates mismatched closures. A US vendor is open on Boxing Day; a UK vendor is closed. A US customer of a UK vendor cannot get business-hour support on December 26 even though it is a normal work day in the US.
For full-year planning, request the vendor's published holiday calendar at the start of each contract year. Use the US Federal Holidays 2026 reference for US vendors and the UK Business Day Calculator for UK vendors to map your own coverage gaps. The time zone business hours overlap calculator makes it easy to map your team's working hours against a vendor in another region; the working hours calculator totals coverage hours across a billing cycle.
Service credits and remedies
When a vendor misses an SLA, the contract usually provides for service credits: a percentage of monthly fees credited to the next bill. A typical structure:
- Response SLA missed: 10% of monthly fees for the month
- Resolution SLA missed: additional 10% to 25% depending on severity
- Repeated misses: escalating credits, sometimes capped at 50% of monthly fees
Service credits are almost always the exclusive remedy. The contract typically waives any other damages for SLA failures. If SLA performance is genuinely critical to your business (a payment processor, a clinical trial system, a real-time trading platform), negotiate the exclusive-remedy clause before signing.
Reading the support exhibit
When evaluating a SaaS contract, the support exhibit is the document that contains the actual coverage commitments. Things to verify:
- Coverage hours, including time zone.
- Excluded holidays (with the exact list).
- SLA response times by priority tier, with whether each is business-hour or 24/7.
- SLA resolution times (if any, often softer than response).
- Service credit calculation, including caps.
- Definitions of priority tiers (especially what counts as P1 versus P2).
- Customer obligations for valid SLA claims (notification within 30 days, ticket numbers, etc.).
The support exhibit is usually negotiable for enterprise contracts. Standard SMB SaaS contracts ship with non-negotiable support tiers, but the published commitments are still binding once you sign.
FAQ
Whose business hours apply if my SaaS vendor is in a different country?
By default, the vendor's business hours unless the contract says otherwise. A US-based vendor with 9 AM to 5 PM ET support hours operates on Eastern Time even if you are in London or Sydney. Contracts that specify "customer's local business hours" or "follow-the-sun" coverage are exceptions, not defaults. Read the support exhibit.
What does "business hours excluded from response time" actually mean?
It means the SLA response clock pauses outside the defined business hours. A 4-hour response SLA on a P3 ticket submitted at 4:00 PM Friday with business hours 9 AM to 5 PM Eastern, Monday through Friday, expires at 12:00 PM the following Monday. The 1 hour Friday afternoon plus 3 hours Monday morning = 4 hours of business-hour clock. The weekend does not count.
Does a follow-the-sun support model mean 24/7 coverage?
Effectively yes, but with handoffs between regional teams. A typical follow-the-sun model has Asia-Pacific coverage from a Manila or Bangalore team, EMEA coverage from a Dublin or Lisbon team, and Americas coverage from a US team. Tickets transition between teams at shift change, with documented handoff notes. Coverage is continuous in clock time, but an individual ticket can pass through three different agents in 24 hours.
How are public holidays handled for support?
Most contracts exclude the vendor's local public holidays from business-hour SLA windows. A US vendor's support is closed on the 11 federal holidays unless the contract specifies otherwise. Premium tiers often add holiday coverage explicitly: "24/7/365 P1 response, business hours response for P2-P4, with 4 federal holidays excluded from business hours." Read the support exhibit for the exact list of excluded days.