Topic rules
Payments, documents, support, and operations go to separate lanes with different service windows.
Queue distribution
One intake desk for many teams.
Pool Desk receives requests from forms, chats, and internal notes, then routes them by topic, urgency, schedule, and team load. The result is a clear work queue instead of a messy room full of mixed messages.
Useful signals, not noise.
The public face looks like a normal operations product because it is structured like one: queue health, routing rules, roles, and daily reporting.
open queues9across teams
closed today74with notes
pickup time8mmedian
rules31reviewed
Routing with visible reasons.
Every item keeps a readable explanation: why it moved, which team owns it, and when it should be checked again.
Load balance
Assignments look at current workload, online operators, and pending review items.
Daily close
Leads get a compact summary of closed, delayed, and reassigned work.
A believable private workspace.
The sign-in form is intentionally quiet: invited users, workspace code, and one-time pass. No public registration, no noisy sales layer.
1. Intake
Requests are normalized and attached to a source.
2. Route
Rules select the right queue and owner group.
3. Review
Exceptions stay visible until a lead closes them.
Queue rhythm
Response rhythm is recalculated when the board refreshes.