All use cases

Onboard / Activate

Activation companion for new banking customers

A new account is opened in minutes, then sits half-used — no direct deposit, no first transfer, the card still in the envelope — and quietly never becomes the one the customer actually banks with.

Next best thingGet aheadBehavioral triggerTime-based triggerSystem triggerIn-appChatPushEmailFintech

What it does

A new banking customer rarely leaves with a complaint; they leave by never arriving. The account opens, but the steps that make it their primary account — routing a paycheck in, sending a first transfer, switching on the card, trying the savings pot — are the steps most people skip, and an account that never activates is an account that churns before it ever earned anything. The companion lives in the app through the first weeks: it answers product and fee questions in chat, deep-links to the exact activation step that matters next, and when a key step is skipped past its window it nudges with one specific, supportive action. Support and product guidance run as one agent, so the customer is helped and moved forward in the same place.

How it works

  1. 1
    Trigger. behavioral, time, and system signals from the banking platform — an account opened but unfunded, a card issued but never enabled, direct deposit not set up by day 14, a savings feature never opened.
  2. 2
    Decision. the agent weighs progress against the activation path that predicts a retained primary-account relationship, recalls what this customer has already done and asked, and picks one next step rather than a generic checklist. Every unprompted nudge clears a quality judge before it sends.
  3. 3
    Action. an in-app message or push that deep-links to the precise step — set up direct deposit, make the first transfer, enable the card — and any question it raises is answered in the same thread, on the customer's consented channel.
  4. 4
    Follow-through. if the customer completes the step on their own, the queued nudge is cancelled before it sends; activation events write back to the bank's analytics; lift is measured against a holdout so the claimed activation gain is proven, not assumed.
Example
AgentWelcome — your account's open and ready. The one thing that makes everything else work is setting up your paycheck to land here. Want me to show you the two-minute switch? Most people do this first.
CustomerIs my card active yet? It arrived but I haven't used it.
AgentNot yet — it needs one tap to enable, here's the direct link. Once it's on, you can add it to your phone wallet too. And whenever you're ready, the direct-deposit switch is right where we left it.

Configuration

How the agent is wired for this use case.

Triggeran activation_step_missed condition from the core banking platform — account opened but unfunded, card issued but not enabled, direct deposit absent past day 14, savings feature never opened.
Tools & actions
  • Core banking platform · read account state, funding status, card-enable state, and which activation milestones are complete
  • CRM / customer 360 · read tenure, channel consent, and prior nudges; log each activation attempt and outcome
  • Product knowledge base · answer fee, feature, and how-to questions in plain language and deep-link the right setup step
  • Customer memory · recall what this customer has done and asked; cancel a queued nudge when the step is completed organically
  • Messaging channel · deliver the in-app, push, or email nudge and run the conversation
Autonomysignal detection, step selection, and nudges run unattended under judge gating; the agent never funds the account, moves money, or enables the card itself — every such step is customer-confirmed inside the bank's own secure flow, following a regulated-banking policy class.
Channelsin-app · chat · push · email
Escalationa complaint, a suspected-fraud or vulnerability signal, a failed-verification block, 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

banking activation events (account_funded, card_enabled, direct_deposit_set, transfer_completed, savings-feature opened) plus stall timers on the activation path.

Data

the activation path that predicts a retained primary-account relationship, the product and fee catalog, the customer's progress so far, channel consent and notification preferences, persistent memory.

Guardrails

judge gating on every unprompted message; regulated-communications wording, quiet hours, and frequency caps so the companion never reads as a campaign engine; no funding, money movement, or card enablement by the agent — each is customer-confirmed in the bank's secure flow; stale-nudge cancellation on organic completion; holdout measurement for honest activation lift.

Metrics it moves

  • activation-rateup, by walking each new customer to the steps that make this their primary account instead of hoping they find them
  • feature-adoptionup, because deep-linked nudges put direct deposit, the card, and savings in front of the right customer at the right moment
  • time-to-valuedown, the companion compresses the half-used first weeks into a funded, active relationship
  • churndown, customers who activate the primary-account behaviors early are the ones who stay

Related use cases

Onboard / Activate

In-app activation companion

the all-vertical parent this specialises for banking activation milestones

Upsell & Cross-sell

Banking product cross-sell from account signals

the same signal engine pointed at cross-sell once the account is active

Win back

Dormant account reactivation (banking)

the win-back sibling for when an activated account later goes quiet

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