> 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/helpdesk-integrations/helpscout/content-library.md).

# Content library

The Content Library enables users to share existing videos directly from the ticket or chat sidebar in HelpScout. This feature allows you to easily access and distribute relevant video content to users.

<figure><img src="/files/yMUY2kqTCz9dw4i3c3As" alt="share video from the content library flow gif"><figcaption></figcaption></figure>

### Direct Sharing

Share videos from the Content Library directly within HelpScout tickets or chat sidebars, providing users with immediate access to helpful video resources.

### Search Functionality

Search for videos by **tags** or **titles** to quickly locate the specific content you need.

The Content Library is a valuable tool for any support team looking to improve their service quality and efficiency by leveraging the power of video.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.screendesk.io/helpdesk-integrations/helpscout/content-library.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
