Overdraft opt-in and opt-out

How do we take an overdraft opt-in or opt-out from any channel with the required notice shown first and the election recorded in the core?

Make the election a process with the notice in front of it. Callvu identifies the customer, shows the Reg E overdraft notice on a process-controlled screen, takes the affirmative choice to opt in (or the choice to revoke), sends the confirmation, and writes the election with its timestamp to the core. An agent cannot record a choice for the customer, and no fee is charged before the election is on the record.

In scopeSimpleCallvu moves: prefill, write back

Last updated November 6, 2026.

The problem today

The customer was opted in on a call, and the proof is a code the agent set.

Today, without Callvu

A customer asks why they paid an overdraft fee on a debit card purchase. The bank's answer depends on whether they opted in. The core shows a flag. Who set it, what the customer was shown, and whether they said yes, is a call from two years ago.

Reg E does not allow a fee for paying an ATM or one-time debit card overdraft unless the bank gave the customer the required notice, the customer affirmatively consented, and the bank confirmed the consent in writing or electronically. A pre-ticked box or a flag set by an agent does not meet it. The notice has required content and must be segregated from other information.

The volume is in the small moments: a new account opening, a call about a declined card, a chat. Each one is where the election gets taken, and each one needs the same notice and the same proof.

How it runs

From the requestto the system of record.

A customer asks about overdraft coverage in the app, on the web, on a call, in a branch, at account opening, or through an AI agent. Callvu identifies the customer and opens the election for the account.

Customer
Reads the notice, makes the affirmative choice to opt in or the choice to revoke, and receives the confirmation.
Callvu
Identifies, shows the notice, captures the election on a process-controlled screen, confirms, and writes the election to the core.
  1. Identify and prefill

    The customer is authenticated under the bank's policy for the channel. Callvu reads the account and its current election (opted in, not opted in, revoked, with dates) from the core and shows it.

  2. Show the notice

    The Reg E overdraft notice, in the required form and content (the bank's overdraft service, the fees, the limit, the choice and how to revoke it), is shown in full on a process-controlled screen, segregated from everything else, in the channel the customer consented to.

  3. Capture the election

    The customer makes the affirmative choice to opt in, or chooses to revoke an existing opt-in, with a timestamp. An agent on a call sends the customer the link; the agent cannot make the choice. Nothing is pre-selected.

  4. Confirm and write back

    The confirmation of the consent, with a statement of the right to revoke, is sent to the customer, and the election with its date, the notice version shown and the confirmation record are written to the core. A revocation is effective as soon as reasonably practicable and is written the same way.

Where it ends: The election is in the core with the notice shown, the affirmative choice, the confirmation and the timestamps, and the fee behavior follows it from that moment. The Decision Trace shows the notice version and the choice; the Audit Trace shows every step.

Runtime enforcement

What is enforcedwhile the work runs.

The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.

The handoff

Between the front doorand the back office.

The front door

Any channel. On a call or in a chat, the agent or the AI agent sends the customer the link; the notice and the choice happen on the customer's own screen.

The back office

Nothing to key. The election reaches the core from the customer's choice, and the examiner's proof is the record, not a call recording.

The Decision Desk

  • There is no Decision Desk step: the election is the customer's alone. A fee dispute that cites the election is answered from the record.

Proof

In scope.Proof at scale, not one process at a time.

The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.

More than 1,000 processes are live across Callvu customers.

Across Callvu customers

Banca Transilvania automated more than 100 workflows with Callvu.

BNK-04

Bank Leumi digitized all loan application and servicing workflows within six months, and dozens more processes since.

BNK-01

Questions

What buyers ask next,answered plainly.

Can an agent opt the customer in on a call?

No. The agent sends the customer a link; the notice is shown and the choice is made on the customer's own screen. That is what Reg E's affirmative consent requires.

What does the record hold?

The notice version shown, the time, the customer's choice, the confirmation sent with the right to revoke, and the election in the core.

How is a revocation handled?

The customer revokes in any channel; it is written to the core the same day and the fee behavior follows it.

Does this change the account terms for customers who do not opt in?

No. The same terms and features are available either way, as the rule requires.

Related processes

Bring this process, or the one that costs you most.

We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.