The CFPB Consumer Response Portal With AI Complaint Handling: The 15-Day and 60-Day Response Windows, the Portal Tag Discipline, and the Public-Database Read the Bank Cannot Ignore

The Portal That Turned Complaint Handling Into a Supervisory Discipline

The CFPB Consumer Response function was built into the Bureau at its founding under 12 USC 5493(b)(3) and has grown from a single-product portal in 2011 to a full-product complaint system that logged more than 1.6 million complaints in 2023, a volume the Bureau's 2024 Consumer Response Annual Report walks through product by product. Every complaint routed to a company through the portal is a supervised event: the company is expected to respond, the response is timed, the response is categorized, and the whole record becomes a data point the Bureau's supervision and enforcement teams read against the company's overall pattern.

The portal is not optional and it is not a customer-service tool. A bank or non-bank consumer-financial-services provider that receives a complaint through the portal is subject to the Bureau's operational rules on how to respond, when to respond, what to tag the complaint with, and how to handle the consumer's dispute of the response. The Bureau's Company Portal Manual is the canonical operational reference, and the manual's specifics are the specifics the company's workflow has to execute against.

The pattern that shows up in the CFPB's Supervisory Highlights year after year is that companies miss the 15-day acknowledgment, send a substantive response that is boilerplate rather than specific to the consumer's issue, mis-tag the complaint's issue or sub-issue field, and fail to close the root-cause loop when the same complaint pattern repeats across the portfolio. The examination reads the portal record, reads the internal complaint file, and asks whether the operations behind the response are the operations of a company that takes the complaint program seriously.

We build the AI agent that participates in the intake, routing, response drafting, and root-cause analysis for the Consumer Response portal at bank and non-bank providers. What the agent does, where the human reviewer takes over, and how the audit file supports the response are the specifics below.

The 15-Day Acknowledgment and the Real Consumer Signal It Sends

The company's first obligation on a portal complaint is the 15-calendar-day acknowledgment. The Bureau's portal timing rules require the company to provide either an interim response indicating the complaint is under review or a final substantive response within 15 days. The 15-day interim response is the standard operational move for any complaint whose substantive resolution is going to take longer, and the substantive response has to follow within 60 days.

The acknowledgment sounds trivial and produces findings anyway. A company that lets the 15-day clock run past on a portion of its portal volume is a company whose complaint response rate the Bureau publishes on the company-level data page. The response-rate metric is public, is comparable across companies in the same product category, and is the kind of metric an examiner opens a supervisory conversation with when the rate is materially below peers.

The consumer's read of the 15-day acknowledgment is a different signal. A consumer who filed a complaint about an unauthorized transaction, a mortgage-servicing error, or a credit-report inaccuracy is a consumer whose specific situation has real time pressure. The acknowledgment that arrives on day 3 with a specific reference to the situation and a specific timeline for the substantive response is an acknowledgment that reads as taking the complaint seriously. The acknowledgment that arrives on day 14 with generic language is an acknowledgment that reads as procedural compliance, and the consumer's likelihood of disputing the eventual response is materially higher.

The agent's acknowledgment workflow reads the complaint content the consumer submitted (the complaint narrative, the products and issues the consumer selected, the attachments), pulls the consumer's account file from the servicing or origination system, and drafts an acknowledgment that references the specific situation the complaint describes and the specific investigative path the company will run. The draft goes to a human reviewer with the account context attached, and the reviewer's approval sends the acknowledgment through the portal inside the 15-day window, typically inside 72 hours of the complaint's arrival.

The 60-Day Substantive Response and the Specific Categories the Company Selects

The substantive response is the response the Bureau publishes as the company's disposition of the complaint. The company selects a response category from the fixed set the portal offers: "Closed with monetary relief," "Closed with non-monetary relief," "Closed with explanation," "Closed" (used sparingly for administrative closes), and "In progress" (an interim status that becomes a final response later). The response category is the field the public database exposes, and the category selection is the field examiners read to understand the company's operational disposition of the complaint volume.

The Company Portal Manual defines each category with specifics that map to a specific business decision. "Closed with monetary relief" means the company provided the consumer a monetary remedy, and the response records the amount. "Closed with non-monetary relief" means the company took an action for the consumer that was not a payment, such as correcting a credit-report entry, waiving a fee, or restoring an account privilege. "Closed with explanation" means the company reviewed the complaint and provided the consumer with an explanation of why no relief was warranted. The three closure categories are the categories the Bureau's data team uses to characterize the company's response mix.

