> 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/front/in-conversations.md). # In conversations Request a recording, record a response, send a library video, start a video call or send a booking link from a Front conversation. Open a conversation and open Screendesk in Front's sidebar. Each action puts its link in the reply you have open, or starts a new reply: you send it. {% embed url="" %} ![The Screendesk app beside a Front conversation](https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2Fl4mKioq5CIWv3RLmriJn%2Fdocs-front-sidebar.png?alt=media) * **Request a recording**: puts a recording link in your reply. **Record on**, under the button, sets where the customer records: one of your websites with the [Screendesk snippet](/request-screen-recording/developer-tools/installing-screendesk-script.md), with console and network logs, or **Screendesk (video only)**. * **Record a response**: opens the recorder in its own window. Your video then shows in the app's list, where **Add to reply** puts its link in your reply. * **Start a video call**: adds the call link to your reply. Available on Pro and Enterprise. * **Send a booking link**: search your [booking links](/scheduling/create-booking-links.md) and click **Add to reply**. Available on Pro and Enterprise. * **Send from library**: search your [reusable videos](/send-screen-recording/adding-video-to-the-library.md) by title, or by tag with `#tag`, and click **Add to reply**. Under the actions, the app lists the newest recordings **From this customer** or **In this conversation**, as set under **Recordings in the app** in Screendesk. **Add to reply** puts a recording's link in your reply, and **Open in Screendesk** opens them all. When Front can't add to the reply, Screendesk copies the link instead: paste it in your reply. ## When the customer records The recording is added to the conversation as an internal comment from Screendesk: **New screen recording** from the customer, a **Watch the recording** link, and what the customer wrote. The customer doesn't see it. The recording is also attached to the conversation as a link, and shows in the app's list. With tags on, the conversation is tagged `screendesk-recording-received`. When [AI resolution](/debug-with-ai/ai-resolution.md) is on, it investigates the conversation and adds what it found as an internal comment. Screendesk admins also see a line at the top of the app: **Working on an AI resolution…**, **AI resolution needs review** or **AI resolution ready**. Click it to read the audit and the suggested reply, and click **Add to reply** to put the reply in your draft. ## If something goes wrong * **Screendesk can't reach this conversation in Front**: the conversation is in an inbox the connection can't read. Check **Inboxes Screendesk can post in** in the Front settings. * **Front needs reconnecting**: a Screendesk admin reconnects Front in **Settings → Integrations**. * **Open a conversation to request a recording**: the actions work on one open conversation. --- # 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/front/in-conversations.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 `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.