Voice AI for balance and account status in financial services
Balance and account status is the highest-containment voice AI use case in retail banking — and the one most often misreported. The work is in tiered authentication, demographic-fair ASR, and clean next-best-action; the read itself is trivial.
70–85% gross on in-scope status intents; 60–75% net of 7-day re-contact
Integration touchpoints
- Core banking read APIs (balance, holds, available vs ledger, last-N transactions) with audit logging on every disclosure
- Card-management system (status, last decline reason, replacement state) for adjacent enquiries within the same call
- Identity service for tiered authentication assurance and step-up on full account values
- CRM case append with reason code so agent-side reporting reflects AI-handled volume
Regulatory hooks
- GDPR / UK GDPR — lawful basis for disclosure and recording, DPIA on the authentication tiers
- FCA Consumer Duty (UK) — vulnerable-customer signals routed to a human before disclosure
- PSD2 strong customer authentication — applies when the enquiry escalates to a payment or change
- PCI DSS 4.0 — relevant the moment the call pivots from status to payment
What good looks like
An AI that authenticates the caller to the assurance level appropriate for the value disclosed, reads the figure with confirmation, offers the next logical action within policy (pay, transfer, dispute), and writes a reason-coded record back to the CRM. Step-up rate is a published operational metric, not a hidden one.
Watch-outs
- Quoting 80%+ aggregate containment on the strength of balance calls alone — the call mix is the metric, not the headline.
- Disclosing full account values at a low assurance tier because the customer 'sounds right'. Voice biometrics is a factor, not the factor.
- Skipping vulnerability detection on the disclosure step. A confused or distressed caller on a balance enquiry is a Consumer Duty signal, not just a containment opportunity.
- Treating ASR errors on sort codes and account numbers as a model problem. The fix is confirmation design and DTMF fallback.
Frequently asked
What does Consumer Duty change for a balance enquiry?
It changes the definition of a successful call. A 'contained' balance enquiry that disclosed a value to a confused caller without offering a human is not a success under Consumer Duty — it is a foreseeable harm. The AI's vulnerability detection has to be measurable and the human routing path has to be visible.
How should authentication tier with the value disclosed?
Masked balance and recent transaction count at low assurance; full balance and full transaction history at medium with a passive factor; any change or full PAN-related disclosure at high with an active factor. The policy is owned by fraud and compliance, not by the AI vendor.