فرز البريد الوارد الذكي

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

1. shared_inbox_source

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

   The inbox or alias being triaged. The pattern reads from here and acts on each new message.

   شكل البيانات

   Email-style messages: sender, recipient list, subject, body, attachments, timestamp.
   يُملأ عادةً بواسطة

   • shared mailbox for info@, support@, hello@
   • distribution list that forwards to multiple people
   • alias inbox in a business email system
2. routing_taxonomy

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

   The categorization the pattern uses to decide where each message goes. Specific to the client, refined over time.

   شكل البيانات

   Categories with descriptions, routing destinations per category, sample messages exemplifying each category.
   يُملأ عادةً بواسطة

   • configuration file maintained by the engagement team and updated quarterly
   • small admin UI inside the pattern
   • internal wiki page listing the categories
3. routing_destinations

   مطلوبكتابةحدث

   The various places routed messages land. Different category, different destination.

   شكل البيانات

   Messages routed with their classification, summary, suggested owner. Destination format varies by type.
   يُملأ عادةً بواسطة

   • ticket queues in the helpdesk
   • channels in team chat
   • individual mailboxes with internal tags
   • tasks in the project management system
4. sender_context_lookup

   موصى بهقراءةطلب

   If the sender is a known customer, partner, or contact, fetch their context so routing and summary can reflect it.

   شكل البيانات

   Sender records with relationship type, recent activity, any active flags.
   إذا مفقود

   Routing accuracy drops about 20% for known senders whose context would have changed the destination (e.g. a VIP customer's inquiry routed as generic).
   يُملأ عادةً بواسطة

   • CRM lookup by email address
   • customer database with relationship data
   • vendor or partner directory
5. misroute_feedback_loop

   موصى بهكتابةحدث

   How recipients flag that a message was misrouted. Without this, the pattern drifts and no one can tune it.

   شكل البيانات

   Reports of misroutes: message ID, where it went, where it should have gone, optional reason.
   إذا مفقود

   Misroutes accumulate silently. Strongly recommend even a lightweight flag mechanism.
   يُملأ عادةً بواسطة

   • thumbs-down button on the routed message summary
   • a designated mailbox to forward misroutes to
   • a Slack reaction the team uses to flag bad routing