All use cases

Win back

Dormant account reactivation (banking)

The account is still open, the balance is still sitting there — but there's been no login, no card swipe, no transfer in months, and one day it quietly moves to another bank.

Get aheadTime-based triggerRisk triggerBehavioral triggerPushEmailSMSIn-appFintech

What it does

A banking customer goes dormant long before they formally leave: logins stop, the card stops being used, the balance sits idle, a product they signed up for is never funded. Nothing alarms the bank because nothing has technically gone wrong — and that silence is exactly how deposits and relationships drift away to a competitor. The agent watches for dormancy and reaches out with a reason that fits this customer: a product they'd actually use, a fee they could avoid, a feature they never tried. Catching it while the account is still open keeps the balance and the relationship that a cold win-back later rarely recovers.

How it works

  1. 1
    Trigger. a dormancy condition fires — no logins or transactions past a defined window, card usage lapsed, or a product opened but never funded — and the agent picks per-customer timing rather than one batched campaign send.
  2. 2
    Decision. the agent reads the account state and memory — products held versus used, balance trend, what would genuinely help — against suppression and consent rules, and chooses the angle: a fee the customer keeps paying that a different product avoids, a savings feature their balance is sitting idle without, a card they never activated. A judge gates the message for relevance, tone, and regulated wording.
  3. 3
    Action. a specific, useful message lands on the customer's consented channel — push, in-app, email, or SMS — leading with the reason, not a generic "we miss you," and opening a thread where the customer can act or ask.
  4. 4
    Follow-through. the outcome writes back to memory; if the customer logs in or transacts on their own first, the pending outreach is cancelled; recovered activity and retained balances are measured per cohort against a holdout so the program proves it kept deposits that would have left.
Example
AgentHi — we noticed your everyday account has been quiet for a few months while your savings pot sits unused. You're earning nothing on the balance sitting in checking. Moving it across takes one tap and you can pull it back any time — want me to show you the rate first?
CustomerWhat's the rate, and is there any lock-in?
AgentNo lock-in — instant access, and here's the current rate against what you're earning now, which is zero. If it looks right, the move happens inside the app in one step. Nothing changes on your account until you confirm it there.

Configuration

How the agent is wired for this use case.

Triggera dormancy_detected signal from the core banking platform — no logins/transactions past a window, lapsed card usage, or an opened-but-unfunded product.
Tools & actions
  • Core banking platform · read account activity, balance trend, products held, and funding state
  • CRM / customer 360 · read tenure, prior offers, and consent; log the reactivation attempt and outcome
  • Product-eligibility service · match the dormant customer to a genuinely fitting product, fee-saving, or feature
  • Customer memory · recall what was offered and declined; cancel pending outreach on organic return
  • Messaging channel · deliver the push, in-app, email, or SMS reactivation message and run the thread
Autonomydormancy detection, angle selection, and outreach run unattended under judge gating; any product opening, money movement, or balance transfer is confirmation-gated and executes only in the bank's own secure flow. Money-moving steps follow a regulated-banking policy class — the agent guides, the customer confirms, the bank's app moves the money.
Channelspush · email · sms · in-app
Escalationa complaint, a suspected-vulnerability signal, a fraud concern, or a request for regulated financial advice hands off to the right human team with full context.

What you need

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

Signals

account-dormancy indicators (no logins/transactions, lapsed card usage, unfunded products), balance-trend and engagement-decay data.

Data

products held versus used, balance and activity history, tenure, channel consent, persistent memory of prior offers and declines.

Guardrails

judge gating on every unprompted message; regulated-communications wording and clear opt-out; no money movement or product opening by the agent — every such step is customer-confirmed in the bank's own flow; suppression of opted-out and do-not-contact customers; frequency caps; stale-outreach cancellation on organic return; per-cohort holdout for honest measurement.

Metrics it moves

  • reactivation-rateup, because the message leads with a reason this dormant customer would actually act on, not a generic re-engagement blast
  • dau-mauup, as idle accounts return to logins, transactions, and card usage
  • ltvup, by retaining deposits and the relationship before they quietly move to a competitor

Related use cases

Win back

Dormant-buyer reactivation

the retail repeat-purchase parent this specialises for banking dormancy

Upsell & Cross-sell

Banking product cross-sell from account signals

the signal-to-product logic, applied to active rather than dormant accounts

Win back

Borrower lifecycle reactivation

the lending-side dormant sibling, where the relationship at risk is a loan rather than a deposit

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