The response mix is a supervisory signal. A company whose response category on a specific product line is nearly all "Closed with explanation" while a peer's response mix on the same product line includes a meaningful share of "Closed with non-monetary relief" is a company whose supervision conversation will include the question of whether the "explanation" category is doing work the "relief" categories should be doing. The response category is a specific decision the workflow makes, and the decision's basis has to be documented.

The substantive response also includes a private narrative the company sends to the consumer and, at the company's option, a public narrative the Bureau publishes on the complaint database. The public narrative is the company's opportunity to explain the response in the public record, and the choice to publish or withhold the public narrative is a strategic choice the compliance and communications teams make together.

The agent's response-drafting workflow reads the complaint file, reads the account file, reads the specific investigative record the company's operations built, and drafts the private response and the optional public response with the specific reference to the consumer's issue, the specific investigative steps, and the specific disposition rationale. The draft goes to the complaint-response team's reviewer with the response category recommendation and the supporting file attached. The reviewer's approval sends the response through the portal.

The Issue and Sub-Issue Taxonomy and Why the Tag Discipline Matters

The complaint enters the portal with a product, a sub-product, an issue, and a sub-issue the consumer selected from the Bureau's fixed taxonomy. The taxonomy is specific: "Mortgage" as the product has sub-products like "Conventional home mortgage," "FHA mortgage," "VA mortgage," and "Home equity loan or line of credit." Under each sub-product the issue and sub-issue drill into specific complaint content ("Trouble during payment process" with sub-issue "Escrow, taxes, or insurance," for instance).

The company can dispute the consumer's product, issue, or sub-issue selection through the portal's re-tagging mechanism. The Consumer Response Annual Report has repeatedly noted that a share of complaint volume is re-tagged by companies during handling, and the re-tagging matters because the public database's aggregation of complaints by issue category is the aggregation the Bureau, journalists, consumer advocates, and researchers cite in their analysis.

The tag discipline the operations run is a discipline that affects the company's public footprint. A mortgage servicer whose portal volume on the "Escrow" sub-issue is materially higher than a peer's is a servicer whose escrow operations are a candidate for a supervisory focus. A servicer whose accurate re-tagging surfaces that the volume on the "Application, originator, mortgage broker" issue is actually about origination and not about the servicer's operations is a servicer whose file supports the re-tagging. The re-tagging is a specific action the workflow takes with the specific basis documented.

The agent's tagging workflow reads the complaint narrative, reads the account file, and evaluates whether the consumer's product/issue/sub-issue selection is consistent with the substantive content of the complaint. A discrepancy triggers a re-tagging recommendation with the specific narrative content and the specific account facts supporting the recommendation. The recommendation goes to the reviewer's decision, and the approved re-tag is submitted through the portal with the required company response.

The Consumer Feedback and What Replaced the Dispute Field

The Bureau replaced the "Consumer disputed?" field with a "Consumer feedback" mechanism in April 2017. Consumers may now provide feedback on the company's response within 60 days, but the feedback does not create a formal dispute status the Bureau republishes as a per-company rate the way the old field did. The historical Consumer disputed? field only applies to complaints filed before that change and is still queryable in the public database's older records.

The feedback replaces the dispute in signal, not in operational effect. A consumer whose feedback says the response was unresponsive is a consumer whose feedback the Bureau's supervision reads when it samples the company's complaint file, and a portfolio pattern of feedback that expresses dissatisfaction is a portfolio pattern the Bureau's exam correlates against the response-category mix and the repeat-complaint rate.

The company's options after receiving negative feedback are to update the response through the portal with additional information or additional relief, or to leave the response unchanged. There is no separate "post-dispute update" workflow the way there was under the pre-2017 regime; the update path is the same portal update path that would apply to any post-response correction.

The internal quality metric that best tracks the substantive quality of the response is the feedback-negative rate combined with the repeat-complaint rate. A company whose 15-day acknowledgment rate is 100 percent and whose 60-day response rate is 100 percent but whose feedback-negative rate is elevated and whose repeat-complaint rate on similar issues is high is a company whose response quality is where the operational improvement lives. Those rates are the metrics the operations team tracks, and the per-issue breakdown is what the root-cause team reads.

The agent's feedback-handling workflow reads the consumer's feedback submission (or, for the pre-2017 legacy population, the dispute submission), re-reads the original response, re-reads the underlying account file, and drafts an updated response with additional information, a relief-adjusted response, or a maintained-response justification with the reasoning. The reviewer's decision selects the path.

The Root-Cause Loop and the Portfolio Pattern the Bureau Actually Reads

