دعم متعدد اللغات بدون توظيف طاقم متعدد اللغات

المتطلبات تصف قدرات يحتاجها النمط في بيئتك، مو الموردين اللي لازم تشتريهم. أي نظام يملأ متطلباً يحقّقه — وهذا اللي يخلّي الكتالوج قابلاً للنقل عبر الذيل الطويل من أدوات الشركات الصغيرة والمتوسطة.

1. inbound_request_channel

   مطلوبقراءةحدث

   Where customer messages arrive, possibly in multiple languages.

   شكل البيانات

   Free-text customer messages with sender identifier, timestamp, and optionally a declared or detected language hint.
   يُملأ عادةً بواسطة

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

   مطلوبكتابةطلب

   Where the translated reply is sent back to the customer.

   شكل البيانات

   Translated reply text in the customer's language, tied to the original thread.
   يُملأ عادةً بواسطة

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

   مطلوبقراءة + كتابةطلب

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

   شكل البيانات

   Bilingual ticket view: original message + translation, draft compose field, optional 'show original' toggle.
   يُملأ عادةً بواسطة

   • 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

   مطلوبقراءةمجموعة

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

   شكل البيانات

   Term pairs: source language term, target language term (or 'do not translate'), context note. Tens to low hundreds of entries per client.
   يُملأ عادةً بواسطة

   • 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

   موصى بهكتابةدفعة

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

   شكل البيانات

   Sampled bilingual ticket pairs with reviewer verdict and notes. Per language, monthly cadence typical.
   إذا مفقود

   Quality regressions in less-common languages go undetected. Recommend at minimum a quarterly review per supported language, even via a contractor.
   يُملأ عادةً بواسطة

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