> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/intelligence-and-analytics.md). # Intelligence and Analytics - [Intelligence Overview](https://docs.concurrence.com/intelligence-and-analytics/intelligence.md): Per-interaction evidence, workspace analytics, dashboards, metric values, and the boundaries that determine their availability. - [Call Intelligence](https://docs.concurrence.com/intelligence-and-analytics/intelligence/call-intelligence.md): Terminal voice-call evidence, operational quality scoring, optional audio analysis, decision traces, and playback timelines. - [Analytics and Dashboards](https://docs.concurrence.com/intelligence-and-analytics/intelligence/analytics-dashboards.md): Workspace analytics, pipeline observability, entity inspection, dashboards, and the Insights Agent - with their freshness and evidence boundaries. - [Metric Store](https://docs.concurrence.com/intelligence-and-analytics/metric-store.md): The current metric catalog, custom-definition boundaries, dashboard behavior, query surface, and freshness semantics. - [Cost to Serve](https://docs.concurrence.com/intelligence-and-analytics/cost-to-serve.md): Understand workspace LLM usage and calculated cost, customer and staff access, and pricing and attribution limits. --- # 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.concurrence.com/intelligence-and-analytics.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.