What’s inside: routing · assistants
The question this file answersHow long does a complaint that is really a conduct issue sit in the general inbox before anyone senior sees it?
Fits: insurers and brokers where claims and policy changes still arrive by email.
Typical pattern, not a measured desk; the finance playbook publishes no complaint volume. Every complaint, mis-sent statement or possible conduct breach, enters the same inbox; acknowledgements are typed one by one, behind whatever is on top. It hurts when the acknowledgement deadline runs while the file sits unopened.
By 09:30 every overnight complaint has an acknowledgement ready and a proposed route, and the complaints lead is reading the files flagged conduct rather than the whole inbox. You can see per case when it arrived, when it was acknowledged and who owns it.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
the same triage build as claims handling — no published figure for complaint admin
Before: acknowledgements wait behind the file that might be conduct. After: acknowledgements are drafted and logged on arrival; conduct goes to a named owner first. No percentage — the claims figure lives on the parent file.
The Accenture (2023) claims figure — 40–50% shorter cycles, standard claims only — measures claims; a complaint is not a claim, so we no longer show that figure here — it stays on the claims file. Not a conduct outcome.
Your CRM and complaints register stay — Salesforce, Dynamics or the one you run — and Outlook stays the front door. This is the same sorting-and-routing build as our claims triage, pointed at complaints:
Nothing is resolved automatically.
Conduct. Vulnerable customers. Remediation. The letter that is not a template.
Not a conduct outcome.
Misclassifying a conduct complaint as a simple one is the failure that matters — so the classifier is tuned to over-refer, and the review list will contain simple cases for the first weeks. If your complaints register is a spreadsheet with no interface, routing and logging go through export and import, which needs your IT.
The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →
Scoped in the audit — the playbook has no estimate for this exact desk.
That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.
Not a named Aperanda client. Process file · Finance.
Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.