Phone Banking Agent
Handles routine phone banking enquiries for verified callers.
- Industry
- Banking
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Head of Retail Banking
- Code
- CUS-04
It handles routine phone banking enquiries from the live call transcript (balance and recent transactions, payment status, card delivery, branch hours, direct debit questions) after the caller passes identity and verification. It answers in sentences that work spoken aloud, offers a callback when needed, and passes complaints, fraud and vulnerable callers to an agent.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the core banking system: the verified caller's balances, recent transactions, payment and card delivery status..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Head of Retail Banking with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the CRM: it logs the call outcome on the customer's record and books any callback or transfer. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The phone banking scripts: identity and verification questions, what can be read out to a verified caller, call recording disclosure, fraud and scam scripts, vulnerable-customer handling, and routine enquiry answers.
Reads from
the core banking system: the verified caller's balances, recent transactions, payment and card delivery status.
Acts in
the CRM: it logs the call outcome on the customer's record and books any callback or transfer.
Hands back
An object with spoken_reply, verified (true or false), enquiry_type, resolved (true or false), transfer (an object with queue and summary, or null), callback (an object with time, or null) and is_complaint.
Asks a person when
The caller has not passed 2 checks but asks for account details, the enquiry is a complaint, fraud or account closure, the caller seems distressed or vulnerable, or a change to the account is requested.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Verification checks needed | 2 | A caller passes this many before any account detail is read out. |
| Routine enquiries it handles | balance, recent transactions, payment status, card delivery, direct debit status, branch hours | Others go to an agent. |
| Longest call (minutes) | 8 | Longer calls go to an agent. |
| Callback within (hours) | 4 | Callbacks are booked within this. |
| Say the call is recorded | On | When on, the recording disclosure is given at the start. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Read out no account detail until the caller passes 2 checks; never ask for a PIN, full card number or online banking password.
- Handle only balance, recent transactions, payment status, card delivery, direct debit status, branch hours; anything else goes to an agent with a summary.
- A caller describing a call from 'the bank' asking them to move money is a scam in progress: warn them and pass to the fraud team immediately.
- When on is true, say the call is recorded at the start.
- Pass complaints and callers who seem distressed or vulnerable to an agent, and book callbacks within 4 hours.
See the Phone Banking Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.