Client requests arrive addressed to everyone and owned by no one: an email that three people read and nobody actioned, a message that was actually four asks wearing one paragraph. This employee is the front desk your delivery never had. It parses every inbound request, splits it into the real asks, and routes each one to the right person with the context attached - so nothing sits unowned while everyone assumes someone else has it.
Inbound asks get parsed, split, and routed to the right person the moment they arrive. The unowned-request problem - the root of most delivery misses - ends structurally.
Clients bundle. One friendly email often carries a change request, a question, a complaint, and a new piece of scope. Each gets separated, named, and routed on its own.
The routed task carries what the receiver needs: who asked, exact words, the client's history, and the commitment it relates to. Nobody starts by re-reading a thread.
It reads urgency from content, not punctuation: the small ask from an unhappy client outranks the big ask from a calm one. Priority stops depending on who shouts.
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 learns your team: who does what, who covers whom, and where routed work should land.
You connect where client requests arrive, once, in your portal's Access tab. From then on, everything inbound gets read on arrival.
It proposes the routing in plain language: this kind of ask goes to this person, this kind escalates. You approve once, adjust any time in a sentence.
Your team finds requests already parsed, prioritized, and in their lane with context attached. The inbox stops being the place where accountability dies.
Like every Tenfold employee, this one runs one opinionated method: every ask gets exactly one owner, bundled requests get split before they get routed, and ambiguity escalates to a human instead of being guessed at. When the field moves, the method moves, and you do nothing to get the update. Here is the whole method.
It reads inbound requests and routes work through grants you make once, in your portal's Access tab. Routing follows the rules you approved, credentials never appear in chat, and you can revoke access yourself at any time.
Its craft is triage: parse, split, route, prioritize. If you want it acknowledging receipt to clients, that runs by the rules you approve and in your voice - and anything beyond an acknowledgment stays human.
From the routing rules you approved, built on your team's actual roles. When a request fits nobody's lane cleanly, it escalates to you with its best suggestion rather than guessing.
It extracts what is clear, names what is not, and routes with the ambiguity flagged - or asks you first, per your rules. Vague in never becomes wrong out.
Yes - connect each place inbound work arrives and it triages them as one stream, one set of rules, one record of who owns what.
The opposite, usually: work arrives cleaner, with context, in the right lane, and nobody gets blamed for a request they never saw. It manages the flow, not the people.
An AI employee that reviews delivery work against your standards before it reaches the client - every time, with the findings listed, so quality stops depending on who was busy.
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.
An AI employee that sweeps your invoicing weekly for overdue invoices and quietly-lapsed recurring billing, and flags what needs chasing - before the money ages out.
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.
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