Which Bank Calls Should an AI Voice Agent Answer?
Washington banks should start voice AI on public information and routing, verify identity by approved factors, and announce recording in the greeting.
In this guide
For a community bank in Seattle or Bellevue, the first AI voice agent should handle a narrow set of approved information requests and routing tasks. Public branch information and appointment requests are reasonable candidates to test. Account lookups need verified identity and a reliable data connection. Fraud, disputes, hardship and other urgent conversations need a prompt route to trained staff. Washington’s recording law also shapes the agent’s first words: recording a private phone call requires every participant’s consent, which the law treats as given once a recorded announcement says the call is about to be recorded.
The boundary is the action and information involved, not how ordinary the caller’s opening sentence sounds. “What is my balance?” can become “I did not make that withdrawal.” The agent must recognize the change and preserve the report, even if the original lookup worked.
Glia’s banking page markets routine voice self-service and routing to bank specialists. Treat that as a capability to verify against your systems. It does not tell you which calls your bank should automate or what share will resolve successfully.
Use the open scorecard to evaluate a voice AI proposal.
Define four call permissions
The call matrix below is a proposed deployment boundary for a first evaluation, not a legal safe harbor or a claim that every platform supports it.
| Caller’s task | Candidate response | Condition for proceeding |
|---|---|---|
| Ask for hours, locations or required appointment documents | Read an approved answer | Correct branch, current content and an owner for updates |
| Request an appointment or callback | Collect minimum details and propose a booking | Confirmed availability, clear consent and a recoverable handoff |
| Ask for account-specific balance or status | Read a permitted value from the bank system | Bank-approved authentication, authorized access and data freshness |
| Report fraud, a dispute, a lost card or financial difficulty | Capture the issue and route promptly | Named receiving team, urgent fallback and preserved report time |
Freeze-card actions, replacement cards, address changes, payments and fee adjustments deserve a separate authorization design. Do not include them merely because a vendor can expose a button or API. For the initial scope, route requests involving these actions to the established service process.
Likewise, a published rate is not a personalized offer. If rates are in scope, bind the answer to an approved product, effective date and relevant conditions. When the source is stale or the caller’s question requires interpretation, transfer the call instead of improvising.
Design the transfer before the greeting
Specify where each urgent or unsupported request goes during business hours and after hours. A generic callback promise is inadequate if nobody is responsible for receiving the task. Agree what the agent says when a live queue is unavailable and how the bank’s existing urgent reporting route remains reachable.
The transfer record should carry the caller’s stated problem, time received, verified identity status, relevant account reference and actions already completed. Limit sensitive information to the systems and staff authorized to receive it. A short summary helps, but staff need access to the original report if the summary is inaccurate.
The CFPB’s 2023 chatbot spotlight estimated that over 98 million users, about 37% of the U.S. population, engaged with a bank's chatbot in 2022, and it identifies inaccurate answers, failure to recognize disputes and barriers to human support as risks. It is not a voice-product certification. Have the bank’s compliance team translate applicable complaint, error-resolution, disclosure and recordkeeping obligations into the actual workflow.
Voice adds three risks that chat does not
Treat the caller’s voice as unverified, treat outbound AI calls as regulated calls, and get consent before recording.
First, authentication. FinCEN's November 2024 alert on deepfake fraud notes that criminals may use tools that generate synthetic audio and video to respond to live verification prompts, and that scammers use deepfake voices to impersonate trusted people. A voice agent should never accept how a caller sounds as proof of identity. Use the bank's approved authentication factors, and treat a request to change contact details, add a payee or move money as higher risk that belongs with staff.
Second, outbound calling. The Federal Communications Commission ruled in February 2024 that the Telephone Consumer Protection Act's restrictions on an "artificial or prerecorded voice" cover current AI technologies that generate human voices, so calls using them require the called party's prior express consent absent an emergency purpose or an exemption. If the same agent will place appointment, payment or collection calls, have compliance confirm consent records and every other rule that applies before it dials.
Third, Washington requires consent to record
Washington makes it unlawful to intercept or record a private communication transmitted by telephone without first obtaining the consent of all participants. Consent is considered obtained when one party announces to the others, in any reasonably effective manner, that the conversation is about to be recorded or transmitted, and if the call is recorded, the announcement must be recorded too (RCW 9.73.030). If the agent records or transcribes calls with Washington customers, put the announcement at the start of the greeting, confirm it is captured in the recording, and test that no recording or transcription starts before it plays, including on transferred and returned calls. Have counsel confirm how the statute applies to an automated agent and to any vendor that processes the audio.
Washington’s biometric laws and voice matching
If the platform matches callers by voice, check two more Washington statutes. The biometric identifier law lists voiceprints but does not apply in any manner to a financial institution or affiliate subject to Title V of the Gramm-Leach-Bliley Act (chapter 19.375 RCW). The My Health My Data Act treats voice recordings from which an identifier template can be extracted as biometric data, which it counts as consumer health data. It exempts personal information governed by and collected, used or disclosed under that federal act, and it does not restrict using such data to prevent, detect or respond to fraud and identity theft, though the entity bears the burden of showing that use qualifies (chapter 19.373 RCW). Have counsel confirm how both apply to the bank and to a voice vendor that is not itself a financial institution before voice matching is turned on.
Illinois recording and voiceprint rules
Illinois makes it eavesdropping to knowingly and intentionally use an eavesdropping device in a surreptitious manner to transmit or record a private conversation you are a party to without the consent of all other parties (720 ILCS 5/14-2), so the same plain announcement belongs in the greeting. Voiceprints raise a separate question. The Biometric Information Privacy Act lists a voiceprint as a biometric identifier. Before a private entity collects one, it must tell the person in writing that it is being collected, for what purpose and for how long, and receive a written release, which can be an electronic signature. Liquidated damages are $1,000 per negligent violation and $5,000 per intentional or reckless violation, or actual damages if greater, and repeated collection of the same identifier from the same person by the same method counts as one violation. The Act does not apply to a financial institution or affiliate subject to Title V of the Gramm-Leach-Bliley Act; that exemption does not mention vendors. Ask whether the platform creates voiceprints for authentication or caller matching, and have counsel confirm how the Act applies before that feature is turned on.
Use difficult calls in the acceptance test
Give the implementation team a bank-approved set of test conversations. Include callers who change topics, speak over the agent, use an unsupported language, provide incomplete details or request a person immediately. Include silence, background noise and failed authentication. Use authorized test data rather than exposing customer account details in a demonstration.
- Public answer: a holiday changes the branch schedule. The agent must use the current approved answer or acknowledge it cannot verify the hours.
- Account lookup: authentication fails. No account-specific information should be revealed while the caller is offered an appropriate recovery route.
- Urgent change of topic: a balance caller reports an unfamiliar transfer. The agent stops the routine flow and routes the report.
- System outage: the core cannot answer. The agent must not convert an old cached balance into a claim about the current balance.
- Incomplete transfer: no staff member accepts the handoff. The task remains visible and follows the bank’s agreed fallback.
Review transcripts and outcomes by call type. Count wrong answers, repeat calls, failed transfers and time to a qualified person, as well as completed self-service requests. A call ending without a live agent is not automatically a resolved call.
Estimate the workload after the pilot
Use observed call mix, handling time, repeat-contact rate and residual staff work to assess economics. Include telephony, software, integration, testing, monitoring and knowledge maintenance. Avoid applying another institution’s deflection percentage to your queue.
Expand one permission at a time after the relevant tests pass and staff can recover failed interactions. If the next candidate is loan-status service, establish which status the loan origination workflow can reliably provide. The broader finance operations plan should connect the phone answer to the work that actually resolves the customer’s request.
Quick answers
Can an AI voice agent verify a bank customer's identity?
Only through the bank's approved authentication factors, never by the caller's voice. FinCEN warns that criminals can use tools that generate synthetic audio to answer live verification prompts.
Can a bank use an AI voice for outbound calls?
Only with the right consent. Under the FCC's February 2024 ruling, AI-generated voices are an "artificial or prerecorded voice" under the TCPA, so calls using them require the called party's prior express consent absent an emergency purpose or exemption.
How many customers already use bank chatbots?
The CFPB estimated that over 98 million users, about 37% of the U.S. population, engaged with a bank's chatbot in 2022.
Can a Washington bank record calls its AI voice agent handles?
Washington requires the consent of all participants to record a private phone call, and treats consent as obtained when one party announces that the call is about to be recorded and the announcement is itself recorded. Put the announcement at the start of the greeting.
Sources
- Glia’s banking page · glia.com
- CFPB’s 2023 chatbot spotlight · consumerfinance.gov
- FinCEN's November 2024 alert on deepfake fraud · fincen.gov
- Federal Communications Commission ruled in February 2024 · docs.fcc.gov
- RCW 9.73.030 · app.leg.wa.gov
- chapter 19.375 RCW · app.leg.wa.gov
- chapter 19.373 RCW · app.leg.wa.gov
- 720 ILCS 5/14-2 · ilga.gov
- Biometric Information Privacy Act · ilga.gov
Revision note · October 6, 2026: Headline simplified; the article body is unchanged.
How we research and review these guides
Put the ideas to work in your business.
We provide AI consulting and implementation for finance operations teams. Bring us the process that is slowing your team down and the systems involved. We can assess the problem with you and discuss a practical implementation.
Discuss your project →Still exploring? Explore the Workflow Opportunity Workbook →