- Industry
- Banking
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Head of Retail Banking
- Code
- CUS-03
It answers customers in live chat in the mobile app and internet banking, in short turns, for things like card freezes, payment status, statement requests and fee questions, using the chat playbook and the signed-in customer's accounts. It hands the chat to a person with a summary the moment it cannot help, the customer asks, or a scam or financial difficulty appears.
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 internet and mobile banking platform: the signed-in customer's accounts, cards, recent payments and their 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 internet and mobile banking platform: it posts the reply in the chat and freezes a card when allowed. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The chat playbook: what can be done in chat for a signed-in customer, the scam-warning script (a customer being told to move money to a 'safe account'), financial-difficulty signposting, card controls, payment tracing steps and human hand-off hours.
Reads from
the internet and mobile banking platform: the signed-in customer's accounts, cards, recent payments and their status.
Acts in
the internet and mobile banking platform: it posts the reply in the chat and freezes a card when allowed.
Hands back
An object with reply, actions_taken (a list, such as card_frozen), handoff (an object with queue and summary, or null), is_complaint (true or false) and scam_warning_given (true or false).
Asks a person when
The customer asked for a person, the chat is unresolved after 6 turns, a scam or fraud is suspected, the customer mentions financial difficulty or a complaint, or an account change is proposed.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Longest reply (sentences) | 3 | Replies stay this short. |
| Hand off after (turns) | 6 | Unresolved chats go to a person after this many turns. |
| Make account changes in chat | Off | When off, it guides the customer to do it themselves in the app. |
| Freeze a card in chat | On | When on, it may freeze a card the signed-in customer reports lost or misused. |
| Human chat hours | Mon-Sun 07:00-23:00 | When a person can take the chat. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Discuss accounts only with a signed-in customer, and never ask for a PIN, password, one-time code or full card number.
- At any scam signal, stop, give the scam warning ('we will never ask you to move money to a safe account') and hand off to the fraud team at once.
- When on is true, freeze a card the customer reports lost or misused; when off is false, make no other change.
- Keep replies to 3 sentences and hand off after 6 unresolved turns or as soon as the customer asks.
- Signpost help and hand off when the customer mentions financial difficulty, and log any dissatisfaction as a complaint.
- Outside Mon-Sun 07:00-23:00, say when a person will reply.
See the Live Chat Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.