> 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/send-screen-recording.md).

# Send Screen Recording

- [Send a screen recording](https://docs.screendesk.io/send-screen-recording/send-a-screen-recording.md): Record and send a screen recording from the dashboard or your helpdesk, with audio and webcam options.
- [Add a call-to-action](https://docs.screendesk.io/send-screen-recording/add-a-call-to-action.md): Add a clickable button on your video to drive viewers to the next step.
- [Add a custom thumbnail](https://docs.screendesk.io/send-screen-recording/add-a-custom-thumbnail.md): Upload a custom thumbnail for a recording, or set a default thumbnail for your workspace.
- [Video editor](https://docs.screendesk.io/send-screen-recording/video-editor.md): How to cut, trim, or mute parts of your video
- [Share recordings](https://docs.screendesk.io/send-screen-recording/share-recordings.md): Different methods for sharing your recordings with viewers.
- [Chrome extension](https://docs.screendesk.io/send-screen-recording/chrome-extension.md): Record with the Chrome extension to draw on screen, highlight clicks, and blur sensitive content.
- [Troubleshooting](https://docs.screendesk.io/send-screen-recording/chrome-extension/troubleshooting.md): Solve common issues with the Screendesk Chrome extension by following these steps: restart your device, clear Chrome's cache, reinstall the extension, download troubleshooting data


---

# 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.screendesk.io/send-screen-recording.md?ask=<question>&goal=<user_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.