Question

A customer support team processes thousands of incoming queries daily. Most are simple FAQ-style questions (password resets, hours of operation), while a small fraction are complex technical issues requiring detailed reasoning. The team wants to minimize cost and latency without sacrificing quality on hard cases. Which pattern best fits this situation?

Accepted Answer

A routing workflow that classifies each query, then sends simple ones to a small, fast model and complex ones to a larger reasoning model

Answer

An orchestrator-workers pattern that dynamically decomposes every query into subtasks handled by separate worker calls

Answer

A parallelization voting pattern that sends every query to three models and takes the majority answer

Answer

A single prompt-chaining workflow that runs all queries through the same fixed sequence of large-model steps