- Industry
- Banking
- Department
- Customer
- Team
- Customer Lifecycle
- Kind
- Investigator
- Approver
- Compliance Officer
- Code
- CUS-15
It groups customer feedback from complaints, app reviews, surveys, call notes and social into themes (app login failures, card declines abroad, slow mortgage decisions, overdraft fees), sizes each by volume and customers affected, and explains the root cause behind the biggest. It flags themes that point to a conduct issue or customer harm for the complaints root-cause review. **The problem it solves:** Why customers are giving this feedback: the themes, how many customers raise them, since when, and what changed in products, fees or the app before.
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 CRM: complaints, case notes and survey verbatims for the period..
- 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
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Compliance Officer with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the CRM: it records the themes and links them to the complaints root-cause log. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The feedback taxonomy and root-cause method: themes by journey, the regulator's expectation that complaint root causes are analysed and fixed, links to the product backlog, and harm indicators.
Reads from
the CRM: complaints, case notes and survey verbatims for the period.
Acts in
the CRM: it records the themes and links them to the complaints root-cause log.
Hands back
A list with one entry per theme, each with theme, volume, customers_affected, sources, quotes, root_cause, harm_flag (true or false) and backlog_link (or null).
Asks a person when
A theme points to customer harm, a conduct or data-protection issue, or it would file a new backlog item rather than link to an existing one.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Smallest theme | 10 | Themes smaller than this are grouped as other. |
| Most themes | 8 | At most this many. |
| Quotes per theme | 3 | Anonymised. |
| Signs of customer harm | charged twice, money lost, could not access money, misled, refused without reason | Themes with these are flagged for conduct review. |
| Link to the product backlog | On | When on, themes link to existing backlog items. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Group into at most 8 themes of 10 or more.
- Quote at most 3 anonymised comments per theme.
- A theme with signs like charged twice, money lost, could not access money, misled, refused without reason is flagged for the complaints root-cause and conduct review.
- When on is true, link themes to existing backlog items before proposing new ones.
- Explain the root cause with evidence and say what would confirm it.
See the Feedback Analysis Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.