customer-360

Consolidate customer data across CRM, finance, support, marketing, and product systems into a unified view.

2|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/erphq/skills --skill customer-360
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: customer-360
Source: https://github.com/erphq/skills/tree/main/departments/sales-crm/03-org-1k-plus/customer-360
Command: npx skills add https://github.com/erphq/skills --skill customer-360

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill brings together scattered customer data into a single, trustworthy view that highlights health signals, renewal risk, and expansion opportunities across CRM, finance, support, marketing, and product systems.

Core Features & Use Cases

  • Unified Customer View: aggregates data from CRM, finance, support, marketing, and product into one source of truth.
  • Health Scoring & Signals: computes a customer health score and surfaces cross-sell, renewal, and risk signals for action.
  • Cross-Department Workflows: enables segmentation, alerting, and collaborative actions for sales, success, and finance teams.

Quick Start

Integrate all relevant customer data sources to produce a single Customer 360 view and compute a health score with cross-sell signals.

Frequently Asked Questions about customer-360

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a customer 360 unified view and how does it surface health signals?

A customer 360 unified view consolidates data from CRM, finance, support, marketing, and product systems into a single source of truth. It applies a consistent health scoring model to aggregate cross-source events and surface actionable risk or expansion signals.

How do I build a customer health score model for renewals and cross-sell campaigns?

Build a customer health score model by integrating cross-functional data sources to establish customer linkage. This aggregates cross-source events into a dashboard-ready data model that supports segmentation, timelines, and escalation workflows for timely renewal and upsell alerts.

Can I use cross-source event aggregation to detect renewal risk across multiple platforms?

Yes, cross-source event aggregation consolidates customer activities from CRM, finance, and support platforms to detect renewal risk. This unified view computes health scores and triggers timely alerts for success teams to initiate escalation workflows.

What's the best way to unify scattered CRM and finance data for actionable customer insights?

The best way to unify scattered data is to consolidate CRM and finance records into a dashboard-ready data model. This establishes a consistent customer linkage across sources, enabling segmentation and actionable insights for cross-department sales workflows.

Do I need a consistent health scoring model before integrating cross-functional customer data?

Yes, a consistent health scoring model is required to validate cross-functional customer data. Customer linkage across CRM, support, and marketing sources must be established first so the computed health score accurately surfaces cross-sell and risk signals.

When should I not use a unified customer data model for signal detection?

Avoid using a unified customer data model if cross-source customer linkage cannot be consistently established across CRM, finance, and support systems. Without reliable data integration, health scoring and signal detection will produce inaccurate risk and cross-sell insights.