- contact@insightserviceai.com
Each one on the demo firm’s data, Fernhollow Bank & Insurance, a fictional firm with invented customers, showing what the agents prepare and what people decide.
Each is a real case on the demo firm’s data, with the screens and a step-by-step account of who does what.
A £10 returned payment fee taken twice on 8 November. The duplicate is found in the fee history and the refund worked out with interest.
A routine request for statements, and one sentence about a call-back that never came.
A widow keeps receiving fee letters addressed to her late husband after sending the death certificate twice.
A query from a customer behind on everything, three overdraft fees, and a request sent through a secure link.
Customers in credit complain about a £6 overdraft fee taken on 3 October. All four fees come from one run.
A downgrade in March, the old £32 fee every month since, and a bounced direct debit.
A home insurance claim complaint past its final-response deadline, and a customer complaining for the fourth time this year.
The same controls and the same record, whatever the customer wrote.
| What arrives | What it becomes | What the agents prepare | What a person decides |
|---|---|---|---|
| A dissatisfied contact | A complaint case on the clock | Classification, vulnerability, research, root causes, remediation, the acknowledgement and final letter | Whether it is a complaint, the outcome, the redress, what to send, the close |
| A routine request with one dissatisfied sentence | A complaint, marked hidden | The quote and a proposal to treat it as a complaint | Confirm, or correct it with a reason |
| A query | A query case, no clock | Research, the response, vulnerability support | The reply, and the close |
| Many complaints with one cause | A root-cause cluster | The cluster, its reach and a systemic flag | Who owns the fix |
Roles map to the identity service: service agents, team leads and administrators.
Works the inbox and the case queue, reviews what the agents prepared, confirms or corrects classifications, sends replies and requests, records the outcome and closes what needs no sign-off.
Approves remediation above the threshold that someone else proposed, signs off closes referred for a breach or a repeat complainant, and records QA results.
Publishes the case controls in Rules Studio and sets how much the agents may do, within the L2 ceiling.
Reads the clock across the book, the root causes and systemic flags, QA results and the agents’ agreement rates.