What are Opening Hours?

Opening Hours defines when your support team is available across channels and teams. Unlike simple “9-5 Monday-Friday” settings, Atender supports multiple independent rules — so you can model Phone team covers 8am-noon, but email is 24/7, or English support around the clock, Norwegian support 8-17 weekdays, all in the same workspace.

What an opening-hours rule is

A rule is one self-contained schedule with its own scope. You can have one rule for the whole company, or fifty rules for fine-grained coverage. Each rule has:

• Name — A descriptive label (e.g. Phone Team Weekdays, Email 24/7, Holiday Phone Hours)
• Team Assignment — One or more teams this rule applies to
• Channel Assignment — Which channels follow this schedule
• Weekly schedule — Per-day time slots, with split-shift support
• Timezone — Auto-detected from browser, overridable per rule
• Holiday calendar — Country code that imports public holidays
• Date overrides — Specific dates marked closed or set to custom hours
• Active toggle — Disable without deleting

Why multiple rules

Because real teams don’t all work the same hours. A few examples:

• Channel-specific availability — phone team is live 8am-12pm; email is asynchronously monitored 24/7. Two rules, different channels, different schedules.
• Language-specific coverage — English support 24/7 across all channels; Norwegian support weekdays 8-17. Two rules scoped to different teams.
• Holiday rules — a “Holiday Phone Coverage” rule with reduced hours that only applies on certain dates, layered over the standard rule.
• Channel + team combinations — Premium chat team is 24/7; standard chat team is business hours only.

Trying to express any of these with a single global “office hours” setting forces compromises. Multiple rules let each team and channel have honest hours.

What downstream features do with opening hours

Opening hours are read by other parts of the product:

• SLA policies pause their timers outside business hours by default — see Run an SLA 24/7 for the exception.
• Automation rules can be scoped to fire only inside or outside business hours via schedule restrictions.
• Voice IVR flows check the schedule via the Is Open node, routing after-hours callers to voicemail or a different queue.
• Web chat widget uses the schedule to show availability state (“we’re online” / “back tomorrow at 9am”) to visitors before they engage.

This is why getting opening hours right is foundational. Several other features pivot on it.

Where to start

• Set up your basic schedule: Set up your team’s opening hours
• Add holidays: Configure holidays and date overrides
• Distributed teams: Set up split shifts and multi-timezone hours
• When rules collide: Rule resolution reference
• SLA not pausing as expected: Why is my SLA timer counting outside business hours?