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

# Lorikeet Insights

> Bring your support tickets, and Coach writes up why customers contact you, who comes back, and what your team's replies get right.

Insights reads your recent support tickets and writes a report of what it finds. You bring the tickets. Coach, Lorikeet's AI assistant, does the reading.

## How it works

1. [Bring your tickets](https://docs.lorikeetcx.ai/insights/bring-your-tickets.md): connect Zendesk, or upload an export or a spreadsheet.
2. Your report is ready about 12 minutes later. Lorikeet emails you when it's published.
3. Slower analyses add to the report over the next one to two hours.

Nothing changes in your helpdesk.

## What the report shows

| Metric | What it tells you |
| - | - |
| [Contact reasons](https://docs.lorikeetcx.ai/insights/contact-reasons.md) | Why customers write in |
| [Repeat contacts](https://docs.lorikeetcx.ai/insights/repeat-contacts.md) | Who wrote again within 72 hours, and why |
| [What's at stake](https://docs.lorikeetcx.ai/insights/whats-at-stake.md) | How many contacts needed something done, not just an answer |
| [How hard the work is](https://docs.lorikeetcx.ai/insights/how-hard-the-work-is.md) | How much of your queue an answer alone could handle |
| [Who's writing in](https://docs.lorikeetcx.ai/insights/whos-writing-in.md) | How many tickets came from AI agents or bots |
| [Quality checks](https://docs.lorikeetcx.ai/insights/quality-checks.md) | How many of your team's replies passed every check |

Each finding links to the tickets behind it. What the report can show depends on what your tickets include: see [what each helpdesk gives your report](https://docs.lorikeetcx.ai/insights/bring-your-tickets.md#what-each-helpdesk-gives-your-report).


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