SocialHub.AI

CRM

Accounts, contacts and service history

CRM is where the account, contact and service relationship lives. The managed Salesforce connector resolves CRM customers to the same verified member — with CRM-managed orders earning points and returns clawing back — while other CRMs connect through the governed API to enrich each email with per-recipient traits, a read-only lookup that never creates a member or exposes PII.

What lands on the member

The data this brings — and what it powers.

Customers → members

Accounts and contacts resolve to the one verified member by your own ID or email, so CRM contacts aren't a separate fragment.

Orders → points (Salesforce)

Orders managed in Salesforce earn points on the header total; returns and credit memos claw back, anchored to the original order.

Traits → email enrichment

Through the governed API, per-recipient traits (name, lifecycle, attributes) personalize email — a read-only lookup that never creates members or exposes PII.

Service history → context

The account relationship gives campaigns and next-best-actions the CRM context, on the live member record.

The CRM relationship and the loyalty record become one verified customer, not two.

In this category

CRM systems.

Managed connectors are configured in-app and open to a detail page. Native connectors and API integrations land on the same verified member through the same governed pipe.

Salesforce

Managed connector

Managed connector · fixture-validated — orders, customers and products via REST + SOQL.

HubSpot

Through the governed API

Through the governed API — read-only trait enrichment for email personalization.

Whichever path a system uses, it runs on one governed API — matched to the right member, harmless to retry, and locked to your data. See the developer guide →

Put crm data on one customer record.

400M+
50+
12+