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

# Repeat contacts

> How often customers write again within 72 hours, and why.

The **Came back within 72 hours** tile shows the share of tickets that were a repeat. The flow under it shows why customers came back. The share counts tickets and the flow counts customers, so don't compare them directly.

![The Came back within 72 hours tile: 8.4% of tickets. A flow from 1,006 customers to 27 who came back and 979 who didn't, then split by same or different issue, the reason, and what would have prevented it.](https://mintlify.s3.us-west-1.amazonaws.com/lorikeet-mtje7p526we/images/insights/repeat-contacts-flow.png)

## How the share is measured

A ticket is a repeat when the same customer opened another ticket in the 72 hours before it. Customers are matched on the email column in an upload, or the requester in Zendesk, so tickets without a customer are left out. If your file has no customer column, the report has no repeat contacts.

* Every repeat counts. Three tickets from one customer in 72 hours are two repeats.
* A new ticket that only says "thanks" counts too, because no AI reads the tickets for this number.
* The share covers your whole file, even if the rest of the report read a sample.
* 72 hours is the default window. The report shows the window it used.

A customer who didn't come back may have given up, so a low share isn't proof of resolution.

## How the flow is measured

For each customer who came back, an AI model reads their first ticket, including your team's replies, and the ticket that followed. It decides whether it was the same issue, why they came back, and what would have prevented it.

* **Reasons:** Answer was wrong, Answer was incomplete, Agent couldn't act, Customer disagreed, Something changed, Routine or planned return, Unclear
* **A better answer would have prevented it:** Clearer steps, Explain why, Set expectations, More empathy
* **Something else would have:** Give the agent the action, Faster access to a person, Policy call, Fix upstream or tell them first, Can't tell


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