Use CFPB Complaint Data to Ask Better Lender Questions
Turn a complaint label into a specific service-process question, then assess whether the answer supplies a usable route and written evidence.
Estimated reading time: 8 minutes
Use CFPB complaint data to prepare a specific question about a lender or servicer, then ask for a current written explanation of its process. A complaint count or response label doesn’t establish that a lender is better, worse or certain to resolve your own problem.
A useful question for a mortgage servicer is concrete: if a payment looks incorrectly posted, who can explain the entry, what record will they supply, and where is the process written down? Complaint research can help you prepare that conversation. Decide what you need to learn before you search.
CFPB complaint data: start with the current database
As rechecked on October 25, 2026, CFPB’s September release removed complaint narratives and database visualizations. Older tutorials that tell you to open a consumer’s story or use those charts no longer describe the current database.
The database isn’t representative of all consumer experiences. It excludes complaints referred to other regulators; publication rules and delays also limit coverage. Counts lack the customer-exposure denominators needed for fair lender comparisons. No matching results don’t prove that no problems exist.
Don’t reconstruct a missing story from a short label. Even before removal, narratives depended on consumer consent and did not cover every complaint.
Keep CFPB complaint data fields separate
Read each field for the limited question it answers. Don’t combine different labels into a story that the data doesn’t supply.
| Field | What it describes | What it does not prove |
|---|---|---|
| Date received | When CFPB received the complaint. | When the underlying problem occurred. |
| Date sent to company | A separate step in complaint processing. | The date a remedy was completed. |
| Issue and sub-issue | Consumer-selected complaint categories. | An adjudicated finding or a full account of events. |
| Company response | The recorded response category. | Consumer satisfaction or independently verified resolution. |
| Public response and timeliness | Separate response-related fields; the public response is optional. | That an empty public field means no response, or that timeliness means the problem was fixed. |
Fictional exercise: imagine payment-related labels, a response marked “Closed with explanation,” timeliness marked “Yes,” and an empty public-response field. This invented combination describes no actual complaint or company. These labels don’t establish satisfaction or verified resolution; a blank optional field doesn’t mean the company gave no response.
CFPB complaint data: replace a verdict with a question
The tempting conclusion is: “They fixed it quickly.” The useful next step is a question you can actually put to the servicer:
“What is your current process for investigating a payment-posting discrepancy? Which team handles it, how do I retain a case reference, and where can I read the procedure?”
Now test the answer. The following replies are invented for practice and aren’t any lender’s policy or a promise of a remedy.
- “We take customer service seriously.” This leaves the practical question unanswered. Ask for the process, responsible team and written source.
- “Contact support.” Ask which verified contact route applies to this issue and what acknowledgment you should retain.
- “Here is the procedure and the team that handles it.” Check whether the document is current and covers your product. Identify any question it still leaves open.
If the answer misses the point, make the follow-up smaller: “Which document explains how I can request the transaction history behind this entry?” Keep the unresolved question visible instead of treating a reassuring phrase as the end of the discussion.
CFPB complaint data: test a comparison with invented denominators
Suppose a classroom file contains 200 complaint records for Company A and 80 for Company B. These are invented companies and counts, not results from the linked API sample. The raw counts alone can’t show the share of customers experiencing a problem.
For a purely mathematical illustration, supply matching exposure counts of 100,000 accounts for A and 10,000 for B over the same defined period and product. Dividing gives 20 complaint records per 10,000 accounts for A and 80 for B. The company with fewer records has the larger hypothetical ratio.
That reversal shows why a denominator matters. It doesn’t create a valid lender-quality measure. A complaint record isn’t necessarily a distinct customer or a verified instance of wrongdoing, and the fictional account counts don’t fix the database’s coverage and selection limits.
In real research, an unrelated company’s total customers, another year’s mortgage originations or a different product’s account count wouldn’t be a matched denominator. Label an unavailable exposure measure unavailable. Don’t insert a convenient number to make a rate appear comparable.
Likewise, two extracts with the same raw total may have different products, receipt periods or company definitions. Match the question and filters before comparing results. Even then, keep the limits attached to the extract rather than turning the result into a verdict.
CFPB complaint data: distinguish a repeated record from a repeated experience
Imagine an export assembled from two overlapping date windows. The first supplies identifiers 1 through 20, and the second identifiers 16 through 35. The files contain 40 rows in total, but only 35 distinct identifiers because five appear in both.
Removing those repeated identifiers repairs this particular export overlap. It doesn’t prove that the remaining 35 records represent 35 different borrowers, 35 separate accounts or 35 independently verified events. The identifier answers a record-count question, not every identity question.
Keep the original files, retrieval dates and exact filters alongside the cleaned working copy. Record why rows were removed and retain the identifier comparison. A later researcher should be able to reproduce the change from 40 rows to 35 records without trusting an unexplained total.
If the database changes after retrieval, label the saved extract by its capture date. A later count can differ because the underlying publication changed, because filters differ or because an earlier procedure was incomplete. Investigate those possibilities rather than assuming the company’s service improved or deteriorated.
CFPB complaint data: turn the research into a limited follow-up
For the payment-posting question above, a useful follow-up might identify one procedure that remains unclear: “Does this written process explain how to obtain the dated transaction history, or is there a separate request route?” This asks for evidence the servicer can actually supply.
If the answer names a team but no document, record that partial answer. If a document covers another product, keep the mismatch visible. A confident reply isn’t a substitute for a relevant explanation.
Don’t include another consumer’s identifiers or imply that a complaint label proves the same event happened to you. Describe your own issue through the verified private channel, using only the records needed for that request.
The finished research note should connect a dated observation, a specific question and the current answer. It should also identify what the data couldn’t establish. This is useful preparation even when no defensible comparison between companies can be calculated.
A five-line preparation note
- Product or service and the date of your research
- The label you observed, without inventing an event behind it
- One question for the verified lender or servicer
- The written source supplied, including its date
- The unanswered point and who you’ll ask next
Keep this note privately. Don’t send account records or sensitive identifiers to this website. This is a conversation-preparation aid, not an official complaint form, legal advice or a change to your payment obligations or formal notice deadlines.
Optional: what the dated API example checks
Open the sample, date-boundary and export notes
An independent repeat captured October 25, 2026 returned 29 published FHA-mortgage complaint records with June 1, 2026 CFPB-receipt timestamps in UTC. The response total was 29, all 29 identifiers were distinct, and every returned product, sub-product and date was checked. This establishes completeness within that response, not all complaints or unique borrowers.
The API schema describes the maximum receipt date as exclusive. A separate October 25 query with June 1 as the minimum and June 2 as the maximum returned 60 rows: 29 dated June 1 and 31 dated June 2. That reproduces a mismatch between the documentation and this observed response. It doesn’t establish a general boundary rule for every query or endpoint.
The exact same-day query remains linked below. Publication and backfill can change later results, so compare the returned timestamps, row count, distinct identifiers and reported total whenever you repeat it. A filter label alone isn’t a substitute for checking the returned rows.
The earlier version of this guide described an October 20 saved response, a locally derived CSV and a blocked official-export attempt. Those historical artifacts aren’t independently verified by the October 25 repeat. No official CSV export is verified here; a file derived from API fields should be labeled as a derived file.
The API method is optional for the practical exercise above. You can prepare a careful question without turning a small data extract into a lender score or treating an unverified export as evidence.
Sources and method
- CFPB database coverage
- CFPB data-use guidance
- CFPB field reference
- CFPB release notes
- CFPB API schema
- Exact same-day sample query
The same care with data definitions matters when reading HMDA mortgage-rate comparisons or interpreting SLOOS lending-standard results.


