> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/support-application.md). # Support Application ## Overview The BlueFletch Support Application is an Android-based application and background service designed to collect and send market-leading, device-specific data to the Google Cloud Platform. You can leverage Support Application features to gain greater visibility and control of critical, real-time data through the Support Analytics tab on the EMS web portal. This will help to manage and support Android-based device ecosystems more efficiently. * Collect 25+ hardware data points such as battery health, network, and vendor-exposed data every thirty minutes. * Collect data such as OS version, patches, reboots, restarts, installed app version, and app usage time for device validation. * Collect usage data, heartbeat events, and other custom data attributes through custom and third-party apps. * Store data in the cloud and view it from a customizable dashboard with KPIs and ad-hoc queries. * Send data to the GPC backend by default or feed into third-party analytics tools such as Splunk, Power BI, etc. Support Application equips end users with proactive self-service options and device-specific data for faster troubleshooting, less device downtime, and cutting back on help desk volume. How does Support Application help end users? * Device data is easily accessible for quick, self-guided diagnosis and repair. * Self-service password reset is readily available to reduce call times and help desk costs. * Easily open a ServiceNow ticket with relevant device information for expedited troubleshooting. {% embed url="" %} Support Agent {% endembed %} --- # 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.bluefletch.com/bluefletch-enterprise/product-guides/support-application.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.