> 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/video-calls/start-a-video-call.md).

# Start a video call

Start a video call from Screendesk or your helpdesk and see the customer's screen live.

A video call opens a private room in the browser. Your customer joins from a link, with no account or download, and can share their screen, camera and microphone. You see their screen, but you can't control it.

{% embed url="<https://app.screendesk.io/recordings/a741391a-fb8f-452a-9191-62d673da575e>" %}

Available on Pro and Enterprise.

## Start a call

Click **Video call** in the sidebar. Screendesk creates a room and copies its link. Paste the link to your customer.

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2FrEDN9hu3Fv2lEOwqoBMS%2Fdocs-hl-call.png?alt=media" alt="The Video call button in the sidebar"><figcaption></figcaption></figure>

Your helpdesk and Slack integrations can also start a call from a ticket or conversation. To let the customer pick a time instead, send a [booking link](https://docs.screendesk.io/scheduling/create-booking-links.md).

{% hint style="info" %}
There is one link for everyone. A member of your workspace who opens it while signed in joins as a host (Watch only members can't host). Everyone else joins as a guest.
{% endhint %}

If the call is recorded, guests see a recording notice before they join, or a choice to join without being recorded. Set this in [Video call settings](https://docs.screendesk.io/video-calls/video-call-settings.md).

## After the call

A recorded call appears with your other recordings, marked **Video call**, a few minutes after it ends. If transcription is on, the transcript is in its details.

The recording's **Details** show when the call ran and who joined. In the **Insights** panel, the **System Info** tab lists each guest's device (operating system, browser, device, screen and window size) and connection (locale, timezone, VPN, IP address, internet provider and location). Hosts aren't listed. These details arrive a few minutes after the recording, and only for recorded calls.

Who can watch video call recordings is set in **Settings → Sharing & access**, and how long they're kept in **Settings → Data retention**.

## If something goes wrong

* **The customer can't share their screen on a Mac.** The browser needs screen recording permission in macOS **System Settings → Privacy & Security → Screen Recording**. The browser may need a restart afterwards.
* **The customer can't connect.** Some company networks block video calls. Ask them to try another browser or network.
* **There's no recording.** Check **Start recording** in [Video call settings](https://docs.screendesk.io/video-calls/video-call-settings.md): with **Manually**, a host has to start it from the call's toolbar.


---

# 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/video-calls/start-a-video-call.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.
