> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/getting-started/pylonboarding/account-intelligence.md). # Account Intelligence Use Account Intelligence to get full customer context
*** ## Overview Account Intelligence in Pylon brings together everything your support and success teams need to understand and engage with customers. It consolidates conversations, call recordings, custom fields, notes, analytics, and other custom data into curated views of customer context.
Use Account Intelligence to: * Access the full history of customer conversations, calls, tickets, and more * Prep faster for meetings or escalations, collaborate on key accounts with AI [Broken mention](broken://pages/Kkm8NVxa0IVfdeMZHL9w) * View important information on an account like `Tier`, `ARR`, or `Owner` * Understand recent trends in sentiment or customer health *** ## Setup {% embed url="" fullWidth="true" %} *** ## Use cases * Prepping for customer meetings * Summarize account activity from the past 30 days * Review open tickets, feature requests, what happened on the latest call, etc. * Collaborating across teams * Use shared notebooks to track QBR prep, onboarding tasks, or escalations * Onboard new team members onto customer context easily * Allow leadership to self-serve context on accounts * Tracking customer health * Monitor sentiment shifts and AI-tagged churn risks * Embed analytics or dashboards to track usage and outcomes * CRM sync * Sync fields like status, stage, or renewal date from your CRM * Keep account context up to date without switching tools *** ## Best practices * Use custom fields strategically * Map key metadata like tier, plan, and region to help route and prioritize * Create notebooks for high-value accounts * Use blocks like AI summaries, analytics, and notes to build shared context for different use cases * Use AI summaries to move faster * AI can give you a fast overview with citations so you can prep for calls quickly * Enable call recorders * Connecting a [Call Recording](/pylon-docs/integrations/call-recording.md) integration gives your account Intelligence view a lot more context from all of your customer meetings *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.usepylon.com/pylon-docs/getting-started/pylonboarding/account-intelligence.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.