# Core Concepts ## **Overview** CX Analyst is a leadership-facing intelligence product within the IFS Loops platform. It is designed to help CX and Support leaders answer operational questions about customer issues, support performance, and account impact by connecting data from help desk ticketing systems and CRM platforms. Rather than requiring manual analysis or custom reporting, CX Analyst allows leaders to ask business questions directly and receive answers grounded in ticket and account context. ## **How It Works** CX Analyst ingests data from connected help desk and CRM systems and links individual tickets to the customer and account records they belong to. This linkage means insights reflect the full account context of a given issue, not just the isolated ticket. Leaders can then ask questions across this connected data set using the platform's question-driven interface. CX Analyst uses purpose-built pipelines for each CX use case on the IFS Loops platform, ensuring the analysis is structured around the specific questions CX and support organizations need to answer. The setup process follows four steps: connecting and ingesting data from the help desk and CRM, validating that the ingested data is complete and accurate, linking tickets to customer and account context, and applying the appropriate use-case pipeline. ## **Key Features** **Account-Linked Ticket Analysis** CX Analyst Connects help desk tickets to CRM account records from platforms such as HubSpot, Salesforce, and others. This means questions about customer issues can be answered with full account context — including customer tier, history, and relationship data — rather than treating each ticket as an isolated event. **Question-Driven Interface** Leaders interact with CX Analyst by asking business questions in plain language. The system returns answers grounded in the connected ticket and account data rather than requiring users to build queries, pull reports, or wait for analyst support. **Cross-Organizational Intelligence** CX Analyst is designed to serve multiple levels of the CX organization. At the leadership level, it supports evidence-based decisions about customer issues, trends, and account impact. At the team level, it gives frontline staff access to the same account context leadership uses, reducing gaps between what agents see and what executives interpret. At the organizational level, it creates a consistent source of truth for VOC discussions, escalation reviews, and cross-functional conversations. **VOC Theme Analysis** CX Analyst surfaces patterns in what customers are reporting across cases and conversations, identifies why certain themes are escalating, and provides the underlying evidence behind VOC narratives — enabling teams to align on customer feedback based on data rather than interpretation. **Support Execution Visibility** CX Analyst can identify where teams are getting stuck across the ticket lifecycle and surface what resolution patterns from closed tickets suggest about the most effective paths to resolution for common issue types. ## **Supported Integrations** CX Analyst connects with CRM platforms including HubSpot and Salesforce, help desk ticketing systems, and 65+ enterprise tools spanning knowledge, collaboration, and data platforms. ## **CX Analyst in Context** CX Analyst is built on the same data foundation used across IFS Loops CX use cases, making it compatible with AI Autopilot, Agent Assist Copilot, and Auto QA Analyst as part of a connected CX intelligence layer. *** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://kb.theloops.io/cxplatform/ifs-loops-cx-platform/cx-analyst/core-concepts.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.