The individual complaint is the surface event. The pattern of complaints across the portfolio is the substantive signal the Bureau reads. A servicer whose escrow-related complaints are running at a certain rate per thousand loans, whose per-thousand rate is elevated versus peers, and whose complaint volume tracks with a specific product change or a specific operational event is a servicer whose supervision file has a specific pattern the Bureau will ask about.

The root-cause loop is the operational discipline that connects the individual complaint to the systemic fix. The complaint's substantive investigation identifies the specific process failure, the specific vendor issue, the specific policy gap, or the specific system defect that produced the complaint's underlying event. The root-cause finding drives a corrective-action plan, and the corrective-action plan's execution reduces the recurrence rate on the specific complaint pattern.

The Bureau's supervision manual on complaint programs specifically evaluates whether the company's complaint program includes a root-cause analysis, tracks the specific patterns the analysis surfaces, and drives the corrective action the analysis recommends. A company whose complaint program produces individual responses without the root-cause loop is a company whose program the examiner will describe as procedural rather than substantive.

The agent's root-cause workflow aggregates complaints across the portfolio by product, issue, sub-issue, and specific narrative themes the agent's text analysis extracts. The aggregation produces per-week and per-month trend data on specific complaint categories, flags material changes in the trend against the baseline, and produces the root-cause packages the compliance team uses to drive corrective action.

The Cross-Referral Web the Portal Actually Runs

The Consumer Response portal does not exist in isolation. Consumers file the same or similar complaints through state attorney-general offices, state banking-department portals, the Better Business Bureau, the Office of the Comptroller of the Currency's Customer Assistance Group, the Federal Reserve's Consumer Help, and the FDIC's Consumer Assistance Group. The portal has referral relationships with several of these channels, and a complaint filed through one channel can appear in the company's portal queue as a referred complaint.

The referred complaints carry the same 15-day and 60-day response obligations and produce the same public record. The company's operational workflow has to accommodate the fact that the same underlying consumer situation may appear in multiple portals and that the responses need to be internally consistent even if they are provided through different channels.

The specific state-level equivalents matter for institutions with concentrated state footprints. A New York-chartered bank whose complaint volume is a mix of Consumer Response portal referrals and New York Department of Financial Services direct complaints is a bank whose workflow has to run both channels with the same substantive discipline. The Bureau's supervision reads the CFPB portal record and the state supervisor reads the DFS record, and both records are the record the institution's compliance file supports.

The agent's cross-referral workflow reads the incoming complaint from any of the aggregated channels, matches it against the account file, checks for related complaints across other channels on the same consumer or the same account, and coordinates the response across channels to keep the substantive content consistent.

The Executive-Response Path and the Complaint Volume the Legal Team Actually Owns

A share of the portal complaints will require executive-response treatment: a complaint from a consumer whose situation is complex, whose potential litigation exposure is real, whose regulatory-relations sensitivity is high, or whose specific facts require senior review before the response goes out. The executive-response path is the operational lane the compliance and legal teams reserve for the complaints that need the additional review, and the routing of complaints into that lane is a decision the workflow has to make.

The routing criteria are specific to the institution's risk appetite. Common criteria include complaint amounts above a specific threshold, specific product categories (foreclosure, adverse action on a large credit line, elder-financial-exploitation allegations), specific consumer characteristics (attorney representation indicated in the narrative, media reference in the narrative, specific state-attorney-general involvement mentioned), and specific narrative themes the agent's classification detects (discrimination allegations, fair-lending references, criminal-conduct allegations by the consumer).

The specific routing decision is the specific decision the workflow makes at intake, and the decision routes the complaint into either the standard response lane or the executive-response lane. The executive-response lane has different SLAs internally, different review levels, and typically a different response-drafting process.

The agent's routing workflow reads the complaint against the routing criteria the institution has defined, produces the routing recommendation with the specific criteria matches noted, and hands off the routed complaint to the appropriate response lane. The complaints in the executive-response lane still get the agent's drafting support, but the review path is materially more involved.

The Portal Metrics That Matter and What We Actually Track

The internal metrics we track on a portal-complaint operation are:

Response timeliness — the share of complaints acknowledged inside 15 days and responded to inside 60 days. The target is 100 percent on the timeliness metrics, and any complaint that misses the window is a specific operational failure the workflow's after-action review examines.

Response category mix — the distribution of responses across "Closed with monetary relief," "Closed with non-monetary relief," "Closed with explanation," and other categories. The mix's stability over time is a signal of the operational and product-quality baseline; a shift in the mix is a signal something changed that the root-cause team should investigate.

