V4N

Operations

How to run a collections call list: a daily process for lenders and SACCOs

By the V4N team · Published · 3 min read

The short answer

Run collections from one shared list per day or campaign. Share it out fairly, put due callbacks first, then people not yet called, then retries. Cap the attempts per number, never call the same person from two lists, record an outcome after every call, and measure the share of people reached and promises to pay kept, by agent, every evening.

Most collections floors start the day the same way: a spreadsheet of overdue accounts, split by hand, sent around on WhatsApp or email. By lunchtime nobody knows who has been called, two agents have rung the same borrower, and the promises to pay made yesterday are in someone's notebook.

A call list fixes that, but only with rules. These are the seven to set before anyone dials.

1. One list, one owner, one end date

Build each list for a purpose, such as "1 to 30 days overdue, Nairobi branches, this week". Give it an owner who answers for the results, and an end date. Lists without an end date never get closed, and old names keep getting called.

2. Share it out fairly

There are three common ways, and each suits a different team:

  • Evenly: every agent gets the same number of people. Simple, and fair when accounts are similar.
  • By a column: each agent gets the accounts of their own branch, region or product. Good when agents know their customers.
  • A shared pool: agents take the next person from one pool. Good for mixed teams, but cap how many untouched names one agent can hold, so nobody hoards the easy ones.

3. Put the calls in the right order

The order matters more than the speed. A sensible default:

  1. Callbacks that are due now, because the customer asked for this time.
  2. People not yet called.
  3. Retries, longest since the last attempt first.
  4. People already spoken to, only if there is a reason to call again.

4. Cap the attempts

Decide how many tries a number gets before it leaves the list, for example three, at different times of day. Unlimited retries waste agent time and, for lenders, can turn into the repeated contact that regulators act on. In Kenya, the Office of the Data Protection Commissioner has ordered a lender to pay a complainant KSh 400,000 over unsolicited calls and texts (Nation).

5. Never call the same person from two lists

Collections, sales and customer care often run lists at the same time. If a borrower is on two of them, they get two calls in one morning. Check every new list against the lists already running, and leave out anyone being worked elsewhere.

6. Record an outcome after every call

Agree a short list of outcomes and make one required after each call: promise to pay (with the date), callback requested (with the time), wrong number, not reached, refused. A callback without a date is a wish, not a follow-up.

7. Measure every evening

MeasureHow to work it out
Reach ratepeople spoken to ÷ people called
Promises to paypromises recorded ÷ people spoken to
Promises keptpromises paid by their date ÷ promises due
Callbacks on timecallbacks made by their time ÷ callbacks due
Attempts used uppeople who reached the attempt cap without being reached

Look at these by agent and by list. A low reach rate usually means the wrong time of day or bad numbers, not lazy agents. For people who call you back and miss you, see how to follow up missed calls.

Sources

Common questions

How many times should a collections team call one number?

Many teams cap it at three attempts at different times of day, then move to a text or letter. Set your own cap and write it down.

Should agents choose who to call next?

Not usually. A fixed order (due callbacks, then new, then retries) is fairer to customers and easier to measure.

How do we stop two agents calling the same borrower?

Give every person on the list one owner, and leave out anyone already on another running list.

Can V4N run collections call lists?

Yes. A supervisor uploads a list of up to 20,000 people and shares it evenly, by a column or into a pool. Agents see due callbacks first, attempts are capped per list, nobody is given out from two running lists, and calls link to the right person on any connected phone system, including 3CX and desk phones. Results are reported by agent, by day.

Every call seen, sorted and answered

See V4N on a setup like yours

A short call with our team. We look at your phone system and your team, then show you V4N working the way you would use it.