> For the complete documentation index, see [llms.txt](https://docs.apruv.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apruv.io/apruv-field-app-guide/introduction.md). # Introduction This is the official documentation for the Apruv Field Performance App. Use this guide to learn how to track your performance, send proof of service, and collect customer feedback after each service. ### What the app does The Apruv Field App supports field technicians by enabling: * Real-time service documentation * Proof of service with media * Customer feedback collection * Optional tipping functionality * Performance metric tracking * Reward-based incentive visibility The app also automatically syncs the following with your field service software: * Scheduled routes * Completed services * Service notes * Media uploads * Performance data ### What this guide covers * Downloading and accessing the mobile application * Managing your profile, password, and notification settings * Linking your bank account for tip deposits * Navigating the Home, Wallet, Feedback, Rank, and Service tabs * Documenting services using photos, videos, and notes * Understanding the customer feedback flow * Reviewing your performance metrics and leaderboard rankings * Troubleshooting common issues > **Not covered:** Administrative setup or system configuration ### Key terms **KPI** is a Key Performance Indicator used to measure technician performance. **Proof of Service** is media and notes sent to customers confirming a completed service. **Leaderboard** is a ranking of technicians based on performance metrics. --- # 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.apruv.io/apruv-field-app-guide/introduction.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.