The Router Agent · Type 5 of 7
◷ 12:00
Follow along · live workshop

Stop Being Your
Team's Router

It doesn't forward your mail. A router agent reads one messy request, splits it apart, and sends each piece to the right specialist.

AI Agent Type 5 — Router Agent·Intent classification·Decompose & dispatch
Skip to “try it yourself”
Messy request ROUTER Engineering Sales Product Human
How a real router agent thinks

Three levels of routing.

Most people picture routing as sorting one email into one bucket. That's level one. The part that impresses is what happens next — it takes them apart and rewrites them.

LEVEL 1

Classify

Reads meaning and intent — not keywords. It knows “about to cancel” is churn, not a billing question.

LEVEL 2

Decompose

One message usually hides several intents. It pulls them apart into separate, distinct tasks.

LEVEL 3

Tailor & dispatch

Rewrites each piece for its specialist and sends only what's relevant. Strips out the rest.

A distribution list

Forwards the whole message to everyone. Each team still has to read it, hunt for their part, and ignore the rest. Nobody saved any work.

copycopycopy
VS

A router agent

Reads the message, separates the issues, and hands each team only its part — already written up. Zero human triage.

bugseatsdocs
Live demo One messy email

How many issues are hiding in here?

BugUpsellDocs
Step 1 It analyzes — the routing log
1 Dashboard crashes on PDF export Engineering97%
2 Wants +50 enterprise seats
⚠ revenue — needs human approval Sales95%
3 API rate-limit docs are outdated Product92%
Step 2 It drafts — three emails, three audiences
→ Engineering
Subject
Bug: dashboard crashes on PDF export
Customer reports the new dashboard crashes on PDF export — likely blocking reporting. Please repro on the current build and triage.
→ Sales
Subject
Expansion: +50 enterprise seats
Growing account wants +50 seats. Warm upsell.
⚠ hold for approval
→ Product / Content
Subject
Docs feedback: API rate-limits outdated
Customer flagged the API rate-limit docs as outdated and confusing. Worth a review and refreshed examples.

Each team gets only its slice — rewritten for them. Nobody triages anything.

Do it now Your own inbox

Run the router yourself.

This is the whole agent, in one prompt. Paste it into Claude or any chatbot, drop in a messy email of your own, and watch it split apart.

The router prompt 

    


    

      
      
The messier the better — cram in two or three different issues (a bug, a billing question, a feature request…).

      
      

        
        
      

    


    

      
You nailed it when…

      
    
        
  • You got a routing log — every issue split out with its own department and a confidence score.
    • 
        
  • Each draft contains only its own team's issue — the others are stripped out.
    • 
        
  • Anything about money or risk got flagged “needs human approval” instead of auto-sending.
    • 
      

    


    

      
      
    

  


  
  

    
Your move this quarter

    
Point it at your messiest inbox.

    
Anywhere mixed, multi-issue requests pile up and someone has to sort them by hand — that's where a router earns its keep.


    

      

        

        
Support inbox
Multi-issue customer emails, split and routed the moment they land.

      

      

        

        
IT helpdesk
One team's ticket triage cut resolution time by roughly 40%.

      

      

        

        
Slack / Teams channel
“Who owns which part of this?” — answered before anyone has to ask.

      

    


    

      
      
Keep a human on the high-stakes calls. A confidence score on every decision, plus a human gate on anything about money or risk, is your control layer — and it's exactly what the next session builds on.

    


    

      
      Back to top ↑