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

# Jiminny

> Connect Jiminny with Hyperline to sync call recordings, participants, summaries, and transcripts into customer intelligence analyses and reports.

[Jiminny](https://www.jiminny.com) is a conversation intelligence platform that records, transcribes, and analyzes customer calls, including video meetings and calls placed from its dialer.

Connecting Jiminny lets Hyperline attach your recorded customer conversations to the matching Hyperline customers, so the customer monitoring agent can combine what was said on a call with contract, subscription, invoice, payment, and usage data.

<Info>
  Jiminny is part of [Customer intelligence](../docs/customer-intelligence/overview), a paid add-on. The Jiminny card only appears in **Settings > Integrations** when Customer intelligence is enabled for your account. Contact the Hyperline team through the in-app chat to enable it.
</Info>

## Prerequisites

* A valid [Jiminny account](https://www.jiminny.com) with conversations recorded in your workspace.
* A Jiminny **API key**, created from your Jiminny organization settings. Generating one usually requires a Jiminny administrator.
* Admin rights on your Hyperline account.

<Note>
  The key is issued at organization level and covers every recording in your Jiminny workspace. Hyperline attributes conversations to customers across the whole organization, so a key limited to a single user would only ever surface that user's calls.
</Note>

## Connect Jiminny

<Steps>
  <Step title="In Jiminny, create an API key">
    Open your Jiminny organization settings, go to **Integrations**, and generate a key for the Customer API. Copy it immediately, as Jiminny only displays it once.
  </Step>

  <Step title="In Hyperline, navigate to the Settings > Integrations page" />

  <Step title="Search for Jiminny and click Connect" />

  <Step title="Paste your Jiminny API key and confirm">
    Hyperline validates the key immediately and rejects it if it is invalid or revoked.
  </Step>

  <Step title="That's it!">
    The integration appears as connected and Hyperline starts matching Jiminny conversations to Hyperline customers.
  </Step>
</Steps>

Jiminny runs separate instances for different regions, and a key is only valid on the one that issued it. Hyperline detects the right instance while validating the key, so there is nothing to select.

The connection is read-only. Hyperline never creates, edits, or deletes anything in Jiminny.

## What Hyperline fetches

For every matched conversation, Hyperline stores:

| Data         | Details                                                                                    |
| ------------ | ------------------------------------------------------------------------------------------ |
| Conversation | Jiminny conversation identifier, title, and the conferencing tool behind the recording     |
| Timing       | Start and end date and time, and duration                                                  |
| Participants | Name and email address of each participant, internal and external, and whether they joined |
| Summary      | The summary Jiminny produced for the conversation                                          |
| Transcript   | The transcript of the conversation, attributed to each speaker                             |

Hyperline does not download audio or video recordings. Only the details, summary, and transcript listed above are stored.

### Which conversations are considered

Hyperline syncs completed conversations that carry a recording: video meetings recorded by Jiminny, and inbound or outbound calls placed through the Jiminny dialer. SMS messages sent from the dialer are ignored, since they have nothing to transcribe.

Very short conversations, such as an unanswered ring or a voicemail, are stored without a transcript. Jiminny does not produce one when there is no conversation to transcribe.

### Which conversations are matched

Jiminny cannot filter conversations by participant, so Hyperline scans the organization and matches locally. A conversation is attached to a customer when at least one participant email corresponds to:

* the customer **Domain**, meaning any participant using an email address on that domain
* the customer **Billing email**
* one of the customer **Invoice emails**
* a contact email synced from a connected CRM

Conversations that cannot be matched to a customer are not stored.

<Tip>
  Keep customer **Domain** and **Billing email** values up to date. They are the main signals used to attach a Jiminny conversation to the right customer.
</Tip>

### Summaries

When Jiminny has produced a summary for a conversation, Hyperline uses it as the meeting summary. When a transcript is available but Jiminny has not produced a summary, Hyperline generates one from the transcript.

## Synchronization

Hyperline synchronizes Jiminny in two ways:

* **Daily workspace synchronization**: once a day, Hyperline reviews recent Jiminny conversations and attaches the new ones to the matching customers.
* **On-demand customer synchronization**: a refresh is also triggered when the customer monitoring agent analyzes a customer, and when you click **Sync meetings** from the customer's Jiminny panel.

Synchronization is incremental. Conversations already stored are not fetched again, and a transcript already downloaded is never downloaded twice.

Jiminny builds transcripts and summaries after a call ends, so a conversation recorded a few minutes ago can appear before its transcript is available. Hyperline retrieves it on a later run, once Jiminny has finished generating it.

<Note>
  The first synchronization covers up to 180 days of history, and each run processes a bounded number of conversations and transcripts. A Jiminny organization with a large history is therefore backfilled progressively over successive runs rather than in a single pass.
</Note>

## Where Jiminny data appears

* **Customer page**: the **Integrations** section shows a Jiminny row with the most recent meeting. Open it to browse synced meetings with their participants, summary, and transcript, or to trigger **Sync meetings**.
* **Monitoring agent**: enable Jiminny from the agent's **Connectors** tab to let it use call context. See [Customer monitoring agent](../docs/customer-intelligence/customer-monitoring-agent).
* **Analysis results**: Jiminny appears under **Data sources** when call context was used for an analysis.

## Manage the integration

Open **Settings > Integrations** and select **Jiminny** to review the connection status. Synchronization errors, such as a revoked key, are reported on this page.

Use **Disconnect** to stop synchronizing new conversations. Revoke the API key in Jiminny as well if you want to invalidate it entirely.

## Related

* [Gong](./gong)
* [Customer intelligence](../docs/customer-intelligence/overview)
* [Customer monitoring agent](../docs/customer-intelligence/customer-monitoring-agent)
* [Integrations overview](./overview)