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.
Complaint operations for UK financial services
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.
The complaint lifecycle
Connected work. Accountable resolution.
Scope
A route grounded in context
Ownership
A clear next action
Evidence
Decision context together
Review
People accountable for outcomes
ResolveCX complaint operations
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.
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.
Keep a named owner and next action visible. Configure timelines and escalation paths around the firm's validated complaint types, calendars and policies.
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.
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.
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.
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
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.
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.
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.
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.
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
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.
| Stage / route | Rule and timing | Firm responsibility |
|---|---|---|
| Receipt and progress | Prompt 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 resolution | Resolved 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 route | By 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 route | For 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 delay | Only 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.
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 limitsKeep 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 recordsConsider 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 resourcesFG21/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 customersCONC 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 policiesExplore ResolveCX
See how complaint handling fits within the broader ResolveCX platform and financial-services operating model.
Reporting context
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
Use discovery to establish a clear operational fit before agreeing scope.
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 software helps UK regulated firms capture, assign, investigate and respond to complaints. It supports case ownership, configured deadlines and evidence, but the firm must determine the applicable rules and reach fair decisions.
Not every complaint has an eight-week final-response deadline. Under DISP 1.6, the general route requires a final or qualifying written response by eight weeks after receipt. EMD and PSD complaints normally require a final response within 15 business days after the day of receipt. Exceptional reasons beyond the respondent's control allow a holding response within 15 business days and a final response within 35 business days. Firms must check scope, exceptions and calendars.
DISP 1.6.1 requires a prompt written acknowledgement explaining the applicable response route, and subsequent progress information. Five business days is not a universal FCA acknowledgement deadline. Internal service targets must not replace the applicable rule; the early-resolution provisions also need consideration.
Under DISP 1.5, where the complainant accepts resolution by close of the third business day following receipt, the firm must promptly send a written summary resolution communication. It records that the firm considers the complaint resolved and includes the required FOS referral information, website and applicable time-limit wording.
DISP 1.9 requires a record of each complaint and measures taken for resolution. From receipt, retain it for 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. Other applicable obligations and policies must also be assessed; this is not a blanket five-year rule for all MiFID complaints.
The consolidated return replaces five existing returns with permission-based sections, revised taxonomy and individual legal-entity reporting rather than group reporting. It includes two specified vulnerability data points. The first fixed six-month reporting period is 1 January to 30 June 2027. Check the current FCA specifications with your reporting team. Any required mapping, export or RegData submission process should be assessed separately when evaluating ResolveCX.
ResolveCX helps organise complaint cases, ownership and investigation context. Firms should use complaint causes, outcomes and corrective actions alongside other evidence to monitor Consumer Duty outcomes, challenge recurring harm and review whether interventions work. Software does not establish that the Duty has been met.
FG21/1 and Consumer Duty provide the broad context. Trained staff should consider support needs in context, distinguish an AI cue from a confirmed need, correct errors and decide appropriate support. AI does not diagnose vulnerability. Collect only necessary, lawful information and evaluate privacy, access, retention and error monitoring. CONC 7.2 applies in the narrower consumer-credit arrears and default context.
ResolveCX helps organise complaint context for review. An FOS case file should bring together correspondence, chronology, evidence, decision rationale, redress and the response sent. In your demonstration, review the available records and any export options against your requirements. Firms remain responsible for the completeness and format of their submissions; the Ombudsman makes its own assessment.
No. ResolveCX supports complaint workflows, not legal interpretation or regulatory approval. Firms remain responsible for rule applicability, configuration, training, material decisions, customer responses and governance. AI assistance does not transfer those responsibilities.
Your complaint operating model
Bring your complaint types, ownership and review needs. Explore a tailored ResolveCX workflow with configured deadlines and investigation context.
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.