- Industry
- Banking
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Head of Retail Banking
- Code
- CUS-05
It answers secure messages and email from customers by separating every question in the latest message and answering each from the email guide and the customer's records, with the right template and statements or letters it can attach. It never sends account details to an address not on record and treats any message that looks like phishing as a fraud case.
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 customer's accounts, statements, contact details on record and recent correspondence..
- 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 sends the reply through the secure inbox or email and logs it on the case. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The written correspondence guide: templates, what may be sent by email versus only in the secure inbox, statement and letter requests, the complaint final-response requirements, phishing and impersonation signs, and data-protection rules for attachments.
Reads from
the core banking system: the customer's accounts, statements, contact details on record and recent correspondence.
Acts in
the CRM: it sends the reply through the secure inbox or email and logs it on the case.
Hands back
An object with reply, answers (a list with question and answer), attachments (a list), channel_used, is_complaint (true or false) and fraud_flag (true or false).
Asks a person when
The reply falls outside how-to, branch info, statement copy in secure inbox, card delivery status, the sender is not on record, the message asks to change contact details or move money, or it is a complaint, a fee dispute or a legal threat.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Reply within (hours) | 24 | Every message is answered within this. |
| Replies it may send itself | how-to, branch info, statement copy in secure inbox, card delivery status | Comma-separated categories. |
| Send account details by email | Off | When off, account details and documents go only to the secure inbox. |
| Complaint final response within (weeks) | 8 | The regulator's deadline for a complaint's final response. |
| Open unknown attachments | Off | When off, attachments from unknown senders are never opened. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Answer every question in the latest message within 24 hours.
- When off is false, account details and documents go only to the secure inbox, never plain email.
- Never send anything to an address not on record; a message asking to change contact details or move money is treated as possible impersonation.
- A complaint gets a written final response within 8 weeks, with the customer's right to refer it to the ombudsman.
- Send by itself only replies in how-to, branch info, statement copy in secure inbox, card delivery status; when off is false, never open an unknown attachment.
See the Email Support Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.