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

# Front

> Connect Front with Hyperline to attach shared inbox conversations, tags, statuses, and messages to customers for the monitoring agent.

[Front](https://front.com) is a shared inbox and customer communication platform for teams handling email and other channels together.

Connecting Front lets Hyperline attach customer conversations to the matching Hyperline customers, so the customer monitoring agent can weigh open conversations and support pressure alongside contract, invoice, payment, and usage data.

<Info>
  Front is part of [Customer intelligence](../docs/customer-intelligence/overview), a paid add-on. The Front 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 [Front account](https://front.com).
* A Front API token, created from your Front settings.
* Admin rights on your Hyperline account.

## Connect Front

<Steps>
  <Step title="In Front, create an API token" />

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

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

  <Step title="Paste your Front API token and confirm">
    Hyperline validates the token 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 Front conversations to Hyperline customers.
  </Step>
</Steps>

The connection is read-only. Hyperline never sends, replies to, or modifies anything in Front.

## What Hyperline fetches

For every matched conversation, Hyperline stores:

| Data         | Details                                                 |
| ------------ | ------------------------------------------------------- |
| Conversation | Front conversation identifier and subject               |
| Status       | Normalized to `open`, `closed`, or `snoozed`            |
| Tags         | The conversation tags, used as labels                   |
| Contact      | Handle and name of the conversation recipient           |
| Dates        | Creation date and last update date                      |
| Messages     | Each message with its text, author, direction, and date |

Front has no native conversation priority, so every synced conversation carries the same default priority in Hyperline.

### Which conversations are matched

Hyperline resolves conversations per customer, in this order:

1. If the customer is linked to a Front **account**, Hyperline lists the conversations of that account's contacts.
2. Otherwise, Hyperline searches conversations mentioning the customer **Domain**, then keeps only those whose recipient uses an email address on that domain.

Public email domains, such as `gmail.com`, are skipped: a domain search on them would match unrelated conversations.

<Note>
  The domain search is best-effort: Front's search has no wildcard on sender or contact, so Hyperline filters the results itself. Linking the Front account on the customer page gives more precise matching.
</Note>

## Synchronization

Hyperline synchronizes Front once a day, and also refreshes a customer on demand when the customer monitoring agent analyzes it.

## Where Front data appears

* **Customer page**: the **Integrations** section shows a Front row with the most recent thread. Open it to browse synced conversations with their statuses, labels, and messages.
* **Monitoring agent**: enable Front from the agent's **Connectors** tab. See [Customer monitoring agent](../docs/customer-intelligence/customer-monitoring-agent).
* **Analysis results**: Front appears under **Data sources** when support context was used.

## Manage the integration

Open **Settings > Integrations** and select **Front**. Synchronization errors, such as a revoked token, are reported on this page.

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

## Related

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