Users and accounts
Represent the people, workspaces, subscriptions, roles, and companies that create customer support context.
Identity platform
Crisp Chat gives support and AI workflows a governed identity layer so every answer, report, and automation uses the same trusted account model.
Active account
Policy check
Can this agent see the account data this user is allowed to see?
Built for teams with real customer data
Represent the people, workspaces, subscriptions, roles, and companies that create customer support context.
Define the plan, payment state, onboarding milestone, feature usage, and recent behavior that should guide each reply.
Control who can see customer data, which AI workflows may use it, and how sensitive traits appear in the workspace.
Crisp Chat lets teams define customer identity once and use it across the inbox, AI drafts, reports, automations, and downstream tools.
The model connects product and business data without forcing agents to search five systems before replying.
Track changes to account traits, customer lifecycle fields, and routing rules before they affect support operations.
Manage common fields in the Crisp Chat workspace so non-engineers can understand the model they rely on.
Sync context from billing, CRM, product analytics, and internal APIs while keeping the Crisp Chat identity model stable.
Active account
Policy check
A shared model for every support workflow
The Crisp Chat catalog documents the fields and events that can appear in support workflows, so agents and AI know what each signal means.
Everyone can see who owns a field, where it comes from, and whether it is safe for support, AI, reporting, or automation.
Every customer signal has an owner and description, so teams know how to interpret account health, plan state, or intent tags.
Support can ask the right internal owner when a trait is unclear instead of guessing in front of the customer.
Click a signal and immediately inspect matching accounts, conversations, and support outcomes.
Active account
All your customer signals available in one place
Journey
Crisp Chat is built for customer data that needs care. Admins can restrict sensitive fields, private teams, report access, and AI visibility.
Support teams can move fast without exposing billing details, enterprise notes, or row-level customer data to the wrong audience.
Admins manage identity fields and policies. Members analyze, reply, and create reports within the permissions they are granted.
Hide sensitive signals such as revenue, payment risk, enterprise notes, or internal scoring from general views.
Create public or private spaces for support, success, sales, product, and leadership.
Active account
allow ai.draft
when user.role in ["support", "success"]
and account.privateRevenue == hidden
and signedIdentity == trueReview
Control customer context with precision
Your agents, dashboards, workflows, and internal tools can access governed Crisp Chat identity through clear APIs without rebuilding customer logic.
Define once in Crisp Chat, then power support automation, AI agents, escalation flows, and custom internal tools from the same model.
Power LLMs, agents, and custom AI use cases with customer context that respects Crisp Chat access rules.
Build exports, forecasting, renewal workflows, support scoring, or internal admin tools on top of the same account model.
Programmatically create sites, update traits, sync accounts, or fetch support summaries for custom workflows.
Active account
Policy check
Use customer context anywhere
How teams use it
Crisp Chat is designed for teams that need high engagement and careful data handling at the same time. The identity platform gives admins a single source of truth while still letting support teams move quickly in daily work.
Control authentication with Google, Microsoft, and enterprise identity providers as your team grows.
Prepare for SCIM and directory sync so support access follows your company structure.
Review who viewed, changed, exported, or used sensitive support context in AI workflows.
Support multiple products, regions, or business units with a consistent account model.
Use Crisp Chat to define identity, permissions, and account context before support AI starts answering for your business.