Use cases

Real complaint situations, worked end to end

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.

Worked end to end

Seven situations every complaints team meets

Each is a real case on the demo firm’s data, with the screens and a step-by-step account of who does what.

Charges · current account

Charged twice for the same fee

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.

  • Duplicate found in the firm’s records
  • £20.06 worked out to the penny
  • A sibling case followed through to an upheld close
Read the worked case
Identification · email

The complaint inside a statement request

A routine request for statements, and one sentence about a call-back that never came.

  • The sentence quoted
  • The clock runs from receipt
  • A person confirms or corrects it
Read the worked case
Vulnerability · bereavement

Letters to a husband who has died

A widow keeps receiving fee letters addressed to her late husband after sending the death certificate twice.

  • Bereavement quoted and flagged
  • Adaptation drafted from the knowledge base
  • Can’t close until it’s recorded
Read the worked case
Vulnerability · financial difficulty

“I lost my job in September”

A query from a customer behind on everything, three overdraft fees, and a request sent through a secure link.

  • Handled as a vulnerable query
  • Remediation and reply prepared
  • A no-login request, held until sent
Read the worked case
Root causes · systemic

One faulty fee run, 104 customers

Customers in credit complain about a £6 overdraft fee taken on 3 October. All four fees come from one run.

  • Cases linked by the fee run
  • The run’s reach: 104 customers, £624.00
  • Flagged possibly systemic, with an owner
Read the worked case
Remediation · four eyes

Eight months of a fee she shouldn’t have paid

A downgrade in March, the old £32 fee every month since, and a bounced direct debit.

  • Nine fees found
  • £273.49 with interest
  • A team lead approves above £250
Read the worked case
The clock · sign-off

A claim complaint past its deadline

A home insurance claim complaint past its final-response deadline, and a customer complaining for the fourth time this year.

  • Breach shown on the clock
  • Close referred to a lead
  • Four eyes enforced
Read the worked case
Four ways work arrives

From the contact to the case, the cluster and the decision

The same controls and the same record, whatever the customer wrote.

What arrivesWhat it becomesWhat the agents prepareWhat a person decides
A dissatisfied contactA complaint case on the clockClassification, vulnerability, research, root causes, remediation, the acknowledgement and final letterWhether it is a complaint, the outcome, the redress, what to send, the close
A routine request with one dissatisfied sentenceA complaint, marked hiddenThe quote and a proposal to treat it as a complaintConfirm, or correct it with a reason
A queryA query case, no clockResearch, the response, vulnerability supportThe reply, and the close
Many complaints with one causeA root-cause clusterThe cluster, its reach and a systemic flagWho owns the fix
Who does what

Agents prepare. These people decide.

Roles map to the identity service: service agents, team leads and administrators.

Service agent

Prepares, sends and submits

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.

Team lead

Approves and signs 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.

Administrator

Sets the controls

Publishes the case controls in Rules Studio and sets how much the agents may do, within the L2 ceiling.

Head of complaints

Owns the outcomes

Reads the clock across the book, the root causes and systemic flags, QA results and the agents’ agreement rates.

Bring your own scenarios

Tell us the complaints your team finds hardest. We’ll show how InsightService prepares them.

Request a demo