Demonstration Study • Customer & Operational Intelligence • Financial Services
Connect reported customer issues with response records and operational handoffs. Explore which problems deserve investigation, what the numbers can establish and what evidence management still needs.
Context
What should a service leader investigate after seeing a high response-timeliness rate?
This study follows checking-and-savings complaints received by the US Consumer Financial Protection Bureau in the first quarter of 2025. It connects the issue reported by the consumer with the submission channel, forwarding interval and recorded company response.
The management view separates recurring issue volume, non-timely response flags and the response mix. It creates an investigation agenda; case histories and customer confirmation are needed to establish why a problem happened or whether it was resolved.
Demonstration note: This is an independent study of public, historical US records. It is not a client engagement, a representative customer survey or a benchmark for Nigerian service performance.
Findings
28,794 of 28,889 records carry a Yes response-timeliness flag. Yet 89.1% of all response categories are “Closed with explanation.” These fields answer different questions; neither establishes customer satisfaction.
Investigate: pair the response record with confirmed resolution, repeat contacts and customer feedback.
Account management is the largest issue group: 13,839 complaints, or 47.9% of the cohort. Account closure contributes 8.3% of complaints but 17 of the 95 non-timely flags—17.9% of those exceptions.
Investigate: review both high-volume friction and smaller groups that carry a disproportionate share of exceptions.
The median receipt-to-forwarding interval is 14.3 minutes. However, 1,878 records have an interval above 24 hours. Referral-channel records have a median of 21.5 hours, compared with 13.4 minutes for web submissions.
Investigate: examine routing dependencies and case mix. These intervals are not company response or complaint-resolution times.
Interactive evidence desk
Filter the same complaint cohort across month, account type, intake channel and issue. All measures and tables recalculate together. The full-quarter totals remain documented in the validation download.
Q1 2025 · All months · All account types · All channels · All issues
Loading the evidence…
Published complaints in the selected receipt cohort
28,889 records with a known Yes/No flag
Source Timely response? = No
3,135 records out of 28,889
28,889 records with valid forwarding dates
Illustrative review boundary, not a regulator’s service target
The largest issue group is account management. Compare complaint burden with response exceptions before setting an investigation priority.
Compare the share of complaints with the share of non-timely flags. Select Inspect to focus the entire evidence desk on that issue.
| Reported issue | Complaints | Volume share | Non-timely flags | Exception share | Timely rate | Explore |
|---|
Exception share uses non-timely flags within the selected scope as its denominator. It is unavailable when there are no such flags. Counts identify investigation workload; they do not establish the incidence of harm among all customers.
These are complaint counts in a frozen published-record cohort. Customer-base size, campaigns and changes in reporting behaviour are not controlled.
| Month | Complaints | Timely rate | Non-timely flags |
|---|
Response categories describe the record, not a consumer’s satisfaction rating. Monetary and non-monetary relief are combined only in the headline relief measure.
“Untimely response” as a response category and “No” as the timeliness flag are separate fields. They are not interchangeable counts.
Elapsed time runs from CFPB receipt to forwarding to the company. It stops before the company’s response and is not a measure of the full service journey. Differences may reflect channel and case mix.
| Submission channel | Complaints | Median forwarding interval | Above 24 hours | Recorded timely rate |
|---|
Top eight sub-issue categories in the selected scope. Source categories describe the consumer’s reported problem.
| Reported sub-issue | Complaints | Non-timely flags |
|---|
Select a scope to identify the evidence an investigation should collect.
A live implementation would attach a case sample, responsible process owner, agreed action and review date. This public cohort does not contain those internal records.
Method
Checking-and-savings complaints received January–March 2025, from the official CFPB open-data API.
Check complaint IDs, dates, product scope, status values and record reconciliation before comparison.
Link reported issues, submission channels, elapsed forwarding intervals and recorded company responses.
Prioritise case review and define the additional evidence required to establish an operational cause.
The API export returned 29,091 records, including 202 received on 1 April. A strict receipt-date rule removes those records and retains 28,889. Complaint IDs are unique. All retained records have a known response-timeliness flag and valid non-negative forwarding intervals. The browser model omits company names, geography, demographic tags, identifiers and free text.
Evidence discipline
Source: Consumer Financial Protection Bureau, Consumer Complaint Database. Frozen retrieval: 9 October 2026. Definitions: official field reference.
Complaint cohort.
These records are not a statistical sample of all customers or all service experiences.
Reported issue.
A category is the consumer’s selection, not a verified root cause.
Timeliness.
The source flag does not provide an exact company response or resolution duration.
Response outcome.
Explanation and relief categories do not establish customer satisfaction or successful resolution.
Population denominator.
Customer-base size and exposure are unavailable, so counts are not customer-level complaint rates.
Operational cause.
Case histories, repeat contacts and internal process events are needed to explain differences.
Historical context.
This is a US complaint cohort, not a current Nigerian market or company benchmark.
Snapshot changes.
Later API downloads can change as public records are updated. The published model and source hash preserve this study’s scope.
From finding to action
Sample both recurring themes and non-timely cases. Trace the actual journey and compare the reported issue with the recorded handling.
Add verified resolution, repeat-contact, reopened-case and customer-feedback measures to the internal reporting design.
Assign an owner, define a change and agree a review date. Compare outcomes with a clear baseline and account for changes in volume and case mix.
Need to understand customer friction?
ONE Light Analytics can connect customer evidence, service records and process measures to a clear investigation and improvement agenda.
