Read your agent performance

Read activity, replies, attributed collections, and time saved without turning correlation into causation.

Updated

In short

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.

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.

Billabex team · Verified against the product on