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.