إنذار مبكّر للتجديد وخطر التسرّب

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

1. account_record_store

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

   Customer accounts being monitored, including the renewal date and current commercial status.

   شكل البيانات

   Account records with contract dates, renewal date, ARR/MRR, plan, owner. Pattern writes a risk score and reason codes.
   يُملأ عادةً بواسطة

   • CRM with account records and renewal dates
   • customer success platform
   • subscription billing system as the source of truth for accounts
2. product_usage_signal

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

   How customers are actually using the product. The single most predictive churn signal in most SaaS businesses.

   شكل البيانات

   Per-account usage metrics over time: active users, key actions, feature adoption, session frequency. Aggregated or detailed.
   يُملأ عادةً بواسطة

   • product analytics platform
   • data warehouse with usage tables
   • internal usage metrics dashboard
   • (for non-product businesses: project hours logged, deliverables shipped, etc.)
3. support_interaction_signal

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

   Support volume, sentiment, and resolution patterns per account. Rising tickets or unresolved issues are churn precursors.

   شكل البيانات

   Per-account support metrics: ticket volume trend, resolution time, sentiment of recent tickets, repeat-issue rate.
   يُملأ عادةً بواسطة

   • support system metrics
   • aggregated data from A1/A2 patterns if live
   • customer success notes archive
4. contact_health_signal

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

   Who's still at the account and engaged. Key contacts leaving is one of the strongest churn predictors.

   شكل البيانات

   Per-account contact list with role, last interaction, engagement level. Changes flagged when a key contact disappears.
   يُملأ عادةً بواسطة

   • CRM with up-to-date contact records
   • data from B2 hygiene pattern flagging contact changes
   • support system records of who's been opening tickets
5. payment_behavior_signal

   موصى بهقراءةدفعة

   Late payments, disputes, downgrades. Commercial signals that hint at intent.

   شكل البيانات

   Per-account payment events: invoice age, dispute flags, plan changes.
   إذا مفقود

   Pattern still produces good risk signals but misses commercial-side cues. Recommend at least monthly visibility.
   يُملأ عادةً بواسطة

   • billing system with payment status
   • accounts receivable system
   • finance team's monthly account health report
6. csm_alert_destination

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

   Where the customer success team sees flagged accounts. Must be in their normal working surface, not a separate dashboard.

   شكل البيانات

   Per-account risk flag with score, reason codes, evidence, suggested intervention. Appears in CSM's daily view.
   يُملأ عادةً بواسطة

   • field on the account record in CRM with sorting and filtering
   • dedicated risk view in the customer success platform
   • Slack alerts for accounts crossing thresholds
7. intervention_outcome_loop

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

   Feedback on whether interventions worked, used to tune signal weights over time.

   شكل البيانات

   Per-flagged-account outcome: did they renew, did intervention happen, what was the action taken.
   إذا مفقود

   Pattern produces flags but can't learn which signals predict actual churn. Strongly recommend closing the loop.
   يُملأ عادةً بواسطة

   • monthly churn retrospective with outcome tagging
   • renewal outcome data fed back from billing
   • structured CSM playbook outcomes