OntoBoomOntoBoomHub
← Hub

@ontoboom/customer-360

Customer 360: a unified, vendor-agnostic schema for the data agents need to reason about a customer end-to-end. Identity + accounts + subscriptions + touchpoints across CRM, marketing, support, billing, product analytics, and consent. Designed to sit on top of any warehouse (Snowflake / BigQuery / Postgres) where these signals already live.

31
Classes
27
Object properties
105
Data properties
0
Individuals

Connect this ontology

● Checking…
MCP endpoint
https://mcp.ontoboom.com/o/@ontoboom/customer-360@0.1.0
{
  "mcpServers": {
    "ontoboom": {
      "url": "https://mcp.ontoboom.com/o/@ontoboom/customer-360@0.1.0",
      "transport": "sse"
    }
  }
}

Two manifest-derived tools are exposed in this iteration:list_entities anddescribe_entity. More tools (find_relationship, enumerate_values) ship as followups.

README

@ontoboom/customer-360

The schema agents need to answer questions like:

"Show me Pro-plan customers who opened a ticket in the last 30 days, haven't logged in this week, and have an unpaid invoice."

It pulls together identity, account, subscription, support, marketing engagement, behavioural events, and consent into one ontology that maps cleanly into a typical warehouse.

Coverage

  • Person, Household, Account — identity at three levels of granularity
  • Email, Phone, Address — typed contact records, with consent and verification status
  • Identifier — external IDs (Stripe customer id, Salesforce contact id, Segment anonymous id, etc.) so you can join across vendor silos
  • Subscription, Product, Plan, PaymentMethod, Invoice — the billing side
  • Touchpoint (super-class) split into EmailTouchpoint, AdImpression, WebSession, AppSession, SupportTicket, CallRecording, NPSResponse
  • Event — behavioural product events (page_view, feature_use, conversion) keyed to an Account or Person
  • Consent — per-purpose marketing / analytics / sales-share consent with timestamp and source
  • Segment, Audience — derived membership for personalization
  • LifecycleStage — ordered funnel stage (lead → opportunity → customer → champion → churned)
  • Score (LTV, CSAT, NPS, churn probability) attached to a Person or Account

SHACL highlights

  • Email matches a permissive regex; phone matches an E.164 pattern when present
  • Subscription.status enumerated trialing | active | past_due | paused | canceled | expired
  • Identifier.system enumerated against known vendors (Stripe, Salesforce, HubSpot, Segment, ...)
  • Consent must carry a purpose, a source, and a granted-at timestamp
  • LifecycleStage has an integer ordering so funnel math is unambiguous

Forking

This pack is designed to be customized — most teams add 5–10 verticals on top (loyalty programs, household roll-ups, B2B account hierarchies, etc.). Fork, extend, publish under your own namespace.

Reviews

Sign in to review

No reviews yet · Be the first to review.

Sort: