Conditional routing sends an input to a specialized agent or workflow based on what the input needs. A router first decides who should handle the request, then hands it off. Unlike a flow that runs the same agents for every input, a branch selects a path for each request. section 4.1.3
Routing support requests
A customer-support router can send a technical question to a technical expert and a billing question to a finance agent. The same pattern could direct a user query to a math problem-solver rather than a legal-reasoning agent. section 4.1.3
Use branching when requests cover distinct domains and not every agent should attempt every task. Skip it when one generalist can handle the inputs: routing adds overhead. Check the boundary between branches carefully. A misclassified request may get a poor answer, while a request spanning two domains may not fit a simple choice. section 4.1.3
