Default team, notification policies and business hours
Set the team new chats land on, which events trigger email/push for your team, and the workspace business hours that drive SLA and auto-snooze.
Watch this step in the video · Workspace settings: notifications
What you're setting up
Three workspace settings that work together: the default team that receives new chats, the notifications that alert your people, and the business hours that define when you're open (and which SLA and auto-snooze depend on).
Requirements
- A role with access to workspace settings (admin / owner).
- Teams created if you plan to route by team.
Default team for new chats
- In the sidebar, open Settings → Workspace settings.
- Go to the Routing tab.
- Under Default team for new chats, choose the team. Every new inbound gets tagged to it automatically.
- Per-channel settings override this value; leave it on — no default team — to skip auto-routing.
- Click Save routing.
Workspace notification policies
- In Workspace settings, open the Notifications tab.
- Under Notification mode, choose how much noise the team gets (for example, Silent — dashboard only to send no email/push).
- Under Notifications by type, define which events trigger email or push for workspace members.
- Turn on Force push notifications for all agents to force push for everyone.
- Under Re-mark as unread, set whether a chat is re-marked unread on transfer or after inactivity, and whether the assignee is notified.
- Click Save notifications.
Each agent also controls their own notifications (email, push, in-app and sound) under Settings → Notifications.
Business hours
- In the Workspace menu, open Business Hours.
- Pick the timezone: all hours below are interpreted in it.
- Under Weekly Schedule, mark the available days and opening hours; use Copy to all to replicate one day across the week.
- Mark days you don't operate as Closed.
- Click Save Changes.
Business hours feed the SLA, the inbox auto-snooze outside hours option and the out-of-hours auto-reply.
Verify
Send a test message outside your configured hours: if auto-snooze is on, it should land in Snoozed. Confirm alerts arrive according to the chosen mode and that new chats fall to the default team.
If it doesn't work
- No notifications arrive: check the workspace Notification mode and, separately, each agent's personal preferences.
- SLA counts off-hours: verify the timezone and that the day isn't marked Closed.
- Chats go to the wrong team: a per-channel rule or a workflow may be overriding the default team.
Tips
- Set the correct timezone first: a perfect schedule in the wrong zone breaks the SLA.
- Use Silent — dashboard only on internal workspaces to avoid email overload.
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.