- Industry
- Banking
- Department
- Customer
- Team
- Support Operations
- Kind
- Decision-maker
- Approver
- Head of Retail Banking
- Code
- CUS-07
It decides who should own a complex case (a complaint near its deadline, a disputed mortgage payment, a bereavement, an SME client with a payments failure, a suspected account takeover) by matching issue type, severity, customer segment and history to the escalation matrix and to who is on rota with capacity. It reassigns the case with a hand-over note and escalates possible regulatory breaches to Compliance.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the CRM: the case history, the customer's segment and relationship manager, and the rota and open load of each team..
- 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.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Head of Retail Banking with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the CRM: it reassigns the case with the hand-over note and notifications. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The escalation matrix: specialist teams (complaints, bereavement, financial support, fraud, disputes, business banking service, wealth service), complaint deadlines, the referral path for possible regulatory breaches, on-call rotas and relationship-manager ownership for corporate and wealth clients.
Reads from
the CRM: the case history, the customer's segment and relationship manager, and the rota and open load of each team.
Acts in
the CRM: it reassigns the case with the hand-over note and notifications.
Hands back
An object with case_id, owner, team, tier, reason, handover_note, notify (a list, such as relationship manager or Compliance) and due_by.
Asks a person when
The case is a possible regulatory breach, an ombudsman referral or media threat, a relationship worth 1000000 USD or more, a suspected account takeover, or the routing overrides the owner the request asked for.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Escalate a complaint this close to its deadline (days) | 10 | A complaint within this many days of its final-response deadline goes to the complaints team lead. |
| Reopens that trigger escalation | 2 | A case reopened this often goes up a tier. |
| High-value relationship (USD) | 1000000 | At or above this the relationship manager is told. |
| Signals that go to a specialist team | bereavement, financial difficulty, fraud, power of attorney, vulnerable customer | Comma-separated signals. |
| Most open escalations per owner | 15 | Owners above this get no more. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A complaint within 10 days of its deadline goes to the complaints team lead.
- A case with any of bereavement, financial difficulty, fraud, power of attorney, vulnerable customer goes to that specialist team, never a general queue.
- A possible regulatory breach is referred to Compliance as well as routed.
- A relationship at or above 1000000 USD, and any corporate or wealth client, is copied to its relationship manager.
- Escalate a case reopened 2 times; never give an owner more than 15 open escalations.
See the Escalation Routing Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.