تنظيف نظام إدارة العملاء وإثراؤه تلقائياً

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

1. crm_record_store

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

   The CRM whose records are being cleaned. The pattern reads and writes here with care: it never deletes, only flags or merges with audit trail.

   شكل البيانات

   Contact, company, and deal records with standard fields plus custom fields. Pattern needs write access for updates and a way to log the change source.
   يُملأ عادةً بواسطة

   • CRM system with API write access
   • internal sales database the team uses as a CRM
   • spreadsheet acting as a CRM (degrades pattern value significantly; consider this a precursor)
2. enrichment_data_source

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

   Where missing fields get filled from. Could be one provider or several stacked.

   شكل البيانات

   Per-contact and per-company data: job titles, company size, industry, funding, recent news. Source attribution and confidence per field.
   يُملأ عادةً بواسطة

   • subscription data enrichment service
   • free LinkedIn or company-data lookup APIs
   • internal historical activity logs
   • import of an enrichment file from a list provider
3. change_audit_log

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

   Every change the pattern makes is logged here. Critical for trust: a CRM that quietly changes data is worse than one that doesn't try.

   شكل البيانات

   Per-change entries: record affected, field changed, old value, new value, source of new value, confidence, timestamp.
   يُملأ عادةً بواسطة

   • audit log inside the CRM
   • separate log table the pattern writes to
   • structured change feed posted to a team channel
4. low_confidence_review_queue

   مطلوبكتابةدفعة

   Changes the pattern isn't confident enough to make automatically go here for a human to approve or reject.

   شكل البيانات

   Proposed changes with confidence scores, evidence, and approve/reject/edit-and-approve actions for a human.
   يُملأ عادةً بواسطة

   • review queue inside the CRM
   • dedicated review UI built for the pattern
   • weekly digest emailed to RevOps with batched changes
5. merge_authority

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

   Who or what authorizes record merges when duplicates are found. Merges are destructive in effect even if the audit trail exists.

   شكل البيانات

   Merge proposal with duplicate records, similarity score, suggested primary record, and human or rule-based decision.
   يُملأ عادةً بواسطة

   • RevOps reviewer with a merge queue
   • rule-based auto-merge above a confidence threshold (only for high-confidence cases)
   • team lead reviewing weekly batches