Before any reminder goes, the agent checks why the payment was missed and whether the customer should be contacted at all. It then sends an approved template at depth 3, within your contact limits. Compliance approves every template. Replies that mention difficulty, disputes or bereavement go straight to a person, and so does any message outside the approved set.
What are early arrears reminders, and who owns them?
Early arrears covers the first days and weeks after a missed payment. Most customers in early arrears are not in serious difficulty: a card expired, a pay date moved, a direct debit failed. A clear, friendly reminder with an easy way to pay resolves most cases. For the few who are struggling, the first contact is the chance to offer help before the debt grows.
Collections owns the contact strategy: when to contact, by which channel, how often. Compliance approves the wording. The agent's value is in the check before the message. A reminder sent to a customer who has just agreed a plan, or whose relative has just died, does real harm and costs trust.
What does the agent prepare, and what does a person approve?
- Agent, depth 1: finds accounts newly in arrears. From the servicing system's daily arrears list.
- Agent, depth 1: checks why. A failed direct debit caused by the bank, a payment received but not applied, a payment made to the wrong reference. Some missed payments are failed payments, which is why payment investigations are a good early job for bank agents.
- Agent, depth 1: checks whether to contact. Vulnerability markers, bereavement, an open dispute or complaint, an agreed plan or payment holiday, a legal marker. Any of these stops the reminder.
- Agent, depth 1: checks contact limits. How many contacts the customer has had and through which channels, against your strategy's limits.
- Agent, depth 3: sends an approved template. With the amount, how to pay, and how to get help. The template chosen depends on the stage and the channel.
- Agent, depth 2: drafts anything else. A reminder that needs wording outside the approved set is drafted for a person.
- Person: handles replies about difficulty. Any reply mentioning money worries, illness, job loss or a dispute goes to a person, with the history attached.
- Agent, depth 3: confirms when the payment arrives. A short thank-you message, and the account leaves the arrears list.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Arrears list | Reads new arrears | 1 | None |
| Why | Checks for failed or misapplied payments | 1 | Correcting bank errors |
| Whether to contact | Checks markers and flags | 1 | Overriding a stop |
| Limits | Checks contact count | 1 | Changing limits |
| Send | Sends approved template | 3 | Template approval |
| Other wording | Drafts | 2 | Sending it |
| Replies | Routes difficulty replies | 1 | The conversation |
| Payment received | Sends confirmation | 3 | None |
Which controls apply, and what evidence do they leave?
Approved templates only at depth 3. The agent can send only templates compliance has approved, in their approved version. Evidence: the template identifier and version on every message sent.
Pre-contact checks filed. Each reminder is filed with the result of each stop check. If a reminder went to someone with a bereavement marker, the record shows whether the marker was there at the time.
Contact limits in the bounds. Your contact strategy's limits sit in the customer's own limits in the minimum chain. A reminder beyond the limit is refused, and the verdict names that bound.
Bank errors fixed, not chased. If the agent finds the missed payment was the bank's fault, no reminder goes. It drafts the correction for a person and notes the account.
Difficulty routing. Every reply routed to a person is filed with the words that triggered it.
Where does it usually go wrong?
Reminding people the bank failed. The direct debit was not collected because of a processing error, and the customer gets an arrears letter. Check first.
Contact after an agreement. A customer agrees a plan by phone, and the next morning the system sends a reminder because the plan was not recorded yet. The check for an agreed plan must read the latest records, including notes from the last day.
Tone drift. Templates get edited over time to be firmer. Reminders in early arrears should be clear and helpful; threats of further action belong later and only where the law and policy allow.
Too many channels at once. A text, an email and an app notification on the same day feel like pressure. Count all channels against the limit.
Missing early signs. A reminder sent to a customer whose account shows other strain may be the wrong first contact. Accounts with several warning signals may need a person, which is why reminders should read the output of monitoring early warning signals in a loan book.
What should you measure?
- Accounts cured after the first reminder.
- Reminders stopped by a pre-contact check, by reason.
- Reminders sent in error, such as to accounts with agreed plans or markers. Should be none; review every case.
- Replies routed for difficulty, and time to first human contact.
- Complaints about reminders.
If a reminder leads to a plan that needs the customer's signature, that is a separate capability; letting an agent send documents for signature covers it. The general bounds for bank agents are in AI agents in banking.
Where Pryme fits
In Pryme, sending approved reminders is certified through Attest on your own past early-arrears cases, including those where a reminder should have been stopped. Contact limits and template versions sit in the customer's own bounds, so the minimum chain refuses anything outside them, and every message and every stop is filed.
Questions people ask
Can the agent call customers in arrears?
Outbound calls are a separate capability. Many lenders keep voice contact with people, because a customer who answers may want to talk about difficulty straight away.
What time of day should reminders go?
Your contact strategy sets the hours, and the agent applies them in the customer's own time zone. Messages outside the allowed hours are refused.
Can the agent take a payment when the customer replies?
Taking a payment moves money and is a separate depth 4 capability. More often the reminder links to a secure payment page the customer completes themselves.