> ## 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.

# Fin (fka Intercom)

> Request screen recordings from customers inside Fin conversations and get the full technical context back in the thread.

Jam for Fin lets your support agents request screen recordings directly from Fin conversations. Agents send a recording request in one click. The customer records without installing anything, and the resulting Jam (a screen recording plus optional technical logs) appears as a note in the conversation and in your Jam dashboard.

Jam supports **Fin Messenger**, **email**, and **Slack** channels.

***

## Connect Fin with Jam

<Steps>
  <Step title="Open Settings → Integrations">
    Go to [**Settings → Integrations**](https://jam.dev/s/settings/integrations).
  </Step>

  <Step title="Select Fin">
    Click **Fin** and complete the authorization flow.
  </Step>

  <Step title="Confirm connection">
    Once authorized, Jam becomes available inside your Fin inbox.
  </Step>
</Steps>

***

## Set up Jam in the Fin sidebar

Pin Jam to the top of the Fin sidebar so agents can request recordings without switching tools:

<Steps>
  <Step title="Open the Fin inbox">
    Navigate to any conversation in your Fin inbox.
  </Step>

  <Step title="Edit sidebar apps">
    Scroll to the bottom of the sidebar and click **Edit apps**.
  </Step>

  <Step title="Pin Jam">
    Find Jam in the list, pin it, and drag it to the top of the sidebar.
  </Step>
</Steps>

***

## Request a Jam from Fin

<Steps>
  <Step title="Open the conversation">
    Navigate to the customer conversation where you need a recording.
  </Step>

  <Step title="Click the Jam app">
    Select Jam from the sidebar or use an Fin shortcut.
  </Step>

  <Step title="Send the recording request">
    Click to send. Jam sends the customer a message with a recording link.
  </Step>
</Steps>

<Note>
  In email and Slack conversations, the Jam app cannot render inside the thread. In those cases, Jam sends the customer a direct Recording Link instead.
</Note>

### What the customer sees

* A message asking them to record their screen
* A link that opens the Jam recorder in their browser
* A simple interface to start recording
* Automatic upload on submission

### What the agent sees

After the customer submits:

* A note added to the Fin conversation
* A link to the Jam recording, which includes:
  * Screen recording
  * System metadata
  * Console logs and network requests (if a custom domain is configured)
  * Custom logs such as user IDs (if configured)

***

## Jam Inbox for Fin

After connecting Fin, a dedicated **Jam for Fin** page appears in your Jam dashboard. This works as a centralized inbox for all recordings requested through Fin.

From the inbox you can:

* View all fin-requested Jams
* See which member requested each recording
* Filter and organize submissions
* Access conversation context

***

## Configure default settings

In the top-right corner of the **Jam for Fin** page, you'll find the configuration panel. Changes here apply to all agents by default. Agents can override any setting when sending a request.

### Capture Logs URL

This setting controls where the customer is redirected to record and where logs are captured from.

* If no custom domain is selected, screen recordings still work but console logs and network requests are not included.
* To enable log capture, install Jam's scripts on your site and verify your domain in [**Settings → SDK**](https://jam.dev/s/settings/sdk).

<Note>
  See [Set up a custom recording domain](/custom-recording-domain) for the full setup guide.
</Note>

### Default folder

Choose the folder where Fin Jams are saved. This keeps support recordings separate from internal bug reports and maintains structured triage.

### Default message

Customize the message sent when requesting a recording. The default is:

> "Would you mind taking a screen recording of the issue to send along to our engineers?"

Edit this to match your support tone. Agents can also edit the message before sending each request.

***

## Fin AI Agent integration

For Fin AI workflow integration, see [Fin AI](/fin-ai-setup).

***

## Privacy and data protection

Jam automatically blurs sensitive information in the browser before the recording is uploaded. This applies to all Fin-requested recordings. Blurred data includes password fields, credit card numbers, social security numbers, email addresses, and API keys.

If you use Jam on your own domain, you can further customize blur behavior. See [Auto-blur sensitive content in requested Jams](/recording-links#privacy-and-automatic-blurring).

***

## FAQ

<AccordionGroup>
  <Accordion title="Does Jam work in email and Slack conversations?">
    Yes. In Messenger conversations, the Jam app renders directly inside Intercom. In email and Slack threads, Jam sends the customer a Recording Link instead, since the app cannot render inside those channels.
  </Accordion>

  <Accordion title="Where do Fin recordings appear?">
    Recordings appear as a note inside the Intercom conversation, in your Jam dashboard, and in the Jam for Intercom inbox view.
  </Accordion>

  <Accordion title="Can agents override the default settings?">
    Yes. Agents can override the Capture Logs URL, Default Folder, and Default Message when sending a recording request.
  </Accordion>

  <Accordion title="Why are console logs missing from my Fin Jam?">
    Console logs are only captured if a custom domain is connected, Jam's Recorder and Capture scripts are installed, and the verified domain is selected in the Intercom settings. If no custom domain is selected, only the screen recording is captured.
  </Accordion>

  <Accordion title="Is sensitive information protected?">
    Yes. Jam automatically blurs sensitive data in the browser before upload. If you use a custom domain, you can further customize blur behavior.
  </Accordion>

  <Accordion title="Can Jam be used with Fin Tasks?">
    No. Jam for Intercom currently only supports Fin Workflows. Integration via Fin Tasks is not available.
  </Accordion>
</AccordionGroup>