Default inbox view and routing / auto-assignment rules
Decide what conversations your team sees when they open the inbox and how new chats are distributed: auto-assign, default team and shift schedules.
Watch this step in the video · Workspace settings: routing
What you're setting up
These settings live at the workspace level and control two things: which conversations show up when an agent opens the inbox, and how new chats are distributed across your team. Done right, they stop two agents from replying to the same customer and keep your list free of closed clutter.
Requirements
- A role with access to workspace settings (admin / owner).
- At least one team created if you plan to route by team.
Opening the settings
- In the left sidebar, open the Workspace menu.
- Go to Workspace settings.
- You'll see the tabs General · Inboxes · Routing · Notifications.
Default inbox view (Inboxes tab)
- Open the Inboxes tab.
- Under Default inbox view, pick one:
- Active only (recommended): hides closed, resolved and snoozed.
- Recent: hides closed and resolved; snoozed stay visible.
- Show all: hides nothing (not recommended at scale).
- Under Visual defaults, set Sort (Most recent, Oldest, Oldest unanswered, By priority), Starting tab (All, Mine, Unassigned) and Density (Comfortable or Compact).
- Turn on Jump to next conversation if you want the panel to open the next chat automatically when an agent snoozes/resolves/closes.
- Click Save inboxes.
Routing and auto-assignment rules (Routing tab)
- Open the Routing tab.
- Auto-assign conversations: turn it on so every new chat is assigned to an available agent automatically.
- Auto-claim on reply: when an agent replies to an unassigned chat, it becomes theirs.
- Respect agent shift schedules: auto-assignment skips off-shift agents (manual assignment is never blocked).
- Default team for new chats: choose the team every new inbound is tagged to. Per-channel rules override this; leave it empty to skip auto-routing.
- Click Save routing.
Verify
Open the inbox in a fresh window: you should see the view, sort and tab you defined. Send a test message from a connected channel and confirm the conversation auto-assigns (if you enabled auto-assign) to the right team or agent.
If it doesn't work
- Chats aren't auto-assigning: check that Auto-assign is on and that agents are on-shift if Respect schedules is enabled.
- They land on the wrong team: a workflow or a per-channel rule may be overriding the default team. Review your automations.
- I still see closed chats: switch the Default view to Active only and save again; remember the inbox Status filter can still surface them on demand.
Tips
- If you run shifts, pair Respect schedules with agent schedules so nobody off the clock gets work.
- Have workflows that assign or change status? They can clash with these defaults: review them before changing global behavior.
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.