LLM-based classification introduces non-deterministic edge-case errors and latency. Discover why explicit rule engines remain the gold standard for routing.
It is tempting to throw an LLM prompt at every classification task in an enterprise. Founders prompt models to classify customer support tickets, route sales leads, and categorize expense items. But in production, prompt-based categorization introduces non-deterministic variance, latency, and recurring token costs for problems solved by simple boolean logic.
A rule engine executes in under 2 milliseconds, costs $0.000000 to run, and behaves with 100% mathematical predictability. An LLM takes 1,500 milliseconds, costs fractions of a cent per call, and occasionally invents an unprecedented edge case that misroutes an enterprise account.
The operational classification hierarchy
Always deploy classification logic in a tiered funnel, exhausting deterministic filters before passing remaining edge cases to semantic models:
- Tier 1: Explicit boolean matches (e.g. domain matching, country codes, exact keyword triggers). This resolves 60-70% of inbound traffic instantly.
- Tier 2: Regular expression and pattern matching (e.g. currency amounts, order numbers, phone formats). Resolves an additional 15%.
- Tier 3: Embedding vector similarity search against known category centroids. Resolves ambiguous phrasing in sub-50ms.
- Tier 4: Generative LLM with strict JSON schema constraints. Reserved solely for the remaining 5% of unstructured, noisy inputs.
Intelligence is knowing when not to use expensive intelligence.
Engineering for auditability
When an important deal is misrouted, a business leader must be able to inspect the decision log and understand why within 30 seconds. Rule-based engines offer unambiguous boolean logs; generative prompts require prompt engineering post-mortems. Choose auditability.

Anmol Masih
Founder & StrategistFounder of Tasvirwala & T. Creatives. Designing intelligent business systems, agents, and compounding operational workflows.