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

# Bring your tickets

> Connect Zendesk, or upload an export or a spreadsheet.

Pick where your tickets live on **Bring your tickets**, then connect or upload. Your report is ready about 12 minutes later.

![Bring your tickets. Nine tiles: Zendesk, Intercom, HubSpot, Front, Freshdesk, Gorgias, Salesforce, Help Scout and Spreadsheet.](https://mintlify.s3.us-west-1.amazonaws.com/lorikeet-mtje7p526we/images/insights/start-page-helpdesks.png)

## What each helpdesk gives your report

Exports leave different things out, so they fill different parts of the report.

| Helpdesk | Contact reasons | Repeat contacts | Answers that worked | Days |
| - | - | - | - | - |
| [Zendesk (connect)](#connect-zendesk) | Yes | Yes | Yes | 90 |
| [Zendesk (CSV)](#upload-a-csv-instead) | Partly | Partly | No | 90 |
| [Intercom](#other-helpdesks) | Partly | Yes | No | 90 |
| [HubSpot](#other-helpdesks) | Partly | No | No | 90 |
| [Front](#other-helpdesks) | Partly | Yes | Partly | 90 |
| [Freshdesk](#other-helpdesks) | Yes | Yes | No | 90 |
| [Gorgias](#other-helpdesks) | Yes | Yes | Partly | 30 |
| [Salesforce](#other-helpdesks) | Yes | Yes | Yes | 90 |
| [Help Scout](#other-helpdesks) | Partly | Yes | No | 90 |
| [Spreadsheet](#spreadsheet) | Yes | Yes | Yes | 90 |

Repeat contacts needs a customer email on every ticket. Answers that worked needs your team's replies.

## Zendesk

Connect if you can. It reads whole conversations, so you get the fullest report without exporting anything.

### Connect Zendesk

You need a Zendesk admin to approve access.

1. Select **Zendesk**, keep **Connect** selected, and enter your subdomain: the `yourcompany` in `yourcompany.zendesk.com`.
2. Select **Connect Zendesk read-only**.
3. Sign in to Zendesk as an admin and approve. If you see a customer sign-in page, choose **Switch to agent sign-in**.
4. Wait while Lorikeet reads your tickets. You can leave the page.
5. Select **Build my report**.

![The Connect panel: a Zendesk subdomain field, a Connect Zendesk read-only button, and the line: Sign in to Zendesk as an admin. If you see a customer sign-in, choose Switch to agent sign-in.](https://mintlify.s3.us-west-1.amazonaws.com/lorikeet-mtje7p526we/images/insights/zendesk-connect.png)

* **Read-only.** Lorikeet asks for `tickets:read` and `users:read`, and can't change anything in Zendesk.
* **Last 90 days, up to 5,000 tickets,** most recently updated first. Internal notes are left out.
* **Access is removed when the import ends,** whether it finished or failed.

### Upload a CSV instead

If you can't connect, select **Upload a CSV**.

1. In Zendesk, go to **Views** and open a view of your recent tickets.
2. Click **Export CSV**. Zendesk emails you the file.

**Leaves out:** the conversation. Zendesk's CSV has each ticket's subject only. [Open Zendesk's export guide](https://support.zendesk.com/hc/en-us/articles/5521220496154-Exporting-a-view-of-tickets-to-a-CSV-file)

### Troubleshooting

> [accordion] We couldn't find yourcompany.zendesk.com
>
> Enter only the part before `.zendesk.com`. If your company uses its own domain for Zendesk, ask your Zendesk admin for the `zendesk.com` subdomain.

> [accordion] My company signs in to Zendesk with SSO
>
> Sign in to Zendesk through SSO in the same browser first, then select **Connect Zendesk read-only**.

> [accordion] The sign-in expired, or the import stopped
>
> Select **Connect Zendesk read-only** again. Lorikeet has already disconnected.

## Other helpdesks

Export a file, then upload it on **Bring your tickets**.

> [accordion] Intercom
>
> 1. In **Reports**, open **Dataset export** and pick **Conversations**.
> 2. Set the dates, then click **Export CSV**.
>
> **Leaves out:** Intercom's CSV has no message text, so the report reads subject lines only.
>
> [Open Intercom's export guide](https://www.intercom.com/help/en/articles/2046229-export-your-conversations-data)

> [accordion] HubSpot
>
> 1. Export your tickets as a CSV.
> 2. HubSpot emails you the file.
>
> **Leaves out:** HubSpot's export has no conversation thread or customer email.
>
> [Open HubSpot's export guide](https://knowledge.hubspot.com/import-and-export/export-records)

> [accordion] Front
>
> 1. In **Analytics**, open the **⋯** menu and choose **Export data**.
> 2. Pick **Messages** and download the file.
>
> **Leaves out:** Front cuts each message to 200 characters. Exports need Front's Professional plan.
>
> [Open Front's export guide](https://help.front.com/en/articles/2147)

> [accordion] Freshdesk
>
> 1. Go to **Tickets**, then **All tickets**, then **Export**.
> 2. Tick **Description** and set the date to **Any time**.
>
> **Leaves out:** Freshdesk exports each ticket's first message, not your team's replies.
>
> [Open Freshdesk's export guide](https://support.freshdesk.com/support/solutions/articles/225158)

> [accordion] Gorgias
>
> 1. In **Analytics**, open a report and click a metric.
> 2. Choose **Export**, then **Export with message content**.
> 3. Gorgias emails you the file.
>
> **Leaves out:** Public replies from the last 30 days only. Gorgias support can do a longer custom export.
>
> [Open the Gorgias export guide](https://helpcenter.gorgias.com/en-US/export-tickets-404844)

> [accordion] Salesforce
>
> 1. In **Reports**, create a report on **Cases and Emails**.
> 2. Export it as **Details Only**, in **CSV**.
>
> **Leaves out:** Needs Email-to-Case. Other formats cut text to 255 characters.
>
> [Open Salesforce's export guide](https://help.salesforce.com/s/articleView?id=analytics.reports_export.htm\&type=5)

> [accordion] Help Scout
>
> 1. Export your reporting data as a CSV.
> 2. Help Scout emails you the file.
>
> **Leaves out:** Help Scout's export has subject lines only, and leaves out open conversations.
>
> [Open Help Scout's export guide](https://docs.helpscout.com/article/849-export-reporting-data)

## Spreadsheet

Use a spreadsheet when your helpdesk isn't listed, or its export leaves out too much. Put one row per message.

> [card] [Download the template](https://docs.lorikeetcx.ai/files/tickets.csv)
>
> `tickets.csv`, with four example tickets

| Column | Example |
| - | - |
| **Ticket ID** | `1001` |
| **Date** | `2026-10-06 09:12` |
| **Customer email** | `priya.shah@example.com` |
| **Who wrote it** | `Customer` or `Agent` |
| **Message** | `My order arrived damaged.` |

* Rows with the same ticket ID become one conversation.
* `Customer` marks the customer's messages. Anything else counts as your team.
* Dates without a time zone are read as UTC. Rows with no date or author are skipped.
* Extra columns, such as plan or region, let Coach split findings.

## File rules

* CSV up to 10 MB, or Excel (`.xlsx`) up to 2 MB
* Up to 5,000 tickets. Above that, Coach reads a sample of 5,000 that keeps each customer's tickets together.

> [!WARNING]
>
> Don't upload PHI until your company has signed a BAA with Lorikeet.


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