ResolveCX
    Regulatory compliance

    Complaint operations for UK financial services

    FCA Complaint Handling Software

    ResolveCX helps financial-services complaint teams coordinate ownership, investigation context and accountable resolution. Bring the work together from first contact through review, response and follow-through.

    Configured timelines Named ownership Case evidence Accountable review

    Scope

    A route grounded in context

    Ownership

    A clear next action

    Evidence

    Decision context together

    Review

    People accountable for outcomes

    ResolveCX complaint operations

    Coordinate the work from intake to resolution

    ResolveCX brings ownership and case context into one workflow. Configure the process around your operating model, with trained handlers and accountable reviewers making the decisions.

    01

    Capture and classify

    Bring complaint context into a case. AI Classification covers inbound cases, complaints and inquiries; categories can feed configured team routing or immediate escalation, with people reviewing exceptions.

    02

    Assign and track

    Keep a named owner and next action visible. Configure timelines and escalation paths around the firm's validated complaint types, calendars and policies.

    03

    Investigate with context

    Keep evidence and decision rationale together. Case Summarization helps handlers review available case material, with original sources as the reference for checking accuracy and omissions.

    04

    Review and respond

    Build a process for authorised review of material decisions, redress and customer-facing responses. Check outcome, reasons, applicable FOS information and the version actually sent.

    05

    Close with evidence

    Keep the outcome, response and follow-up work in context. Review the available chronology and records against your firm's FOS preparation and retention requirements.

    06

    Learn and act

    Connect recurring issues to investigation and owned corrective actions. Managers decide what is material, agree due dates and assess whether the action has made a difference.

    Evidence and oversight

    Keep decisions reviewable and actions owned

    A useful case file explains what happened and why. Oversight considers customer outcomes, support needs and whether corrective actions work, not only the number of cases closed.

    01

    Make the decision reviewable

    For FOS preparation, bring together the original complaint, correspondence, chronology, evidence, decision rationale, approvals, redress and response sent. Check the request and file completeness; an organised record does not determine the Ombudsman's decision.

    02

    Connect recurring causes to action

    Investigate patterns, assign corrective actions to an owner with a target date, and review effectiveness. Preserve management challenge and follow-through; completing root cause analysis is not proof of remediation.

    03

    Keep AI assistive

    Check source material for summaries and suggested content. Authorised staff should review material decisions and customer responses, correct or override errors, and own the final action. Configured category-based routing need not wait for manual approval of every route.

    04

    Set clear privacy and error checks

    AI does not diagnose vulnerability or infer protected traits. Each firm determines lawful use and data minimisation, and remains responsible for privacy, access and retention controls, source checking, and monitoring errors or missed signals.

    The regulatory framework

    Complaint deadlines depend on the route

    For complaints, compliance and operations teams across UK financial services. Applicability depends on the firm, permissions, product and complaint type. DISP uses different response routes, not one universal timer.

    FCA DISP response routes
    Stage / routeRule and timingFirm responsibility
    Receipt and progressPrompt written acknowledgement explaining the applicable response route; keep the complainant informed of progress.Agree ownership and internal targets. There is no universal five-day acknowledgement rule.
    Early resolutionResolved by close of the third business day following receipt, with the complainant's acceptance: promptly send a summary resolution communication.Record acceptance and resolution date, with the required FOS information. DISP 1.5 disapplies the time-limit rules where it applies.
    General eight-week routeBy the end of eight weeks after receipt, send a final response or a qualifying written response explaining the delay and expected response date, with FOS information.Check applicability and exceptions. Eight weeks is not a universal final-response deadline.
    EMD / PSD routeFor e-money (EMD) and payment-services (PSD) complaints, send a final response by the end of 15 business days after the day of receipt.Use the applicable business-day calendar, not a calendar-day timer. Check mixed complaints and relevant parts.
    Exceptional EMD / PSD delayOnly where reasons beyond the respondent's control prevent the final response: send a holding response within 15 business days and a final response within 35 business days after the day of receipt.The holding response must explain the reasons and specify the final-response deadline. This is not a routine extension.

    ResolveCX workflows can be configured around validated rules and escalation thresholds. Teams confirm the applicable calendar, receipt date, exceptions and temporary or sector-specific rules when setting timers.

    01

    Responses and FOS information

    Keep the outcome, reasons, redress and response sent with the case. For the applicable route, check the Financial Ombudsman Service (FOS) referral rights, leaflet, website and time-limit wording. EMD/PSD final responses must be on paper or another agreed durable medium.

    FCA DISP 1.6: complaint time limits
    02

    Complaint records and retention

    Keep a record of each complaint and the measures taken to resolve it. From receipt, DISP 1.9 requires at least five years for collective portfolio management services for a UCITS scheme or a scheme that was an EEA UCITS scheme immediately before IP completion day, and three years for other complaints. Assess other applicable obligations too.

    FCA DISP 1.9: complaint records
    03

    Consumer Duty oversight

    Consider complaints alongside other evidence when reviewing outcomes, recurring harm and differences between customer groups. Bring causes, outcomes, redress and action effectiveness into senior management and board review. Case records alone do not demonstrate good outcomes.

    FCA Consumer Duty publications and resources
    04

    Vulnerability and support needs

    FG21/1 describes health, life events, resilience and capability as four drivers of vulnerability. Trained staff should understand a customer's circumstances and agree appropriate support. Read FG21/1 alongside current Consumer Duty expectations.

    FCA FG21/1: fair treatment of vulnerable customers
    05

    Arrears and default context

    CONC 7.2 concerns appropriate policies for consumer-credit customers in or approaching arrears or in default, including fair treatment of those understood or reasonably suspected to be vulnerable. It is not the broad vulnerability framework for all financial services.

    FCA CONC 7.2: arrears and default policies

    Reporting context

    Prepare for the consolidated complaints return

    PS25/19 replaces five returns: DISP 1 Annex 1, Consumer Credit (CCR), Funeral Plans (FP), Claims Management Companies (CMCs), and Electronic Money and Payment Services (PSR). Permission-based sections and revised product/service taxonomy replace a one-size reporting approach. Reporting is at individual legal-entity level, not group level.

    First fixed reporting period

    1 January to 30 June 2027

    Firms should collect the required data from 1 January. The two specified vulnerability data points cover customers identified as being in vulnerable circumstances, regardless of disclosure method, and complaints relating to or caused by failure to consider or respond to vulnerability. Collect data lawfully, including under data protection law.

    The FCA reporting page, updated 25 September 2026, also notes targeted-support and Deferred Payment Credit changes and published RegData resources. Confirm current specifications, taxonomy and entity ownership with your reporting team. Treat data mapping, export formats and any RegData submission process as separate requirements to evaluate.

    Buyer evaluation

    Questions to bring to implementation

    Use discovery to establish a clear operational fit before agreeing scope.

    • How should each complaint route handle calendars, exceptions and escalation?
    • Which chronology, source evidence and response versions will your FOS and governance reviews need?
    • How will staff check AI suggestions against sources, correct errors and review material responses?
    • What current evidence is available for access, audit history, retention, hosting, security and integrations?
    • Which reporting fields and export processes are required for each permission and legal entity?

    Discovery can cover rule validation, configuration, migration assessment, testing, training and launch criteria. Agree supported data and attachment scope, connected systems, ownership and rule-change review before committing to a plan. Delivery timing and migration formats depend on the agreed scope.

    Buyer questions

    FCA complaint handling questions

    Your complaint operating model

    See how complaint work can stay connected

    Bring your complaint types, ownership and review needs. Explore a tailored ResolveCX workflow with configured deadlines and investigation context.

    Sources and editorial history

    Published . Updated . Last reviewed by Product Management, Product Manager; product and content review (not legal/compliance sign-off). Primary sources checked on 17 October 2026. The latest edits await qualified compliance review. This page provides general information, not legal advice or regulatory approval.

    This information is not legal advice. Firms remain responsible for applicable rules, configuration, staff training, decisions and effective governance.

    Start Resolving. Not Tracking.

    Start Resolving. Not Tracking.

    See how ResolveCX helps teams manage cases, escalations, incidents, and customer issues with greater speed, accountability, and control.