Product conversion and rate changes
How do we move a customer to a different deposit product, or apply a rate rule, with eligibility checked and the disclosures delivered first?
Treat a product change as an opening and a closing in one. Callvu checks the customer's eligibility for the new product, shows the differences, delivers the new product's account disclosures before the change, applies the change-in-terms notice where a bank-initiated rate or product rule reduces what the customer gets, captures the customer's acceptance, and writes the change to the core with the right effective date.
In scopeSimpleCallvu moves: prefill, decide, write back
Last updated November 6, 2026.
The problem today
The customer is moved to the new product on the call, and the disclosures for it arrive with the next statement.
A customer asks to move from a basic checking account to one with interest, or the bank retires a product and migrates everyone to its successor, or a relationship rate stops applying because a balance fell. In each case the core is changed first and the paper follows, if it follows.
Reg DD treats the new product as a new account for disclosure purposes: the disclosures go before the change. A bank-initiated change that reduces the yield or adds a fee needs the 30-day change-in-terms notice. Eligibility for a product (an age, a relationship, a balance, a direct deposit) is a policy that has to be checked, not assumed from the conversation.
A migration of a retired product touches thousands of accounts at once, and the notice goes to all of them with a date that must hold.
How it runs
From the requestto the system of record.
A customer asks for a product change in any channel, or a rate or product rule applies (a product retirement, a relationship tier change, a promotional rate ending). Callvu opens the account and classifies the change.
- Customer
- Chooses or is informed, reads the disclosures and the notice, and accepts on their own phone where acceptance is required.
- Deposit operations
- Decides eligibility exceptions and rate exceptions in the Decision Desk, and approves bank-initiated migrations.
- Callvu
- Checks eligibility, delivers disclosures and notices on the right dates, captures acceptance, and writes the change to the core.
Prefill and classify
The current product, its terms, the balance and the relationship are read from the core. The change is classified: customer-requested product change, bank-initiated migration, or a rate rule applying. The classification sets the eligibility check, the disclosures and the notice.
Eligibility
The new product's eligibility rules from the bank's policy (age, relationship, minimum balance, direct deposit, account type) are checked against the core. An ineligible request is explained to the customer with what would make them eligible, or routed where policy allows an exception.
Disclose and notify
For a customer-requested change, the new product's account disclosures are delivered and the customer accepts before the change. For a bank-initiated change that reduces the yield or adds a fee, the change-in-terms notice goes out at least 30 calendar days before the effective date; a change that benefits the customer is disclosed with its date.
Decide and write back
A change inside the rules is written to the core with its effective date, the disclosures and the acceptance attached, and a confirmation goes to the customer. A rate exception or an eligibility exception goes to deposit operations in the Decision Desk with only the allowed outcomes. A migration runs on the approved date for every account in scope, each with its notice on record.
Where it ends: The customer is on the new product or rate in the core with the right effective date, and the disclosures, the notice and the acceptance are on record in the right order. The Decision Trace shows the eligibility and notice rules; 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
The customer in any channel, or the bank's own rate and product rules. Acceptance happens on the customer's phone.
The back office
Deposit operations approves migrations and decides exceptions; every change reaches the core with its disclosures and notice from Callvu.
The Decision Desk
- A rate exception, an eligibility exception, or the approval of a bank-initiated migration goes to deposit operations in the Decision Desk with the accounts in scope and only the allowed outcomes.
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.
Questions
What buyers ask next,answered plainly.
Does the customer see the new product's disclosures before the change?
Yes. For a customer-requested change the disclosures are delivered and accepted on the customer's phone before the change is written to the core.
How is a product retirement handled?
As a bank-initiated migration: the change-in-terms notice goes to every account in scope at least 30 days before the date, deposit operations approves the migration, and each account carries its notice record.
What if the customer is not eligible?
They are told why and what would make them eligible. Where the policy allows an exception, the request goes to deposit operations in the Decision Desk.
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.