All use cases

Upsell & Cross-sell

Pre-approved lending offer from account signals

A customer is about to cover a big bill from savings they will need next month — the agent offers the line of credit they already qualify for, with the cost shown plainly.

Get aheadNext best thingBehavioral triggerSystem triggerRisk triggerIn-appChatPushEmailLending

What it does

Customers run into credit needs the account can already see coming: a cash-flow gap before payday, a large upcoming spend draining a buffer, a strong repayment record that says a better facility is warranted. Lenders sit on those signals and either miss the moment or push a blanket credit ad that ignores affordability. The agent reads account behavior, repayment history, and eligibility flags, and surfaces a pre-approved, suitable credit product the moment the signals fit — framed around whether it actually helps the customer, with the real cost spelled out, not a balance-transfer hook.

How it works

  1. 1
    Trigger. an account signal fires — a recurring cash-flow gap, a large scheduled debit against a thin balance, or a repayment-history threshold that unlocks a higher facility.
  2. 2
    Decision. the agent checks the customer's memory (products held, offers previously declined) against affordability and suitability policy, and confirms the pre-approval limit before composing anything; the quality judge gates the message so only an offer the customer genuinely qualifies for and can afford goes out.
  3. 3
    Action. a short in-app or chat message that names the observed pattern and the fitting product — an overdraft, a line of credit, a BNPL upgrade — with the representative cost, the repayment shape, and an affordability note drawn from the customer's own numbers; push and email are fallbacks for customers not in the app.
  4. 4
    Follow-through. the response is written back to memory and sets a cool-down; if the account picture changes before the send (the gap closes, the balance recovers), the stale offer is cancelled. Drawing the credit completes in the lender's own regulated application and secure step — the agent hands off, it never books the facility itself.
Example
AgentYour rent debit lands Tuesday and this month it would dip your balance below your usual buffer. Based on your account you are pre-approved for a flexible line of credit — here is what it would cost if you used it just to bridge that, and the repayment over three months.
CustomerWhat is the rate, and is there a fee if I do not use it?
AgentThe representative APR is shown here and there is no fee for holding it unused — you only pay on what you draw. If it fits, I will take you to the lender's application to confirm; the regulated steps happen there.

Configuration

How the agent is wired for this use case.

Triggera cashflow_gap_detected, large_debit_scheduled, or repayment_threshold_met event from the core-banking / account-aggregation stream.
Tools & actions
  • Core-banking / account-aggregation stream · read cash-flow, scheduled debits, balance and repayment-history events
  • Eligibility & affordability engine · confirm the pre-approval limit and run the suitability/affordability check before any offer is composed
  • Customer profile / CRM · read products held, consent state, memory of prior offers and declines
  • In-app messaging / push / email surface · deliver the offer with representative cost and repayment shape
  • Loan servicing / origination system · hand off to the lender's own regulated application and secure step (the agent never books the facility)
Autonomyjudge-gated and unattended for surfacing the pre-approved offer; the credit drawdown is a money-moving, regulated step that completes only in the lender's own application flow under a consumer-credit policy class, with the affordability check enforced before composition.
Channelsin-app · chat · push · email
Escalationany sign of financial difficulty or vulnerability (the cash-flow gap reads as hardship, not convenience), a complaint, or an affordability fail routes to a human and suppresses the offer.

What you need

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

Signals

core-banking events (cash-flow gaps, scheduled large debits, balance thresholds), repayment-history events, pre-approval and eligibility flags

Data

products held, affordability and suitability assessment inputs, pre-approval limits, consent state, memory of past offers and declines

Guardrails

affordability and suitability rules enforced before any offer is composed; vulnerability and hardship detection that suppresses the offer and routes to a human; consumer-credit communications and pre-approval-validity policy; judge gating on every unprompted message; frequency caps and decline cool-downs; the lender keeps owning the send channels and the regulated application step

Metrics it moves

  • attach-rateup, as a credit product attaches to deposit/transaction customers at the moment the account makes the case, not in a quarterly campaign
  • arpuup, because the facility adds revenue from a customer the lender already holds, framed around fit
  • conversion-rateup on credit offers, since a pre-approved, affordability-checked offer at the right moment converts far better than a blanket ad

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