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

# How KPI Manager Works

> The daily pass, and when an analysis does and does not run

KPI Manager runs a single automated pass once every day, at **5:00 AM IST**, covering the **previous calendar day's** calls. The pass has four phases.

## The four phases

<Steps>
  <Step title="Collect">
    Callkaro gathers the previous day's calls for every agent that has a KPI Manager configuration, applies the scope from your RCA Prompt, and sends the batch to each configured data source — calling your API endpoints and running your Python code.
  </Step>

  <Step title="Measure">
    Each KPI metric's actual value is read from the responses and compared against its target. Every comparison is recorded, whether it passed or failed.
  </Step>

  <Step title="Analyse">
    Any metric that missed its target by at least **1 percentage point** — and that your RCA Prompt actually asks about — triggers a Root Cause Analysis. The RCA agent reads the day's audited calls, transcripts, post-call variables, the agent's own prompt and its recent findings history, then writes a report.
  </Step>

  <Step title="Deliver">
    The report is stored against the agent and that day, rendered as a PDF, emailed to the agent's owner, and its root causes become cards in Pending Tasks ready to be assigned.
  </Step>
</Steps>

<Info>
  **Why the threshold exists.** A metric that lands a fraction below target is noise, not a problem. The 1-percentage-point floor keeps the reports meaningful — you only get a report when there is something real to explain.
</Info>

## Watching the pipeline run

Every step of the pass is recorded in a day-wise timeline, so you can see exactly what happened and when. Open it from [History → RCA](https://callkaro.ai/dashboard/kpi-manager-dashboard?tab=history\&subtab=rca) on the KPI Manager Dashboard.

<img src="https://mintcdn.com/callkaroai/YnMJfeuar7Le0tPd/images/kpi-manager/day-wise-timeline.png?fit=max&auto=format&n=YnMJfeuar7Le0tPd&q=85&s=c0ff49236adfa3777451b45f6805b449" alt="Day-wise pipeline timeline" width="2048" height="1232" data-path="images/kpi-manager/day-wise-timeline.png" />

Each event is tagged **Done**, **Attention**, **Failed**, **Skipped** or **Info**, and the **Automatic** and **Manual** tabs separate the nightly pass from analyses you triggered yourself.

## When an analysis does not run

A metric is measured and reported every day, but an analysis only runs if all four of these are true:

* The metric's actual value is **below** its target.
* The shortfall is at least **1 percentage point**.
* Your RCA Prompt **covers that metric** — if the prompt asks only about conversion rate, other metrics are still measured but not analysed.
* **Auto RCA** is switched on for that agent.

<Tip>
  Whichever condition blocked it is written into the day's timeline in plain English, so a missing report is never a mystery.
</Tip>