Collections: supervise a collections desk
The Collections screen for a lender's desk and field teams, from today's list, calls and promises to pay to targets, trust scorecards, legal and settings. Beta.
Browse documentation
What Collections is
Collections supervises a lender's collections work: the desk that calls customers, the field officers who visit them, the agencies they work for, and the managers above them. It keeps every account, call, visit and promise to pay in one place and checks each entry against other evidence. Collections is Beta.
Collections is a module Nagent switches on for your workspace. When it is on, the sidebar shows Collections, which opens /admin/collections.
Who does what
| Who | What they can do |
|---|---|
| Organisation admin | Everything, including Settings and approving instructions |
| Collections officer | Works the desk: reads and updates accounts, calls and promises to pay |
| Field officer | Visits customers in the field app, and nothing else in Collections |
Grant the Collections officer and Field officer roles on Team Members (see people and roles). The managers above them come from your staff file (see Hierarchy below).
The tabs
- Today: the accounts due today in your queue, with what is outstanding and why each is on the list. A manager sees an empty list until they pick a person.
- Accounts: search by account or customer reference, with what is outstanding and the days past due.
- Board: the Target board, for supervision or by agency: what was collected, what is expected from open promises to pay, the new promises needed and the daily run rate.
- Scorecards: Trust scorecards. Each person's score comes from how well their entries match other evidence. An entry the checks contradict can be disputed with a reason, and someone more senior than the person it is about rules on it, never the one who raised it.
- Legal: the Legal and recovery advisor for an account, and the Legal rulebook. The legal team drafts the rulebook and a second person publishes it.
- Instructions: Instructions and campaigns for the team, for example "Cycle 5, 30 to 60 days past due: call everyone by Wednesday". Nothing is sent until the plan is approved; each person acknowledges their tasks and progress shows by manager.
- Hierarchy: regions, agencies and staff, read from your staff file. It also lists people the file names who have no sign-in yet; invite them from Team Members. A file never creates a sign-in.
- Settings: admins only (below).
Working an account
Open an account from Today or Accounts. Its card shows the customer, the days past due and the instructions that include it.
- Calling. Pressing Call rings your phone and connects you to the customer. Calls go out only within the workspace's calling hours, never to a customer who asked not to be called, and only up to the daily limit per customer.
- Outcome. After a call, choose an outcome, such as promised to pay, asked for a call back, disputes the amount or wrong number, and add a note.
- Promise to pay. A promise needs your own connected call of at least 30 seconds, a date from today to 30 days ahead, and an amount above zero and no more than is owed. The customer is sent a confirmation message; until they confirm, the promise stays unconfirmed.
- Visits. Assign visit sends a field officer. In the field app the officer records the visit with a location trail, live photos and the customer's visit code.
Settings
Admins set up the desk in Settings:
- Workspace: the display name, calling hours (India time), the call line used to bridge calls, and the go-live date. Until the go-live date, the accounts file sets who owns each account; after it, a different owner in the file is listed as a conflict instead.
- Customer messages: the WhatsApp and SMS templates for promise to pay, visit codes, receipts and contact confirmation. Use only template names your compliance team approved. A message with no template set is not sent.
- Verification: how much weight each kind of evidence carries in a trust score (four whole numbers that add up to 100), the share of contacts asked to confirm, and how close a visit must be to the customer (50 to 2,000 metres).
- Call recording: record connected calls, once you confirm the line plays the recording notice before the call connects.
- Address lookup: the geocoding key.
- Files: the staff, accounts, payments and cash receipts files. Map your column names, then upload a file or give the SFTP server it is collected from. Recent imports and Owner conflicts show what each import did.
For your developers
The field app records visits through the API with a key holding the Collections field evidence scope, on the Business plan and above.