That “unknown carrier” path is where I’d add an ops feedback loop, not just a fallback matcher. Log the raw customer-entered name, resolved carrier, tracking-number prefix/length, and outcome; then review unresolved cases by frequency each week. Let support propose aliases in a small reviewed table (normalized spelling, source, last-verified date) with approval and rollback, rather than requiring a code deploy. On the customer page, show “We think you mean Jetspeed” beside the original query and let people confirm. If confidence is low, keep broad matching running and label the result unverified instead of stopping updates. A simple dashboard for alias-driven resolutions, false matches, and “courier not found” tickets will show whether the change helps without hiding bad mappings.