Experience-aware question routing

The idea

A question goes to the colleague or manager with the most relevant ownership, precedents, finished work and expertise, with the basis stored; the nearest manager is the fallback.

The problem
Routing by hierarchy alone sends questions to people who do not know.
Why it matters
Questions reach whoever has evidence of knowing the topic.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

Where it lives in the product

  • Authority ladder: the owner is the last resort

    A question goes to the asker's manager worker, then the CEO, which decides from the org profile and record; a person gets it only for an owner reason, and their answer becomes a precedent.

  • Typed requests in every direction

    Workers and people ask each other typed questions (review, information, decision, help, handoff) peer to peer, up or down, with due times, defaults, redirects and an inbox.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.