Multilingual support without hiring multilingual staff

Requirements describe capabilities the pattern needs in your environment, not the vendors you must buy. Any system that fills a requirement satisfies it — that’s what makes the catalog portable across the long tail of SMB tooling.

1. inbound_request_channel

   REQUIREDREADevent

   Where customer messages arrive, possibly in multiple languages.

   DATA SHAPE

   Free-text customer messages with sender identifier, timestamp, and optionally a declared or detected language hint.
   COMMONLY FILLED BY

   • helpdesk ticketing system
   • shared support inbox
   • chat widget on the website
2. response_channel

   REQUIREDWRITErequest

   Where the translated reply is sent back to the customer.

   DATA SHAPE

   Translated reply text in the customer's language, tied to the original thread.
   COMMONLY FILLED BY

   • same helpdesk system, reply field
   • outbound mail from a shared inbox
   • chat widget response stream
3. agent_working_surface

   REQUIREDREAD + WRITErequest

   The agent's view, showing the translated inbound message and accepting replies in the agent's native language.

   DATA SHAPE

   Bilingual ticket view: original message + translation, draft compose field, optional 'show original' toggle.
   COMMONLY FILLED BY

   • the existing helpdesk agent view with translation overlay
   • a side panel showing the bilingual pair
   • a browser extension if the helpdesk doesn't allow inline customization
4. terminology_glossary

   REQUIREDREADcorpus

   Brand, product, and policy terms the pattern must translate consistently or leave untranslated. The mechanism that makes the pattern feel native rather than machine.

   DATA SHAPE

   Term pairs: source language term, target language term (or 'do not translate'), context note. Tens to low hundreds of entries per client.
   COMMONLY FILLED BY

   • a spreadsheet maintained by the support lead
   • a small admin UI inside the pattern
   • a section in the internal wiki the team edits
5. quality_audit_loop

   RECOMMENDEDWRITEbatch

   Native speakers periodically review translated tickets for quality. Without this, drift toward awkward or wrong phrasing goes unnoticed.

   DATA SHAPE

   Sampled bilingual ticket pairs with reviewer verdict and notes. Per language, monthly cadence typical.
   IF MISSING

   Quality regressions in less-common languages go undetected. Recommend at minimum a quarterly review per supported language, even via a contractor.
   COMMONLY FILLED BY

   • monthly digest emailed to a native-speaking advisor or freelancer
   • internal review dashboard
   • language-specific Slack channel where bilingual team members spot-check