All use cases

Collect / Recover

Upcoming-payment reminder and autopay rescue (lending)

The installment that's about to be missed doesn't have to be. The agent sees the broken autopay or the tight payday today and gets it fixed before the account ever slips into arrears.

Get aheadTime-based triggerSystem triggerRisk triggerSMSEmailPushVoiceChatLending

What it does

Most arrears begin as a payment that was never going to land: a direct-debit mandate that failed to set up at funding, a card on autopay that expired, an installment date that falls just before payday on an account that looks tight. Once the payment is missed, the account enters the collections funnel and a borrower who simply forgot or had a timing problem gets treated like a debtor. The agent works the days before the installment instead: it confirms the upcoming payment, checks that autopay or direct debit is healthy and repairs it through a secure link if not, and sends a judgment-timed reminder so a borrower who would otherwise miss a date pays it cleanly and the relationship never starts to fray.

How it works

  1. 1
    Trigger. a time or risk signal ahead of an installment: an upcoming payment date, autopay or a direct-debit mandate flagged as failed or unset, an expiring card on file, or a pre-delinquency risk score crossing its threshold.
  2. 2
    Decision. the agent reads the loan's repayment schedule, the autopay status, and the borrower's history and channel preference, then weighs whether to nudge, repair the method, or stay silent because the payment is already covered. It frames the touch as a helpful heads-up, not a demand, and a quality judge gates the message before it goes.
  3. 3
    Action. a short reminder on the borrower's preferred channel that names the amount and date, and — where autopay is broken — carries a secure link to the lending provider's hosted page to repair the card or re-authorise the direct debit. Card details never pass through the conversation; the agent only confirms the method is set for the next installment.
  4. 4
    Follow-through. a repaired method or a confirmed manual payment writes back to the loan servicing record and cancels pending reminders for that cycle. If the installment then runs cleanly, the loop closes silently. If it's missed anyway, the full context hands off to arrears or collections so the borrower never has to re-explain.
Example
AgentHeads-up on your loan: your next repayment of the usual amount is due Friday, but the direct debit we had set up didn't go through last cycle. Want to fix that now so it runs automatically? Here's a secure link to re-authorise it.
CustomerYes please, and can I move the date to the 3rd? That's right after I get paid.
AgentDone — the mandate is re-authorised, and I've moved your repayment date to the 3rd from next month. Friday's payment is covered, and you shouldn't need another reminder from me.

Configuration

How the agent is wired for this use case.

Triggera time / risk event ahead of an installment — payment_due_soon, autopay_failed / unset direct-debit mandate, card_expiring, or a pre-delinquency risk score — emitted by the loan servicing system.
Tools & actions
  • Loan servicing system · read the repayment schedule, autopay status, and arrears state; write back the confirmed method and any agreed date change.
  • Payment provider · hand off to the lender's secure hosted page to repair the card or re-authorise the direct-debit mandate (the agent never touches card data).
  • Direct-debit / autopay engine · confirm the mandate is active and scheduled for the next installment, or flag it for repair.
  • Messaging channel · send the judgment-timed reminder, including an outbound voice call where the stakes or the borrower's preference warrant it.
  • CRM / servicing audit log · record the reminder, the method change, and any schedule adjustment for the regulated trail.
Autonomythe reminder, the autopay-health check, and a borrower-requested payment-date change run under judge gating inside the servicing policy; repairing the payment method completes only on the lender's secure hosted step, so no money-moving action and no card data ever sit inside the conversation.
Channelssms · email · push · voice · chat
Escalationa method that can't be repaired before the due date, a borrower who signals hardship or can't afford the installment, or a dispute over the amount hands off to a human servicing or hardship specialist.

What you need

The inputs this use case runs on. Your channels stay yours; the agent supplies the judgment.

Signals

upcoming-installment dates, autopay / direct-debit failure or unset flags, card-expiry events, pre-delinquency risk scores.

Data

loan and repayment-schedule state, autopay and mandate status, payment and contact history, consent and contact-window preferences, customer memory.

Guardrails

secure payment hand-off only, no card or mandate data in any conversation; regulated contact windows and frequency caps on reminders; reminder cancellation once the method is repaired or the installment clears; a hardship signal routes to a specialist rather than continuing as a payment nudge; judge gating on every unprompted message.

Metrics it moves

  • involuntary-churndown: broken autopay is repaired before the installment is missed, so the account never enters the arrears funnel over a timing or method glitch.
  • contact-ratedown: a healthy mandate confirmed before the run removes a class of missed-payment and collections conversations later in the loan.
  • recovered-revenueup: every installment that lands on schedule is repayment kept performing rather than chased after the fact.

See it on your own customer journey

Bring one drop-off, one churn cliff, or one silent segment. We will show you what a proactive agent with memory and judgment does with it.

Book a demo