# Read your agent performance

- HTML page: https://www.billabex.com/en/help/reporting-analytics/read-agent-performance/
- Language: en
- Version française: https://www.billabex.com/fr/aide/pilotage-analyses/performance-agent.md
- Updated: 2026-07-15
- Site index: https://www.billabex.com/llms.txt

<section class="help-summary" aria-labelledby="in-short"><h2 id="in-short">In short</h2><p>Performance combines contacted accounts, deliverability, replies, and collections attributed to the agent. A collection is attributed when a follow-up was sent on the same account within the previous 30 days; this is temporal proximity, not proof that the email caused payment. Time saved depends on the organization’s minutes-per-reminder setting.</p></section>

## Expected result

You read metrics together with period and attribution rule without overinterpreting one number.

## Before you start

- Check base currency and time-saved setting.
- Compare equivalent windows and identify partial current month.

## Procedure

1. Open **Performance** and read the period applied to every metric.
2. Compare active debtors, deliverability, opens, and replies.
3. Review attributed collections and their 30-day window.
4. Check time saved from reminder count and organization setting.
5. Open monthly series before communicating a trend.

## What Billabex does

Billabex joins converted collection movements with Sent follow-ups on the same account in an inclusive 30-day window, then aggregates twelve months in browser timezone.

## If the result is not what you expected

- Attribution is not causation; payment can have another origin.
- Changing minutes per reminder affects estimated time, not email history.
- Compare volumes behind rates before claiming improvement.