> 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/hubspot/request-via-sidebar.md).

# In tickets

Request a recording, record a response, share a library video, start a video call or send a booking link from a HubSpot ticket.

The Screendesk card is in the sidebar of HubSpot's help desk tickets. Each action copies a link or opens Screendesk: you paste the link into your reply and send it yourself. Nothing is sent for you.

{% embed url="<https://app.screendesk.io/recordings/e33440f8-f531-4009-bdec-fe776930b790>" %}

## Ask a customer for a recording

1. Open the ticket and find **Screendesk** in the sidebar. The first time, click **Get started**.
2. If your workspace has websites with the Screendesk snippet, choose under **Record on**, below **Request a recording**, where the customer records.
3. Click **Request a recording**. HubSpot says **Recording request link copied**: paste it into your reply, say what you'd like the customer to show, and send.

The customer records in their browser, with no account or install, reviews the recording and submits it. Screendesk then adds a **New Screen Recording Received** note to the ticket with a link to the recording. The note is internal. If the ticket was closed, it reopens, in your pipeline's **Waiting on us** stage if it has one.

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2Fxdqjsxn2kLCeq96vrxNs%2Fhubspot-ticket-note.png?alt=media" alt="The New Screen Recording Received note on a HubSpot ticket"><figcaption></figcaption></figure>

{% hint style="warning" %}
Copy a fresh link on each ticket. The link belongs to the ticket it was copied from, so if you reuse it elsewhere, the recording goes to the first ticket. For a link you can save, see [Snippets](https://docs.screendesk.io/helpdesk-integrations/hubspot/snippets.md).
{% endhint %}

## The other actions

* **Record a response**: opens the recorder in a new tab. Record your explanation, submit it, then copy the share link it shows into your reply. It doesn't add a note to the ticket.
* **Start a video call**: copies a call link for your reply. Open it yourself to join. If the call is recorded, the recording lands on the ticket as a note. It's available on Pro and Enterprise, for roles that can host calls. See [Video calls](https://docs.screendesk.io/video-calls/start-a-video-call.md).
* **Send a booking link**: find a booking link by title or host and click **Copy link**. The customer picks a time. See [Booking links](https://docs.screendesk.io/scheduling/create-booking-links.md).
* **Share from library**: search by title or type `#` and a tag, and click **Copy link** next to the video. Only [reusable videos](https://docs.screendesk.io/send-screen-recording/adding-video-to-the-library.md) appear, and the customer can only open one if its sharing settings allow.

## Recordings in the card

Under the actions, the card lists the customer's recordings (**From this customer**) or the ticket's (**On this ticket**), as set under **Recordings in the card** in Screendesk. **Copy link** puts one in your reply when the customer can open it; otherwise the row says **Team only**, or **Processing** while it's being prepared. The link under the list opens them all in Screendesk.

When [AI resolution](https://docs.screendesk.io/debug-with-ai/ai-resolution.md) has looked at the ticket, a line at the top of the card says so: **Working on an AI resolution…**, **AI resolution needs review** or **AI resolution ready**. Click it to read the result, copy its suggested reply, or see the investigation in Screendesk.


---

# 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/helpdesk-integrations/hubspot/request-via-sidebar.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.
