> ## Documentation Index
> Fetch the complete documentation index at: https://jam.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Request Jams from customers

> Create a Recording Link for each support ticket from a script. Customers record the bug without installing anything, and the Jam lands in your workspace.

When a customer reports a bug, ask them to record it. A [Recording Link](/docs/recording-links) lets them record their screen without installing anything, and the Jam lands in your workspace. The CLI creates links from a script, so your support tooling can send one with every new ticket.

<Info>
  Recording Links capture console logs and network requests only on a connected domain. See [Connect Domain](/docs/custom-recording-domain).
</Info>

## Ask your agent

```text wrap theme={"theme":"css-variables"}
Create a Recording Link for ticket https://example.zendesk.com/tickets/4812 and file its Jams in "Bug reports".
```

## Do it yourself

<Steps>
  <Step title="Find your connected domain">
    ```bash theme={"theme":"css-variables"}
    jam recording-links urls
    ```

    Copy the ID of the domain the customer uses.
  </Step>

  <Step title="Create a link for the ticket">
    ```bash theme={"theme":"css-variables"}
    jam recording-links create --name "Ticket 4812" \
      --recording-url-id <url-id> \
      --reference https://example.zendesk.com/tickets/4812 \
      --folder "Bug reports"
    ```

    The receipt prints the link's `publicId` and `url`. Send the URL to the customer, and keep the `publicId` for the next step.
  </Step>

  <Step title="Read the Jams that come back">
    ```bash theme={"theme":"css-variables"}
    jam recording-links jams <public-id>
    ```

    Pass the receipt's `publicId`, not its `id`.

    Each Jam carries the video, console, and network. Hand one to your agent with [Fix a bug from a Jam link](/docs/cli-fix-a-bug).
  </Step>
</Steps>

To see every Jam that arrived through any link, run `jam list jams --origin recording_link`.

## Next

* For link expiration, metadata, and revoking a link, see [Recording links](/docs/cli-reference#recording-links).
* For the dashboard workflow and help desk integrations, see [Recording Links](/docs/recording-links).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.