> ## Documentation Index > Fetch the complete documentation index at: https://docs.outlit.ai/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Outlit is the product that monitors customers and completes approved customer work. The customer context interfaces are the API, CLI, MCP server, and skills. Canonical references on this site: /api-reference/introduction for API concepts and authentication, /openapi.json for the public API contract, /cli/overview for the CLI, /ai-integrations/mcp for MCP. Prefer the `outlit` CLI or MCP tools for agent tasks; cite page sources when answering. # Customer context graph > See how connected sources become customer profiles, evidence, and attention items. 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
Scroll sideways or use arrow keys. Connected SDKs, integrations, and conversations feed a graph of visitors, contacts, accounts, relationships, activity, and facts; customer profiles and developer interfaces use that context. Connected SDKs, integrations, and conversations feed a graph of visitors, contacts, accounts, relationships, activity, and facts; customer profiles and developer interfaces use that context. Connected SDKs, integrations, and conversations feed a graph of visitors, contacts, accounts, relationships, activity, and facts; customer profiles and developer interfaces use that context. Connected SDKs, integrations, and conversations feed a graph of visitors, contacts, accounts, relationships, activity, and facts; customer profiles and developer interfaces use that context.
The diagram shows how connected sources feed customer profiles. Outlit uses those profiles and their evidence when it prepares churn cases and renewal briefs. | Source | What it adds | | - | - | | Outlit Browser SDK and Outlit server SDKs | Website visits, identified people, and product events you instrument | | PostHog or Mixpanel integrations | Product activity and usage trends imported into Outlit | | Stripe | Subscription state, billing status, and revenue | | Salesforce, HubSpot, or Attio | Account records, contacts, owners, deals, and renewal dates | | Gmail, Slack, Granola, Gong, Fireflies, or Google Calendar | Conversations and meetings | | Pylon | Support tickets and escalations | | Clerk or Supabase Auth | User identity and sign-in activity | Connect sources in the [Outlit app](/integrations/overview). 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](/concepts/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](/concepts/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](/cli/overview), [MCP](/ai-integrations/mcp), and [API](/api-reference/tools) let authorized agents and applications query customer context. Their access follows the same customer and workspace permissions. ## Next steps Review profiles and source coverage. Understand activation, engagement, and billing. See how visits and events link to people. Add the sources Outlit uses for monitoring. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.