Does everyone have to use a new form or a new tool?

No. It reads the intake channels you already authorize, and where a request is missing something its type requires, it asks rather than assuming. Which of your channels are in scope is what the audit establishes.

What happens to a request the rules do not cover?

It is held for a person, with what it was and what it lacked, rather than dropped into a default queue. The missing rule is the output of that hold.

The request goes to whoever was nearest

Today

Nothing is refused and nothing is done

The request goes to whoever was nearest.
It lands in a thread or an inbox that belongs to one person, missing the one field that would let anybody act on it, and it sits there while the person who asked assumes it is moving.
Two people pick the same thing up and neither of them knows.
Nothing is refused and nothing is done.

With agents

Completeness and routing both settled at intake, against rules you wrote

A request stops depending on who was asked.
The incomplete request is answered before it stalls.
A misrouted request turns into a rule correction.

How an agent runs it

A request that arrives from a person can be incomplete, and the queue it belongs in is already written down somewhere. This workflow does both jobs at intake.

Takes

Reads requests from the intake channels you authorize, so people can ask the way they already ask.

Classifies

Types each request against the request types you have written down, and says which type it matched.

Checks

Confirms the request carries what its type requires, and asks the requester for what is missing through a channel you authorize.

Routes

Places the request in the queue or with the owner your rules name, and says which rule placed it.

Human gate

Anything the rules cannot classify goes to a person rather than into a default queue. Nothing is fulfilled, approved or closed by the workflow, and the queue can be worked by hand at any point without the agent because the rules and the requests are in your systems.

Tracks

Reports what is open, what is aging past the window you set, and who each request is waiting on.

Records

Keeps the routing decision and the reason for it, so a request that went the wrong way can be explained and the rule corrected.

Results

What changes when intake does both jobs

Not dependent on who was asked

It is typed against your written request types and placed by your own routing rule.

Answered before it stalls

The completeness check runs at intake, and the missing field is asked for rather than assumed.

A misroute becomes a rule correction

The routing decision and its reason are kept with the request, so the rule that failed is the thing you fix.

Where this fits

Workflow / Automate a Workflow

Tier 1 through the Automate a Workflow door: one process end to end, from a request arriving to the right queue holding it. Doing the work, approving it, and every exception to the rules stay with people. The executive assistant layer is where this can go next if the same intake later sits with one seat's calendar and follow-through, as a possible step rather than a promised state; How It Works shows how the hold and the authorizations are built.

Tier 1 / Prove

How It Works

Questions, answered

No. It classifies and routes, and nothing is fulfilled, approved or closed by the workflow. The gate is closed by default, and the rules and the requests live in your systems, so the queue can be triaged by hand at any point without the agent.

AI Opportunity Audit

See how many your own written rules could have placed

Bring a week of internal requests and see how many of them your own written rules could have placed without anybody reading them first.

Book an audit