Agent schedules: weekly hours, split shifts, routing and OOO
Set per-workspace shift schedules so auto-assignment only routes conversations to agents who are currently on shift.
Watch this step in the video · Each person's workspaces, calls and schedule
Agent schedules define, day by day, the hours each agent is available to receive conversations. They keep automatic assignment (auto-assign and round robin) from handing chats to someone who is off shift, and let you represent temporary absences (OOO).
Heads up: schedules are per workspace. The same agent can have different shifts in each workspace they belong to.
Before you start
- You need the organization owner role to manage other members' schedules.
- Schedules only affect routing when the workspace toggle (below) is on.
Set up a schedule
- Go to Settings -> Members.
- On the agent's row, click Manage schedules.
- If you belong to several workspaces, pick the right one in the selector at the top of the modal (schedules are stored per workspace).
- For each day (Monday to Sunday), click Add range and enter a start and end time.
- For a split shift (e.g. 09:00-13:00 and 15:00-19:00), add two ranges on the same day by stacking them.
- Save your changes.
How ranges are interpreted
- An agent with no ranges at all in the workspace is treated as always available (backward compatibility).
- An agent with at least one range but no range covering the current moment is off shift.
- Ranges are half-open intervals
[start, end): a shift ending at 18:00 covers up to 17:59:59, so 14:00-18:00 and 18:00-22:00 never overlap. - Times are evaluated in the workspace timezone.
Turn on schedule-aware routing
- Open the workspace and go to its Settings.
- Enable Respect agent shift schedules.
With the toggle on, auto-assign and round robin skip off-shift agents. Manual assignment from the inbox always works, on shift or not.
Temporary absences (OOO)
There is no per-agent "out of office" button. To pull someone out of automatic routing:
- One day off: leave that day with no ranges (they'll be off shift that day), as long as the agent has hours on other days.
- Longer absence: temporarily remove them from the teams that route, or deactivate them as a member.
Verify
Create a test conversation and confirm that, while off shift with the toggle on, they are not auto-assigned. Inside their range, they should receive it.
If it doesn't work
- They still get chats off shift: check that Respect agent shift schedules is on in that workspace.
- They always look available: they probably have no ranges saved; remember an empty grid = always available.
- Times look off: check the workspace timezone.
Tips
- Set the workspace timezone first; every shift is read against it.
- Use split shifts for lunch breaks instead of one long block.
Related articles
Related articles
-
How to enable two-factor authentication (2FA)
Protect your Omnifox account with a second factor from an authenticator app, step by step.
-
Create your own help center for your customers
Publish FAQ articles on a public page with your brand color so your customers can solve their questions without opening a conversation.
-
Data protection and GDPR for companies in the European Union
What Omnifox offers today to help you comply with GDPR: data export and deletion, security, where data is hosted, the data processing agreement (DPA) and what doesn't exist yet.
-
Single sign-on (SSO) with your identity provider (OpenID Connect)
Let your team sign in to Omnifox with their company account from Microsoft Entra ID, Google Workspace, Okta or any other OpenID Connect provider.
-
Settings and security complete guide
Settings and security in depth, in 32 chapters: organization, workspaces, members and roles, teams, hours, SLA, notifications, two-factor authentication, passwords, sessions, IP allowlist, audit and privacy.