Cc Crm Updater

CRM Updater

Maintains CRM accuracy by automatically logging activities, updating fields, and syncing data from connected systems. The unglamorous but essential data hygiene layer that every other skill depends on -- health scores, engagement tracking, renewal forecasting, and reporting are all only as good as the CRM data underneath them.

This is a data operations skill. It writes structured data to the CRM. It does not make judgment calls about what data means -- it ensures the data is there, accurate, and current.

When to Run

• Continuous: Syncs activities as they occur (email sent, call completed, ticket resolved, meeting held)
• Scheduled: Daily reconciliation pass to catch missed updates, flag inconsistencies, and report on data health
• On-demand: When a CSM requests a data refresh for a specific account

Core Execution Logic

Step 1: Auto-Log Activities from Connected Systems

As events occur across connected systems, log them to the CRM activity record:

Filtering rules: Not everything should be logged. Automated marketing emails, system notifications, auto-replies, and background API calls are excluded. Only human-meaningful interactions create CRM activity records.

Step 2: Update Account-Level Fields

Keep CRM fields current from upstream skill computations:

Step 3: Reconciliation and Hygiene (Daily Pass)

Every day, scan the CRM for data health issues:

Step 4: Protect CSM-Entered Data

Critical principle: the agent never silently overwrites data that a CSM has manually entered.

Step 5: Generate Data Health Report

Daily summary for CS Ops, weekly summary for CS leadership:

{
  "report_date": "2026-03-10",
  "activity_logging": {
    "activities_logged_today": 47,
    "by_channel": { "email": 22, "meeting": 8, "call": 5, "support": 7, "product_event": 5 },
    "duplicates_skipped": 3,
    "logging_errors": 0
  },
  "field_updates": {
    "fields_updated_today": 23,
    "health_scores_written": 42,
    "lifecycle_stage_changes": 1,
    "conflicts_flagged": 2
  },
  "reconciliation": {
    "accounts_scanned": 142,
    "accounts_with_flags": 5,
    "flags": [
      {
        "account": "Beta Inc",
        "flag": "activity_gap",
        "detail": "No recorded activity in 35 days. Last touch: email on Feb 3",
        "recommended_action": "CSM review -- verify engagement status",
        "priority": "high"
      },
      {
        "account": "Gamma Corp",
        "flag": "lifecycle_stage_conflict",
        "detail": "Stage is 'Onboarding' but account has 8 months of active usage",
        "recommended_action": "CSM or CS Ops update lifecycle stage to 'Active'",
        "priority": "low"
      }
    ]
  },
  "data_health_score": {
    "overall": 0.94,
    "by_dimension": {
      "activity_completeness": 0.97,
      "field_freshness": 0.95,
      "required_field_coverage": 0.91,
      "contact_accuracy": 0.93
    }
  }
}

Handoff to Human

Confidence and Limitations

• High confidence for activity logging from structured sources (email, calendar, support) -- deterministic data writes with defined deduplication logic
• High confidence for field updates from upstream skills -- the agent writes what the skill computed. If the computation is wrong, that is the upstream skill's issue, not the CRM updater's
• Medium confidence for reconciliation flag relevance -- the flags are based on defined rules, but not every flag requires action. An activity gap on an SMB account with a quarterly cadence is expected, not concerning
• Low confidence for conflict resolution between agent-computed and CSM-entered values. The agent cannot determine which is correct -- it can only flag the discrepancy. The CSM decides
• Cannot log activities that happen outside connected systems. In-person meetings, phone calls not through the platform, Slack conversations, WhatsApp messages -- none of these appear unless the CSM logs them manually. This is a fundamental coverage gap that the reconciliation pass cannot fill
• Cannot ensure CSMs log their own observations and notes. The skill automates what is system-observable. The richest CRM data -- the CSM's qualitative assessment, relationship read, and strategic notes -- still requires human input

Dependencies

Required:

• CRM API (read/write access to account, contact, activity, and custom field objects)

Strongly recommended:

• Email integration (for email activity logging)
• Calendar integration (for meeting logging)
• Call platform (for call logging)
• Support platform (for ticket event logging)
• All Book Intelligence skills (for field update sources)
• Product analytics (for usage event summaries)

Downstream consumers:

• Every skill that reads from CRM -- this skill ensures the data they consume is accurate and current
• bi-health-score, bi-risk-detector, bi-usage-monitor (depend on CRM field freshness)
• ra-engagement-tracker (depends on activity log completeness)
• lo-renewal-manager (depends on contract field accuracy)
• CS Ops (reconciliation flags and data quality metrics)
• CSMs (stale data and conflict alerts)

References

• references/sync-rules.md -- Activity logging rules, field update policies, deduplication logic, and conflict resolution procedures