Consumer feedback-negative rate — the share of responses that draw negative feedback from the consumer through the post-2017 feedback mechanism (or, for legacy pre-2017 complaints, the disputed-response rate on the historical field). The rate is not a public per-company metric the way the pre-2017 dispute rate was, but it is a strong internal signal of response quality and the per-issue breakdown is where the operational improvement lands.

Repeat-complaint rate — the share of complaints from consumers who have complained before on the same account, either in the portal or through the internal complaint channel. Repeat complaints are the signal the prior resolution did not stick, and the repeat rate on a specific pattern is the strongest signal for root-cause investigation.

Root-cause remediation rate — the share of identified root-cause findings that drove a specific corrective action and the share of corrective actions whose implementation reduced the recurrence rate on the specific pattern. The remediation rate is the metric that connects the complaint program to the operational improvement the program is supposed to produce.

The Audit File the Examiner Reads

The audit file per portal complaint includes the original complaint content the consumer submitted, the intake classification and routing decision the workflow made (with the reasoning), the 15-day acknowledgment content and delivery evidence, the substantive investigation record (the accounts pulled, the documents reviewed, the personnel consulted, the vendor contacts made), the 60-day response content with the response category and the private and public narratives, the consumer feedback (or, for pre-2017 legacy complaints, the dispute) and the company's post-response action if any, and the root-cause finding if the complaint was elevated to the root-cause workflow.

The completeness of that record is the defense to the specific examination question about the complaint program. The examiner's request is typically a sample of the complaint volume from a specific period with the specific per-complaint file. The company whose record is complete for every sampled complaint is a company whose program the examiner will describe as substantive. The company whose record has gaps — missing investigations, generic responses without account-specific reasoning, missing root-cause findings on repeat patterns — is a company whose program the examiner will describe as procedural.

The agent's audit-file workflow produces the record per complaint as the workflow runs, indexes the record for retrieval on a per-complaint or per-portfolio-pattern basis, and archives the record for the retention period the company's record-retention policy requires, typically the longer of the CFPB's guidance and the specific state supervisor's requirement.

The Failure Mode We Engineer Against

The pattern that produces the worst Consumer Response outcomes is the operation whose response timeline is met on paper but whose response content is boilerplate, whose response category is "Closed with explanation" as the default regardless of the substantive investigation, whose consumer-feedback signal is negative because the responses do not resolve the underlying consumer situations, whose repeat-complaint rate is high because the fixes do not stick, and whose root-cause loop does not exist because the individual complaints are treated as isolated events. The Bureau's supervisory read of that operation is a read that the complaint program is not doing the work the Bureau's supervision manual contemplates.

The architecture we run against that is a workflow whose intake routes complaints correctly, whose investigation touches the actual account and produces specific findings, whose response references the consumer's specific situation and the specific investigative work, whose tagging is accurate and re-tagged when the consumer's selection is off, whose feedback-handling reads the consumer's substantive concern rather than reiterating the prior response, and whose root-cause aggregation drives operational fixes the compliance team can point to in an examination.

The consumer's experience in this model is that the acknowledgment arrives fast and references the consumer's specific situation, the substantive response arrives inside 60 days with specific reasoning, and the disposition is either specific relief or a specific explanation the consumer can understand. The Bureau's experience is that the company's record supports a professional complaint program with a substantive root-cause loop, and the examination conversation is about specific supervisory questions rather than about the program's foundational quality.

The Honest Read

The Consumer Response portal is the surface every consumer-financial-services company is measured on and the surface where the quality of the complaint program is most publicly visible. The 15-day and 60-day timing rules are the surface metric; the substantive quality of the response, the accuracy of the tagging, the consumer-feedback signal, and the root-cause loop are the substantive metrics that determine how the program actually performs. The AI agent's contribution is to make the intake fast, the investigation specific to the account, the response drafted with the actual facts, and the root-cause aggregation something the compliance team can act on rather than a report that lands in a queue and dies.

We have written separately on the Reg X 1024.35 notice-of-error and 1024.36 request-for-information workflow that overlaps with the mortgage-portal complaint pattern, on the Reg E 1005.11 error-resolution regime whose disputes often surface as portal complaints, on the FCRA furnisher-accuracy framework whose Metro 2 disputes overlap with the credit-reporting complaint volume, and on the UDAAP framework at 12 USC 5531 and 5536 whose evaluation of the complaint pattern is a specific supervisory read. The Consumer Response portal sits at the intersection of consumer protection and public accountability, and the operation whose portal record supports the substantive program is the operation the Bureau's supervision reads as taking the work seriously.