Business API accelerator

Customer360

Create a governed customer context contract across CRM, ERP, service, commerce, SaaS, and approved operational data sources.

Customer contract explorer

Change the customer-context consumer

Inspect how one governed customer contract can expose different approved context while preserving source provenance.

Interactive product experience

Select a consumer profile to update the response boundary.

Business API acceleratorsSource systemsConsumersResult and contract
CRM, ERPEnterprise applicationsGET /v1/customers/{id}/context
CRM, DatabasesAI agents and copilotsidentity · service status · provenance
Source systemsAnalyticsapproved relationship attributes
Active scenario

Service app

Service application context

Identity, relationship status, and recent service context are available to an approved internal application.

Result and contract

Operation
GET /v1/customers/{id}/context
Fields
identity · relationship · service
Approved

Guided explanation

The customer problem

The customer problem

Customer-facing teams and applications assemble context differently from CRM, ERP, service, commerce, and regional systems.

What this enables

  • Reuse one governed customer context across channels.

  • Preserve source provenance and domain ownership.

  • Evolve participating sources without redefining every consumer.

Scope and qualification

  • The contract reflects each enterprise's approved identity, privacy, and access rules.

Source systems

CRMERPSaaS applicationsDatabases

Consumers

Enterprise applicationsAI agents and copilotsAnalyticsWorkflows and automation

One customer contract, designed around your approved context.

Customer360 does not prescribe a universal customer record. It gives each enterprise a stable interface for the identity, relationships, provenance, and operations its consumers are allowed to use.

Map the customer sources and consumers in your landscape.