Support Services OneSSONE Platform
Guide · 6 min read

AI voice agents for banks: what to automate and what to hand to a person

Bank callers want quick answers about cards, balances and loans. They also expect their money and their data to be safe. The way to get both is to decide the boundary first.

The calls that suit an assistant

  • Questions that have the same answer every time, such as opening hours, branch details, card replacement steps and loan application stages.
  • Looking up status that the caller is already allowed to hear.
  • Booking, moving and cancelling appointments with an adviser.
  • Collecting the details a person will need, so the person starts with the context.

The calls that must reach a person

  • Anything that moves money, or changes who can move it.
  • A report of fraud, or a caller who sounds frightened or pressured.
  • A complaint, a bereavement or a vulnerable customer.
  • Any request the assistant is unsure about. It should say so and hand over.

Guardrails to check before you go live

RiskWhat a good setup does
Card numbers, PINs and security codes spoken aloudNever ask for them, never repeat them, and keep them out of the transcript
Fraud reportsHand over to a fraud desk first in line, with the context of the call
Bulk money movementRefuse, then hand over to a person
Prompt injection (a caller trying to rewrite the assistant's rules)Detect it and refuse, and review those calls afterwards
Wrong or invented answersAnswer from your own documents, and send unsure cases to a person

Hand-over that works

A hand-over fails if the person has to start again. The person should see what the caller asked and what the assistant said. Routes should be set by what the caller mentions, for example fraud to the fraud desk, a card to card services, and a loan to loan officers.

What to measure

  • How many calls were fully resolved by the assistant, and how many were handed over.
  • How quickly calls are answered and how many callers hang up while waiting.
  • How often a hand-over was avoidable. This tells you where to improve the assistant.

A note on compliance

No assistant, and no starter configuration, makes a bank compliant by itself. Your compliance team still reviews the wording, the rules and the records, and signs them off. Use a starter pack to begin with sensible rules, not to skip the review.

In the platform

How the SSONE banking pack starts you off

The banking starter pack loads knowledge topics for lost and stolen cards, fraud reporting, balance and statement questions and loan enquiries, for you to replace with your own documents. It ships guardrails against spoken card numbers, a card security code before the keyword, bulk money movement, PIN disclosure and prompt injection, and example routes to a fraud desk, card services and loan officers. Callers can book appointments that show in your calendar, and a Banking Operations Health board shows calls resolved by the assistant, calls escalated, answer time and abandonment. The pack is configured around PCI-DSS and KYC settings, which does not make an organisation compliant by itself.

Questions people ask

Can an AI voice agent take a card payment?
The SSONE banking starter pack hands anything that moves money to a person. If you want automated payments, use a payment flow that is built and assessed for that purpose, rather than the assistant's transcript.
How do we stop the assistant making things up?
Give it your own documents to answer from, add rules for what it must never say, and send any question it is unsure about to a person. Review a sample of calls regularly.
What should we test before launch?
Bring recordings of real caller questions and check what the assistant resolves and what it hands over. Include difficult calls: fraud, anger, and callers who try to trick it.
Keep reading

More guides

All guides

See it on your own traffic

Book a short walkthrough and bring a real scenario. We will show what the platform does with it.

Book a demo