Customer context graph

Outlit connects customer data from billing, product usage, CRM, conversations, and support. It links people to customers and keeps a timeline of what happened and where each piece of evidence came from. Your team can review that context in Customers and Attention; authorized agents can query it through the CLI, MCP, and API.

​

From sources to customer work

The diagram shows how connected sources feed customer profiles. Outlit uses those profiles and their evidence when it prepares churn cases and renewal briefs. Connect sources in the Outlit app. Churn monitoring needs billing and product activity for useful coverage; the Outlit Browser SDK adds the landing page, referrer, UTM data, and anonymous website visits before signup. Identifying the browser visitor links that history to later customer activity. Check Responsibilities → Churn for your workspace’s actual monitoring status.

​

How records become a profile

Identity resolution links an anonymous visitor to a known person after they identify. A company email domain, explicit customerId, or connected account records can link that person to a customer. Ambiguous matches wait for review rather than being merged automatically. A customer’s Coverage tab shows which sources support its profile. The activity timeline records events in time order. Each source can also support a fact, such as declining usage, a support escalation, a competitor mention, or a change in a key contact. Public fact results include occurredAt, status, and available provenance fields such as sourceType, sourceId, sourceOccurredAt, sourceQuote, and permalink. Read the source time and status before relying on an older finding.

​

Customer journey and billing

A person’s product journey can be Discovered, Signed Up, Activated, Engaged, or Inactive. A customer’s billing status can be None, Trialing, Paying, Past due, or Churned. These describe different parts of the relationship. Billing comes from a verified integration such as Stripe. You choose an ordinary product event for activation. The first matching event records activation once for each eligible resolved person and company, independently; later matches leave the recorded timestamp unchanged. SDKs and analytics integrations send ordinary events, and Outlit derives activation from the configured event. See Customer journey for the exact stages and setup.

​

Where to use the context

• Customers shows profiles, people, coverage, timelines, and facts.
• Attention shows churn and renewal situations that need a person, with evidence and an approach when available.
• The CLI, MCP, and API let authorized agents and applications query customer context. Their access follows the same customer and workspace permissions.

​

Next steps