How to handle requests to change a repayment due date with an AI agent

Moving a due date to match pay day is a safe change for an agent, as long as it checks three things first: the product allows it, the customer is not asking because they cannot pay, and the customer understands the first payment after the move. Then it updates the schedule and the collection date together and confirms in writing.

What is the process, and who owns it?

Customers ask to move their loan or card repayment date for ordinary reasons: a new job pays on a different day, rent goes out first, a benefit payment moved. Aligning the due date with income reduces missed payments, which is good for both sides.

The change has more parts than it looks. Moving the date creates one longer or shorter period, so interest for that period changes and the first payment after the move may differ. The direct debit or standing collection must move too, or the lender will collect on the old date. Products usually limit how often the date can change and which days are allowed.

The head of lending operations owns the rules. A named servicing team leader takes exceptions. The financial support team takes customers who are really asking for more time to pay. For the wider frame, see our guide to AI agents in banking.

What are the steps, and who acts at each one?

1. Agent, depth 1: authenticates and reads the account. Product, current due date, payment history, previous date changes, arrears, collection method. Evidence: facts used.
2. Agent, depth 1: asks why. If the answer is about income timing, continue. If it is about not having the money, the case goes to step 9. Evidence: the customer's reason.
3. Agent, depth 1: checks eligibility. Product allows changes; no change within the restricted period; account not in arrears; requested day within the allowed range. Evidence: eligibility result per condition.
4. Agent, depth 2: shows the effect. The new date, the length of the bridging period, the first payment amount after the move, and any change in total interest, all as amounts. Evidence: the illustration shown.
5. Agent, depth 1: confirms the customer's choice. Evidence: confirmation recorded.
6. Agent, depth 3: applies the change in the servicing system. Evidence: schedule change.
7. Agent, depth 3: moves the collection date to match, so the old date does not trigger a collection. Evidence: collection change, timed before the next old-date collection.
8. Agent, depth 2: confirms in writing. Old date, new date, first payment amount and date. Evidence: letter or message sent.
9. Person, support specialist or team leader: takes difficulty cases and exceptions. Requests outside the rules, accounts in arrears, customers who cannot pay. Evidence: decision.

Which controls matter, and what evidence do they leave?

Rules as bounds. Frequency, allowed days and arrears status are checked when the change is applied. Evidence: verdict citing each rule.

Schedule and collection change together. If one fails, the other is rolled back and the case goes to a person. Evidence: paired change records.

Timing against the next collection. If the old-date collection is too close to stop, the agent says so and explains what will happen. Evidence: timing check.

One change per request. The agent does not combine a date change with an amount or term change in the same action; each is its own capability. Evidence: separate verdicts.

Difficulty screened on every request. Moving a date later is sometimes a request for time. Evidence: screening result.

Clear illustration. The customer sees amounts, not percentages or jargon. If they need it in another format, the agent arranges it; see whether an AI agent can handle accessibility requests. Evidence: illustration and format.

What should you measure?

• Changes applied per week, and time from request to confirmation.
• Missed first payments after a change. Should be low; a rise suggests customers misunderstood the bridging payment.
• Collections on the old date after a change. Target zero.
• Requests routed to support at step 2.
• Repeat requests from the same customer within the restricted period.
• Time between the change and the next collection, to catch changes made too close to a collection.

Where does it usually go wrong?

The collection is not moved. The lender collects on the old date as well as the new one, and the customer is overdrawn.

The bridging payment surprises the customer. A longer first period means a larger first payment. Show it in money.

Difficulty hides behind the request. "Can I move it to the end of the month?" from a customer who cannot pay this month is a request for help. Where a longer arrangement is needed, see agreeing repayment plans within set limits and the repayment plan limits matrix.

Accounts in arrears are moved. Changing the due date on an account in arrears can obscure the arrears. Keep these with a person.

Card and loan rules are mixed. A credit card's statement and payment dates work differently from a loan's. Separate capabilities. The same caution applies to related current account changes such as overdraft requests.