Banking · collections and customer conversations
Collections conversation: offer Conversation 2214, €85 a month for 6 months
A retail bank contacts about 120,000 customers a year who have missed a payment on a personal loan or a credit card. An agent holds the conversation in the bank’s app and by message. Within a mandate owned by the Head of Collections, it offers the standard repayment arrangements of the bank’s forbearance policy; the messaging service sends the offer. Anything else goes to a trained specialist, and every customer flagged for specialist support is handed to the support team before any offer is made.
Follow it through the essentials (part two)Turn the map to this firm (part four)Walk its pathway on the explorer
Today, with a person
A trained specialist speaks to the customer, takes income and spending, offers an arrangement the forbearance policy allows within her authority, and records it. Customers who need specialist support are handled by a dedicated team. Quality assurance listens to a sample of conversations and decides who may agree what.
The question for the room
Would you let this agent offer a repayment arrangement to a customer without individual human approval?
The day, in the record
- 10:02 Customer C-5521 replies to a missed-payment message on loan L-3390 · arrears €240 · monthly instalment €180
- 10:06 Income and spending taken in the conversation · €95 a month left after essential spending
- 10:07 Offer drafted · a reduced payment of €85 a month for six months, arrangement RA-2, template RA-2-T3 · declared basis: the customer file as at 07:00, forbearance policy v7 · operation M2214-O1
The mandate CO-03 · version 03.4 · since 01.08.2026
| Owner | Head of Collections |
| Agent | collections-agent-05, acting for Collections |
| Action | offer the standard repayment arrangements of the forbearance policy in a conversation, and send the offer through the messaging service |
| Level | decide: the agent offers within the mandate; the messaging service sends |
| Limit | arrears up to €2,500 · a reduced payment for up to six months · no fee waived · €400,000 of arrears under new offers a day across the deployment |
| Conditions | arrangement types RA-1 to RA-3 only · income and spending taken in the conversation · no support flag on the customer record · no open complaint · no legal action started · the offer text from an approved template, with its numbers filled from the record |
| Review trigger | three referrals for one reason in seven days (R-11); an offer sent to a customer with a support flag narrows at once (R-11V) |
| Revocation | the owner, the second line, or a revocation rule |
| Challenger | Head of Conduct Risk, the second line |
| Restore | after 40 clean offers from a test chosen for the cause, sampled by the conduct team, on two signatures, the owner’s and the Head of Conduct Risk’s |
| Expiry | 31.12.2026, or the next release of the agent, whichever comes first; renewed on the evidence of the quarter |
| Deputy | the Head of Customer Support signs in the owner’s absence, within the same limits |
The knowledge that applies
What does the bank know about this customer now? what the bank knows about this customer; fixed by the moment the offer is sent; owned by the customer data team, with the specialist support team for the flags.
- file as at 07:00 the agent’s nightly copy · no support flag · arrears €240
- customer record, 09:40 on 15.09 support flag set by the specialist support team: the customer asked for help after losing her job · arrears €240
What applies: an offer at 10:07 → the record as at 10:07 applies · a flag set at 09:40 the same morning is part of it
The agent’s copy of the customer file refreshes overnight. At 10:07 on 15.09 it still shows no support flag, and the agent drafts a standard offer in good faith. Only the check against the customer record catches the flag before the message is sent.
The check, at the act
| Identity | collections-agent-05, acting for Collections |
| Release | v1.3 · approved and validated for this workflow |
| Applicable basis | the customer record as at 10:07 on 14.09 · no support flag · forbearance policy v7 |
| Mandate | CO-03.4 active · arrangement RA-2 · arrears €240 within €2,500 · six months within six |
| Exact action | offer text RA-2-T3: €85 a month for six months, unchanged since declared |
| Current state | no offer sent before · no open complaint · no legal action · €400,000 daily limit not reached, permits in flight counted |
Outcome: permit · sent once
The act, and the customer
The messaging service executes the act: the offer sent to the customer. The agent may not mention legal action, a default notice, or a fee not yet charged. It cannot send the offer itself: the messaging service sends only an offer that carries the check’s permit.
The agent can explain the arrangements the policy allows, say that it is an AI system, hand over to a person at any point, and send an offer within the mandate. The customer asks: “Can I pay less for a while?”
The loop: The same flag, three times
Rule R-11, within seven days. Restored after 40.
- 15.09 Conversation 2219 referred: a support flag set at 09:40 is in the customer record; the agent’s copy of 07:00 predates it REFER · 1
One referral. Each one counts against the mandate’s review trigger. - 17.09 Conversation 2240, same agent, same reason REFER · 2
Two referrals for the same reason, from the same agent. - 19.09 Conversation 2263 has the same mismatch. R-11 is triggered after three referrals for the same reason within seven days NARROW
Three referrals: the rule narrows the mandate to recommend. The release does not change. - 21.09 Review CR-044: the agent’s copy of the customer file refreshes overnight, so flags set during the day reach it the next morning. The customer data team streams flag changes to it and verifies 25 lookups; no offer went to a flagged customer CAUSE: SOURCE DATA
The cause is fixed at the source, by the team that owns the customer file. - 24.09 After 40 clean offers from a test chosen for the cause, sampled by the conduct team, the Head of Collections and the Head of Conduct Risk sign CO-03.6, and R-11 is re-armed. The three referrals remain in the record RESTORE
Forty clean offers from a test chosen for the cause, sampled by people who did not build the agent, and two signatures restore it. The mandate changed twice; the release never did.
One record, every reader
| Who | Asks | Reads |
|---|---|---|
| CISO security and resilience | Who acted, and was it contained? | Its own identity. One gated message, nothing sent. |
| CTO architecture | Which model, and which release? | Release v1.3, two model tiers. |
| CFO finance | What did this conversation cost? | €0.24 in tokens, €7.33 in review. |
| Business owner Head of Collections | Who decided, and under which mandate? | Referred, then handled by a specialist. |
| Second line Head of Conduct Risk | Was the customer treated fairly, and can we show it? | Every version, on every line. |
| CRO risk appetite and the board | Did the controls hold within appetite? | No offer reached a flagged customer. |
The record of the two acts, field by field
The fields of the record line, as part three gives them, filled for the clean act and for the referral. A field with two lines gives the agent’s line and the person’s, marked O2 and S1.
| Field | Conversation 2214 · the clean act 14.09.2026 · the offer permitted at 10:07, delivered in the 10:10 batch | Conversation 2219 · the referral 15.09.2026 · the offer referred at 10:07, the conversation taken over by a specialist at 10:12 |
|---|---|---|
| Before the act · what the check read | ||
| whenthe second the check decided, and the second the act committed | decided 14.09.2026 10:07:03 · committed 10:10:00, the messaging batch · delivered 10:10:04 | O2 referred 15.09.2026 10:07:11S1 decided 15.09.2026 10:12:40 · message delivered 11:20 · the arrangement recorded 11:22 |
| the agent and its identitywhich agent, acting for whom, under its own identity, and how long its credential lived | collections-agent-05, acting for Collections · its own identity · token issued 10:02:14, valid 15 minutes · disclosed as an AI system at 10:02:20, in the first line of the conversation, the customer told she can ask for a person | O2 collections-agent-05, acting for Collections · its own identity · token valid 15 minutes · disclosed as an AI system at 09:58:04, in the first line of the conversation, the customer told she can ask for a personS1 specialist S-061, the specialist support team · her own login |
| the releasethe release id, each model by version and hash, the prompt set, the validation report | v1.3 · tier-1 model 2026.06.1 (7c41e0) · tier-2 model 2026.05.2 (e9a3b7) · prompt set collections-talk 1.3, with the may-not-say list · validated by model risk, MRV-047, 20.07.2026 | O2 v1.3 · tier-1 model 2026.06.1 (7c41e0) · tier-2 model 2026.05.2 (e9a3b7) · prompt set collections-talk 1.3S1 none · a person took the conversation over |
| the basiseach claim the act relied on, its version, and its standing at that second on both axes: evidential warrant, and authority | Customer C-5521 carries no support flag · the customer record as at 10:07 on 14.09 · read through the check · warrant validated · current to the second · authority: the specialist support team, who set and lift flags · the customer data teamC-5521 has €95 a month left after essential spending · the conversation, 10:06 · the customer’s own figures · warrant provisional · the customer’s own statement, unverified · authority: the customerA reduced payment for up to six months on arrears to €2,500 is a standard arrangement, RA-2 · forbearance policy v7 §3 · template RA-2-T3 · warrant foundational · in force · authority: the Head of Collections, with conduct risk | Customer C-5538 carries no support flag · declared: the file as at 07:00 on 15.09, the nightly copy · superseded at 09:40 · warrant fails on currency · contradicted by the customer record · authority: the customer data teamCustomer C-5538 is flagged for specialist support since 09:40 on 15.09 · applicable: the customer record · set by the specialist support team at 09:40 · read by the check at 10:07 · warrant validated · current · authority: the specialist support teamA flagged customer receives no standard arrangement from the agent · mandate CO-03.4, the never-to line · forbearance policy v7 §8 · warrant foundational · in force · authority: the Head of Collections, with conduct risk |
| the mandate versionthe mandate in force at that second, with its level and its limit | CO-03.4 · since 01.08.2026 · decide · standard arrangements RA-1 to RA-3 · arrears to €2,500 · €400,000 of arrears under new offers a day across the deployment | O2 CO-03.4 · decide · RA-1 to RA-3 · arrears to €2,500S1 the specialist’s authority · payment breaks and bespoke plans · the forbearance procedure |
| the control standardthe control standard version and the rule set the check applied | CS-11 v2026.2 · rule set RS-CO-03 r5 | CS-11 v2026.2 · rule set RS-CO-03 r5 |
| the consequence tierthe tier the act was classified into, and the version of the taxonomy that classified it | routine · taxonomy CT-2026.1 · a standard arrangement on arrears of €240, one customer, withdrawable, no fee, no money moved | critical · taxonomy CT-2026.1 · a customer flagged for specialist support: never the agent; a specialist decided it |
| At the act · what the check decided | ||
| the check’s decisionpermit, refer, or block, how many of the six inputs held, and the reason code | PERMIT · six of six · reason code OK | O2 REFER · five of six · reason code BASIS-01: declared file 07:00, record 09:40 with a support flag · owner: specialist supportS1 ARRANGE · the specialist’s decision |
| the exact actwhat was done, to whom, for how much, under which id, once | send offer RA-2-T3 to C-5521 in conversation 2214 · €85 a month for six months · M2214-O1 · once | O2 proposed: offer RA-2 at €85 a month for six months to C-5538 · M2219-O2 · never sentS1 a three-month payment break for C-5538 on loan L-3417 · M2219-S1 · once |
| the permitits id and what it was bound to: the mandate version, the release, the basis version, the exact act; and how long it held | PR-2214-1 · bound to CO-03.4, release v1.3, the customer record as at 10:07 and policy v7, the exact text of RA-2-T3 · valid for the next messaging batch | O2 none · the conversation went to the specialist, with a holding message that promised a person and no arrangementS1 none needed · a person’s arrangement, recorded in the loan system |
| After the act · what came back | ||
| the receiptwhat the receiving system returned, and the reconciliation against it: one permit, one act, one receipt | D-2214 · delivered by the messaging service 10:10:04 · reconciled against the messaging log and the loan system: one permit, one message, one receipt | O2 noneS1 D-2219 · the specialist’s message delivered 11:20 · the payment break recorded in the loan system 11:22 · reconciled: one arrangement, one record |
| the human decisionwhere a person decided: who, under which authority, what they confirmed, and when | none needed | O2 none yet · referred to a person with the reasonS1 specialist S-061 took the conversation over at 10:12 and agreed a three-month payment break |
| the costwhat the decision cost in tokens, and in a person’s time where one was needed | €0.24 in tokens · no specialist time | O2 €0.24 in tokensS1 €7.33 of a specialist’s time |
| retentionhow long the record, the manifest, and the permits are kept, and personal data inside them by its purpose | the record, the manifest, and the permits: six years from the end of the arrangement, the period the bank sets for conduct decisions of this tier (illustrative) · the conversation and the personal data in it by purpose and retention rule · a corrected fact is a new, linked entry | the record, the manifest, and the permits: six years from the end of the arrangement, the period the bank sets for conduct decisions of this tier (illustrative) · the conversation and the personal data in it by purpose and retention rule · a corrected fact is a new, linked entry |
control standard CS-11, version 2026.2 · rule set RS-CO-03 r5: refer any flag, any open complaint, any legal action, any offer outside RA-1 to RA-3, any mismatch of basis · CT-2026.1 · the bank’s consequence taxonomy · proposed by the CRO with conduct risk and Collections, set by the board, 06.2026 · ids, dates, and figures invented.
The business case
120,000 conversations a year, 50% eligible and 80% adopted; 25 minutes saved on each at €55 an hour, 65% realised. Run cost €350,000 a year; set-up €600,000. Fewer defaults, earlier arrangements, and complaints avoided are not yet included.
The people, on the day the mandate narrows
The specialists do this work today. The person who receives a referral holds at least the authority of the mandate the agent acted under, its limit included. Specialist S-061 can agree a payment break or a bespoke plan; the agent offers standard arrangements on arrears up to €2,500, and never to a flagged customer. On the day after a long weekend, missed payments and messages bunch after a long weekend, and the conversations double
What the law asks here
| Duty | Why here | Evidence | Boxes |
|---|---|---|---|
| Conduct rules on arrears and forbearance a lender deals with a customer in payment difficulty | the agent offers arrangements to customers in payment difficulty | forbearance that fits the situation; particular care with customers in vulnerable circumstances; every support flag honoured before an offer | e4 w3 w4 w6 |
| Consumer Credit Directive II consumer credit agreements concluded from 20 November 2026 | arrears on consumer credit agreements concluded from 20 November 2026; earlier agreements stay under Directive 2008/48, which since 30 December 2023 also asks for reasonable forbearance before enforcement (Article 16a) | human intervention, an explanation, and a review of a credit decision, on request; reasonable forbearance before enforcement | w3 w4 w5 w6 |
| GDPR, Article 22 (to be tested) a decision is solely automated and has a legal or similarly significant effect: a test the firm applies per type of decision | to be tested: the agent weighs a person's affordability and the offer changes what she pays; where it applies, Article 22(2)(a), necessary for the contract, with the 22(3) safeguards; a referred offer is a person's decision | a route to a person on request, with a time; reasons that explain the procedure and principles actually applied (CJEU C-203/22) | w4 w5 w6 |
| GDPR, Articles 15, 16, 17 personal data is processed | the customer file, and the support flag | access to the data on request; a corrected fact as a linked entry; retention by purpose, the storage-limitation principle | w5 p5 |
| EU AI Act, high-risk (to be tested) the use is on Annex III, among them the creditworthiness of natural persons (5(b)), life and health pricing (5(c)), and essential public benefits (5(a)), and Article 6(3) does not take it out | arguable: the agent weighs a person's affordability, which Annex III point 5(b) covers for creditworthiness; the bank records its reasoning | the classification, with its reasoning, in the agent portfolio; if high-risk, human oversight and logs | e1 w1 w4 |
| EU AI Act, Articles 4 and 50 any provider or deployer; Article 50 when an AI system talks to people, since 2 August 2026 | Article 50: the agent talks to the customer, who is told it is an AI system; Article 4 for the specialists | measures to support the AI literacy of the people who decide referrals (Article 4 as reworded by the 2026 omnibus: the duty stays, no guaranteed level); telling the person she is talking to an AI system | e4 w4 |
| DORA the firm’s ICT, and its ICT third parties | the bank is a financial entity under DORA | identity and access control, under the ICT risk framework; incident classification and reporting; the register of ICT third-party arrangements; testing | p1 p3 p5 p6 e1 e4 |
| EBA guidelines on restrictive measures | no sanctions screening in this decision | ||
| EIOPA opinion on AI governance (6 August 2025) | not an insurer | ||
Dated 11 October 2026; from the shared duty table; not legal advice.
Notes on the case
- The exact action the check reads is the text of the offer from an approved template, with its numbers; a message written freely by the model does not pass the check.
- Every customer flagged for specialist support stays with people. The mandate never covers them, and an offer sent to one narrows the mandate at once (R-11V).
- The customer is told she is talking to an AI system, as the AI Act’s transparency rules require of systems that talk to people, and can ask for a person at any point. Whether a collections conversation is on the AI Act’s high-risk list is arguable: Annex III point 5(b) covers evaluating the creditworthiness of natural persons, and the agent weighs a person’s affordability for an arrangement on an existing debt, with no new credit granted. The bank records its reasoning.
- The check gates the offer, not the conversation. A flag the agent’s copy misses is caught at the offer, after the customer has already spoken to the agent; a bank that wants the flag to stop the conversation itself puts a second check at its start.
- Figures are illustrative: 120,000 contacts a year, half eligible, 25 minutes saved per conversation, a referral rate of 20%. The loop’s counts and thresholds are illustrative too.
- The Consumer Credit Directive II forbearance duty (Article 35) is paraphrased, and it covers agreements concluded from 20 November 2026 (Article 47); the case’s existing loans stay under the earlier rules. A compliance reader should confirm the wording against Directive (EU) 2023/2225 and the national transposition.