Question

A customer support team receives a wide mix of incoming messages: simple password resets, billing disputes, and complex technical troubleshooting. Each category needs a very different prompt, tone, and level of reasoning. The team wants each message handled by the most appropriate specialized prompt without paying for heavy reasoning on trivial requests. Which workflow pattern best fits this need?

Accepted Answer

Routing — first classify each message into a category, then send it to a prompt specialized for that category

Answer

Parallelization — send every message to all three specialized prompts simultaneously and merge the outputs

Answer

Evaluator-optimizer — repeatedly generate and critique a single response until it meets a quality bar

Answer

Orchestrator-workers — have a model dynamically break each message into unpredictable subtasks at runtime