Once your workforce mixes humans and AI employees, every inbound message poses a routing question: is this for the SDR, the bookkeeper's queue, or a human who needs to see it now? This employee is the front door. It reads what comes in, understands what each message actually needs, and routes it to the right employee - human or AI - with the context attached. Messages stop pooling in inboxes waiting for someone to sort them.
Inbound messages get read on arrival and routed to whoever - or whatever - should handle them. The sorting job nobody owns becomes a job that runs continuously.
The refund request goes to a human, the follow-up request goes to the SDR's queue, the bill goes to the clerk. The routing understands the content, not just the sender.
The angry client, the time-critical ask, the message that should interrupt your day: escalated immediately, past every queue. Everything else flows without ever pinging you.
Every message gets an owner and a visible disposition. The record of what went where means no one ever archaeologies an inbox to find what got dropped.
Your private channel opens the minute you hire. No call, no kickoff meeting, no software to install.
It studies your business and writes your Company Brief, then maps the destinations: your people, your AI employees, and what belongs to each.
You connect where messages arrive, once, in your portal's Access tab. From then on, arrivals get read and routed as they land.
The rules get proposed in plain language: this goes there, this escalates, this waits for a human. You approve once, tune forever in single sentences.
Messages land where they belong with context attached, urgent things interrupt, routine things flow, and the disposition record answers every "what happened to...?"
Like every Tenfold employee, this one runs one opinionated method: route on content rather than sender, escalate ambiguity instead of guessing, and leave a disposition trail for every single message - a front door that loses mail is worse than no front door. When the field moves, the method moves, and you do nothing to get the update. Here is the whole method.
It reads inbound messages and routes them through grants you make once, in your portal's Access tab. Routing follows the rules you approved, replies to outsiders stay human unless you say otherwise, and you can revoke access yourself at any time.
Its craft is routing. Acknowledgments can go out under rules you approve; substantive replies go to whoever the message was routed to - human or AI employee - each with their own approval rhythm.
By your rulebook: what each destination handles, stated plainly and approved by you. Content it cannot confidently place escalates to a human with its best suggestion attached.
They skip every queue and reach the right human immediately - urgency detection is part of the reading, and the definition of urgent is yours to set.
Always: every message carries a disposition - routed where, when, handled by whom. The audit trail is the difference between triage and a black hole.
It shines brightest running a mixed workforce, but even routing purely to humans it ends the everyone-reads-everything tax. As your roster grows, the front door is already standing.
An AI employee that watches every employee in your AI workforce and alerts on silent failure - the workforce management layer that keeps automated work trustworthy.
An AI employee that snapshots your workforce's state on a rhythm and restores it on failure - so a bad day costs you hours of history, never the workforce itself.
An AI employee that reads across every department each morning and hands you one digest: the consolidated waiting-on-you queue, per-department notes, and the cross-signals.
An AI employee that processes incoming bills, categorizes them, flags what looks off, and queues everything for your approval - so paying bills takes minutes, not an afternoon.
Requesting this role moves it up the roster - requests set the order roles open for hire, and you will hear the moment it opens.
See all 51 roles