Product

Introducing Patterns

Domain-specific accuracy for the identifiers that matter most

June 22, 2026 2 min read

A caller reads out their order code. The model drops one letter. The lookup fails, the wrong item ships, and your support queue grows by one. General-purpose speech recognition was built for natural language, not for the structured identifiers your transcripts actually depend on. That’s why we built Patterns, a feature on our API that biases the model toward those identifiers order codes, invoice numbers, license plates, SKUs, case references so they come out right the first time.

Why general models get identifiers wrong

A general speech recognition model transcribes an order code the same way it transcribes a sentence: by predicting what’s most likely to come next in natural language. However, identifiers follow rules the model was never told about, which leads it to guess - dropping a letter, mis-formatting a licence plate, hearing “INB” instead of “INV”. When the result has to match a record exactly, every guess is a failed lookup, a wrong delivery, and another support ticket

How Patterns works

You give us a sequence that describes the format you expect, and the model will bias towards it as it transcribes.  

What is heard (without Patterns) What is said (corrected with Patterns)
Your order code is INB seven six two five X INV7625X
The reference number is P096590, quantity one six PO96590, quantity one six
The number plate is TC94FTH northbound at 85 TZ94 FTH northbound at 85
Registration W53TYN WU53 TYN

Performance improvements

We measured the impact of Patterns on two relevant use cases, scoring word error rate on the identifier against the baseline model with no patterns applied.

Use case Baseline WER WER with Patterns Relative error reduction
Order numbers 8.0% 1.5% −81%
Licence plates 6.6% 4.7% −29%

Getting started

Check out our documentation to learn more, and head over to our console or speak to our team to get started with Patterns today!