How to Build Customer Health Scoring Using CRM, Support, and Billing Data
March 24, 2026
Customer health scoring is a feature inside a SaaS product that evaluates the status of a customer account using signals from CRM, support activity, and billing data. It helps teams identify which accounts are healthy, at risk, or likely to churn.
To build this, your product needs access to multiple data sources at once. Account data lives in CRM platforms like Salesforce or HubSpot, support interactions are tracked in tools like Zendesk, and billing data is managed in systems like Stripe.
Each platform exposes different APIs and schemas. Unified provides category-specific APIs that allow your product to retrieve CRM, ticketing, and payment data through consistent objects, making it possible to compute health scores without building separate integrations for each provider.
Why SaaS Products Build Customer Health Scoring
Customer health scoring is a core capability in many B2B SaaS products.
Examples include:
- Customer success platforms
- Revenue intelligence tools
- Churn prediction products
- Account management tools
- AI customer assistants
These products help teams answer questions like:
- 'Which accounts are at risk?'
- 'Which customers are highly engaged?'
- 'Who should we prioritize this week?'
Without a unified view of CRM, support, and billing data, these insights require manual analysis across multiple tools.
Common Customer Health Use Cases
Customer health scoring typically supports several workflows.
Churn prediction
Identify accounts with declining activity or negative signals.
Account prioritization
Help customer success teams focus on high-risk or high-value accounts.
Customer segmentation
Group customers into health categories such as healthy, watch, or at risk.
Renewal tracking
Monitor subscription status and upcoming renewal risk.
Engagement analysis
Evaluate customer activity across support, sales, and communication channels.
Unified Categories Used
Customer health scoring combines data from multiple categories.
| Category | Description | Key Objects |
|---|---|---|
| CRM | Account, deal, and activity data from platforms like Salesforce | contact, company, deal, event |
| Ticketing | Support interactions from platforms like Zendesk | ticket |
| Payments | Subscription and transaction data from platforms like Stripe | payment, subscription |
Using category-specific APIs allows your product to retrieve data across these sources without writing provider-specific logic.
Unified Objects and Key Fields
CRM Objects
CRM data provides account-level context and engagement history.
| Object | Key Fields | Purpose |
|---|---|---|
| Contact | name, emails, company_ids | Customer identity |
| Company | name, domains | Account grouping |
| Deal | amount, stage_id, probability, closing_at | Pipeline context |
| Event | type, created_at, contact_ids | Activity history |
These objects allow your product to measure sales activity and engagement.
Ticketing Objects
Support data provides insight into customer experience.
| Object | Key Fields | Purpose |
|---|---|---|
| Ticket | subject, description, status, priority, created_at, updated_at | Support interactions |
Important signals include:
- number of open tickets
- ticket resolution time
- ticket priority
- frequency of support requests
These signals help identify frustrated or struggling customers.
Payments Objects
Billing data provides financial signals.
| Object | Key Fields | Purpose |
|---|---|---|
| Payment | total_amount, currency, contact_id | Payment activity |
| Subscription | status, current_period_end_at, interval | Recurring revenue |
Important signals include:
- active vs canceled subscriptions
- renewal dates
- payment activity
- billing frequency
These signals help determine account stability.
Connecting Customer Data Sources
Customers connect their CRM, support, and billing platforms using Unified Connect.
Typical process:
- Your application launches the authorization flow.
- The user selects integrations such as Salesforce, Zendesk, or Stripe.
- The user authorizes access.
- Unified returns a connection_id.
Your application stores:
user_id → connection_id
All API requests reference this identifier.
Retrieving Customer Data
Your application retrieves data from each category using Unified endpoints.
CRM:
GET /crm/{connection_id}/contact
GET /crm/{connection_id}/company
GET /crm/{connection_id}/deal
GET /crm/{connection_id}/event
Ticketing:
GET /ticketing/{connection_id}/ticket
Payments:
GET /payment/{connection_id}/payment
GET /payment/{connection_id}/subscription
These endpoints return normalized objects across providers.
Mapping Data to Health Signals
Customer health scores are built by combining signals across categories.
CRM signals
- recent activity (
event.created_at) - deal progression (
stage_id) - engagement frequency
Support signals
- number of open tickets
- ticket priority
- time to resolution
Billing signals
- subscription status
- upcoming renewal (
current_period_end_at) - recent payments
These signals are combined to create a health score.
Example Health Score Model
A simple scoring model might look like this:
health_score = (engagement_score * 0.4) + (support_score * 0.3) + (billing_score * 0.3)
Where:
- engagement_score is based on CRM activity
- support_score is based on ticket behavior
- billing_score is based on subscription status
Example rules:
- Active subscription → positive signal
- Overdue or canceled subscription → negative signal
- High ticket volume → negative signal
- Recent activity → positive signal
Building a Health Scoring Pipeline
A typical implementation follows these steps.
1. Retrieve data
Fetch CRM, ticketing, and billing data using Unified APIs.
2. Aggregate signals
Group data by account using contact and company relationships.
3. Calculate metrics
Compute engagement, support, and billing indicators.
4. Generate scores
Apply a scoring model to produce a health score.
5. Store results
Persist scores in your application database.
6. Display insights
Show health indicators in dashboards or account views.
Keeping Health Scores Updated
Customer data changes frequently, so scores must be recalculated regularly.
Unified provides event-based updates across categories.
Examples include:
- CRM updates (deal changes, new activity)
- ticket updates (new or resolved tickets)
- payment and subscription changes
Applications can subscribe to webhook events or use timestamps such as updated_at to trigger recalculation.
Supported Platforms
Unified supports a wide range of integrations across categories.
Examples include:
CRM (47+ integrations)
- Salesforce
- HubSpot
- Pipedrive
- Zoho CRM
Ticketing platforms
- Zendesk
- Jira Service Management
- Freshdesk
Payments platforms (16 integrations)
- Stripe
- PayPal
- Square
This allows customer success tools to support many customer environments.
Why This Matters
Customer health scoring requires combining data from multiple platforms.
Without a unified approach, developers must build separate integrations for CRM, support, and billing systems.
Unified provides:
- normalized objects across CRM, ticketing, and payments
- consistent API endpoints for retrieving data
- real-time access to source data
- unified authentication and webhook support
This allows product teams to build customer success features without managing integration complexity.
Start building customer health scoring across CRM, support, and billing platforms today.