> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/screen-recorder/getting-started/use-cases.md). # Use Cases Walkthroughs, customer support, product feedback, and troubleshooting with Screen Recorder. Use Screendesk Screen Recorder to explain what happened, show someone how to do something, or collect visual feedback. ## Walkthroughs and onboarding Record a tab or desktop workflow. Add webcam video and microphone narration to guide the viewer through the steps. [Review the recording](/screen-recorder/review-and-share.md) before sharing its link. ## Customer support Show a customer how to complete a task, or request a recording through a [recording link](/screen-recorder/record-and-capture/recording-links.md). Supported [helpdesk integrations](/screen-recorder/customer-support-integrations/intercom.md) let agents add recording links to conversations. ## Product feedback Capture a screenshot, annotate the area you want to discuss, and add a description. Keep feedback and discussion together with [comments](/screen-recorder/debug-a-capture/collaboration/comments.md). ## QA and troubleshooting Record reproduction steps or save recent activity with [Instant Replay](/screen-recorder/record-and-capture/instant-replay.md). Attached browser diagnostics help teammates investigate console errors, network requests, and the browser environment. Bugs are one use case: the same tools work for demonstrations, feedback, and handovers. ## Finish later Keep an unfinished capture in [Drafts](/screen-recorder/review-and-share/drafts.md). Drafts remain local and expire after seven days; upload captures you want to keep or share. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.screendesk.io/screen-recorder/getting-started/use-cases.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 `build a script that syncs our docs to a CMS` 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.