Business Hours
Business Hours in Salesforce is the Setup feature that defines the operating windows the org uses for time-sensitive calculations: when escalation rules fire, when milestone clocks tick, when entitlement SLAs count down, when Omni-Channel routes to available agents, when chat channels accept inbound conversations.
Definition
Business Hours in Salesforce is the Setup feature that defines the operating windows the org uses for time-sensitive calculations: when escalation rules fire, when milestone clocks tick, when entitlement SLAs count down, when Omni-Channel routes to available agents, when chat channels accept inbound conversations. Each Business Hours record specifies a name, a time zone, and a weekly schedule of open and closed periods. Multiple Business Hours records can coexist; rules and entitlements reference whichever one applies to their context.
Business Hours exists because almost every service workflow needs to know whether it is currently "in hours" or "after hours". A case opened at 2 AM should not have its 4-hour SLA tick down through the night when the team is not staffed. An escalation rule that fires after 1 hour of no response should only count business hours, not weekend hours. The single setting underpins much of the time-aware automation across Service Cloud and beyond, and getting it right is one of the cheapest ways to make automation behave the way users expect.
Why Business Hours is the time foundation almost every service workflow depends on
Where Business Hours lives and what it contains
Setup, Company Settings, Business Hours. The page lists every Business Hours record in the org, the time zone for each, the active flag, and which is marked as Default. Each record has a weekly schedule (Monday through Sunday with open and close times per day) and a Holidays section listing one-time closures. Click into a record to edit. The Default Business Hours is the one used by any rule or feature that does not explicitly reference a specific Business Hours record.
Time zones and the per-region pattern
Each Business Hours record has its own time zone. Global orgs typically build one Business Hours per region (US East, US West, EMEA, APAC) so case routing and SLA calculations align with the team that actually handles the work. The time zone is the trick most often gotten wrong; setting a Business Hours to UTC when the team is in Pacific time produces SLAs that count down at the wrong moments. Always verify the time zone against the team that consumes the Business Hours record.
Holidays and the closure exception pattern
The Holidays section on each Business Hours record lists one-time closures (Christmas Day 2026, New Year's Day 2027) plus recurring closures (every July 4th). Time-sensitive automation pauses during holidays the same way it pauses outside daily business hours. Holidays must be maintained per year; an org that set up Holidays in 2024 and never updated finds that 2026 Christmas Day is treated as a regular Friday. Build a quarterly habit of reviewing the next 12 months of holidays per Business Hours record.
How Business Hours connects to Entitlements and Milestones
Entitlements (the Salesforce SLA construct) reference a Business Hours record. Each Milestone on an Entitlement Process has a time-to-complete that counts only during the referenced Business Hours. A case attached to an entitlement with US East Business Hours has its SLA tick during US East working hours, pause overnight and weekends, and resume the next business morning. The connection is one-to-many; a single Business Hours record commonly powers dozens of entitlement processes. Changing a Business Hours record's schedule ripples through every entitlement that references it.
Escalation rules and the after-hours behavior
Case Escalation Rules have a Business Hours field that determines when their "minutes to escalate" countdown runs. A rule with 30-minute escalation on US East Business Hours starts the countdown when the case is opened, pauses when business hours end, resumes the next business morning. A rule without a Business Hours reference runs 24/7. Most service teams want business-hours-only escalation for cases opened by customers and 24/7 escalation for system-detected outages; build separate rules with separate Business Hours assignments to express both patterns.
Omni-Channel routing and the channel-availability question
Omni-Channel can use Business Hours to gate channel availability. A chat channel can be available only during business hours and route to a hold or callback queue outside. Voice channels can route to overflow agents in another region after local business hours. The configuration is per channel; admins set the Business Hours record on the Omni-Channel Routing Configuration. Without explicit Business Hours configuration, channels are always available, which often leads to off-hours customer chats sitting unattended.
Maintenance, auditing, and the quarterly review
Business Hours records drift from real-world business reality over time. Teams change shifts, regions add coverage, holidays add and remove. The maintenance discipline: quarterly review of every Business Hours record against current team schedules. Most orgs do this poorly; the Business Hours configured at go-live persists for years even as the team moves to different working hours. The signal that maintenance is overdue: customer complaints about responses that should have come faster but did not because the SLA was paused.
How to design Business Hours that align with how the team actually works
The pattern: one Business Hours per region or team that needs distinct coverage, time zones set to the team's actual location, holidays maintained quarterly. The complexity scales with the number of regions; single-region orgs need one record, global orgs need several with careful per-feature assignment.
- Inventory the regions and teams that need distinct hours
Document which teams cover which regions, what hours they actually work, what time zone they live in. The list is the basis for Business Hours record design.
- Create one Business Hours record per team
Setup, Business Hours, New Business Hours. Name it after the team or region. Set time zone to the team's location. Configure the weekly schedule per the team's actual hours.
- Mark one record as Default
The Default Business Hours is used by any rule or feature that does not explicitly reference one. Pick the most-applicable team's hours as the default.
- Add Holidays for the next 12 months
Add company holidays per Business Hours record. Maintain quarterly so the next 12 months is always populated.
- Assign Business Hours to Entitlements, Escalation Rules, Omni-Channel
For each time-sensitive feature, reference the matching Business Hours. Skipping this falls back to the default, which may not match the team responsible.
- Document the assignment in your change log
Which Business Hours backs which entitlement, escalation rule, channel. The assignment is easy to lose track of as features accumulate; the documentation is the audit trail.
- Schedule the quarterly Business Hours audit
Quarterly review: confirm hours match current team schedules, confirm holidays are populated for the next 12 months, confirm assignments still match the responsible team.
The time zone the schedule is interpreted in. Set to the team's actual location.
Open and close times per day of week. Configures the daily windows.
One-time or recurring closure dates. Maintain quarterly.
Whether this record is the org-wide default used by features that do not explicitly reference one.
Whether the record is in use. Deactivating retires the record without deleting historical references.
- Time zone misconfiguration is the most common Business Hours mistake. Setting US East Business Hours to UTC produces SLAs that tick at the wrong moments.
- Holidays do not propagate across years automatically. An org that configured Holidays in 2024 and never updated finds 2026 Christmas treated as a regular Friday.
- Default Business Hours is used by features that do not explicitly reference one. Misalignment between default and responsible team produces SLA surprises.
- Changing a Business Hours record's schedule ripples through every entitlement, escalation rule, and Omni-Channel config that references it. Audit before changing.
- 24/7 escalation rules (no Business Hours reference) and business-hours rules look identical in Setup; the only difference is the Business Hours field. Confirm before assuming a rule's behavior.
Trust & references
Cross-checked against the following references.
- Business Hours referenceSalesforce
- Entitlements overviewSalesforce
Straight from the source - Salesforce's reference material on Business Hours.
- Business HoursSalesforce Help
- EntitlementsSalesforce Help
- HolidaysSalesforce 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. Can a Salesforce admin configure Business Hours without writing code?
Q2. In which area of Salesforce would you typically find Business Hours?
Q3. Why is understanding Business Hours important for Salesforce admins?
Discussion
Loading discussion…