> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/support-center-framework/support-center-framework-overview.md). # Support Center Framework Overview The Support Center Framework is an framework on which you can build targeted applications, like you can with the [Assessment Framework](/release-9/design-considerations-and-frameworks/frameworks/assessment-framework.md), [Web Services Framework](/release-9/design-considerations-and-frameworks/frameworks/web-services-framework.md), [Starter Application Framework](/release-9/design-considerations-and-frameworks/frameworks/application-starter-framework.md), and [Visual Navigation Framework](/release-9/design-considerations-and-frameworks/frameworks/visual-navigation-framework.md). More specifically, you can use the Support Center Framework to build an interactive application that helps your customers to troubleshoot or analyze problems; for example, a malfunctioning device or piece of equipment at your company. You model content that walks your users step-by-step through the procedure to narrow down possible causes/root causes for a problem. Along the way, you can include instructions to guide users on where to look or what actions to take to confirm a problem area. The Predictive Analytics feature in the Support Center Framework enhances guided diagnostics and troubleshooting applications by allowing the designer to indicate specific outcomes or root causes within the modeled diagnostic pathways. Once deployed, the AI automatically tracks how users traverse the decision pathways to arrive at and indicate particular root causes. Additionally, using historical data, your system can display predicted possible causes. It will also indicate the most likely of the cause, based on previously confirmed causes. ### Architecture Diagram The above architecture diagram gives a flavor of the process and components of a typical Support Center Framework application that includes: 1. users answering questions, making observations and being given instructions 2. the application constantly assessing the probability and confidence of potential causes. Any cause with zero probability of being chosen (due to the logic model) is removed from the list 3. When all causes bar one are eliminated, or when the user has sufficient confidence, they select a cause from the remaining list 4. In confirming the cause, the user provides any additional information requested by the model 5. User SUBMITS their response, and the cause/observations update the statistics for future sesssions In the remaining articles in this section of the Community Portal, each part of the Support Center Framework application is outlined in more detail, along with various customization points. Click on the last breadcrumb at the top to see a list of relevant topics. --- # 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://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/support-center-framework/support-center-framework-overview.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.