---
title: "Recurring Issue Root Cause"
section: "Agent store — Customer Service — Customer Support"
canonical_url: "https://leverge.ai/agents/customer-service/customer-support/issue-root-cause"
category: "Customer Service"
process: "Customer Support"
trigger: "Runs on a schedule"
publisher: "Ailoitte Technologies Private Limited"
---

# Recurring Issue Root Cause

Cluster a month of tickets into the underlying faults behind them, and rank the fixes by how many tickets each one would actually stop arriving.

## At a glance

- Business function: Customer Service
- Process: Customer Support
- Runs: runs on a schedule — First of the month at 10:00
- Run cost: 7 credits
- Uses a knowledge base: no

## What it needs

- **Ticket export** (file upload) — A period's worth of tickets. Resolution notes are what make the clustering work.
- **Analysis settings** (form)

## How it works

1. Reading the ticket export
2. Clustering tickets by underlying cause
3. Writing the case for the top fix

## What it returns

- **Avoidable volume** (score)
- **The case for fixing this first** (written summary)
- **Underlying causes, by ticket volume** (breakdown table)
- **One-offs worth a second look** (flagged exceptions)

---

Source: https://leverge.ai/agents/customer-service/customer-support/issue-root-cause — Leverge