Consumer Duty moved the bar from good intentions to evidenced outcomes. We build the customer contact layer that produces that evidence as a by product of doing the work properly.
The Fortay impact in financial services
Queues at the moment of highest anxiety. Some abandon and never come back.
Answered at any hour with intent captured before a person is involved.
The same details taken three times across three channels.
Identified once. Context carried into every onward handoff.
Spotted if the agent is experienced and not under pressure.
Indicators detected consistently and escalated under a documented protocol.
Deflected from the queue rather than resolved. The customer contacts again.
Resolved end to end or routed to the right person with full context.
Handling time is measured. Outcome is not. The file cannot answer the FCA.
Resolution quality and understanding and escalation rate all captured by default.
Deflection and resolution are not the same thing. Deflection reduces inbound volume. Resolution delivers the outcome the Duty requires, and it is the only one of the two you can evidence.
This is why assembling a Consumer Duty evidence pack is a project rather than a report.
Who called, but not the outcome.
The account or policy, but not the conversation.
What was promised, but rarely what was delivered.
The complaint, but not the signs that preceded it.
A sample of calls rather than all of them.
It is a hard question to answer internally. Pilots stall in governance, contact data sits across five systems, and it is difficult to say with confidence which use cases are safe to automate.
Fortay Connect is an independent CX and communications consultancy. We work across the market leading communications and contact platforms, which is what lets us stay outcome focused and technology neutral. Regulated firms bring us in to design the governance first, work out which contact types can be automated safely, and then build on whatever fits the risk profile.
Most of the work is in setting the boundaries. The technology decision comes after.
Three weeks. We map where contact is lost, where evidence is missing, and which use cases your risk profile will support. You keep the findings.
What the review coversThey did not arrive with a platform under their arm. They arrived with a notebook.
The strawman comparison made the decision obvious because the work behind it was rigorous, and the partnership has run straight through into delivery.
A 157 year old Welsh mutual. Three platforms benchmarked through a structured RFP, then delivered by the same team that ran the discovery.
Ordered by how quickly the value arrives. Each one produces evidence as a by product rather than as a reporting exercise.
Detection sits in the contact layer rather than depending on which agent happened to take the call.
Governance designed before the technology goes live, not retrofitted after an incident.
Cost per contact falls either way. Only resolution evidences a good outcome.
Assembling the Duty evidence pack stops being a manual exercise across five systems.
Claims contact at the worst moment of a customer's year. Vulnerability is the norm rather than the exception.
Branch heritage, closed core platforms, and members who expect to be known.
High volume contact, affordability conversations, and a heavy complaints backdrop.
Fewer contacts, higher consequence, and an evidence burden on every one.
Arrears and forbearance conversations where the escalation path has to be provable.
The FCA has confirmed that AI accountability fits inside existing SM&CR structures. There is no standalone AI Officer role.
Sources: FCA commentary on AI accountability under SM&CR, and NICE research on vulnerable consumers, 2025.
We work across the market leading platforms, so the design follows the outcome and the risk profile rather than a single product set.
Contact flow across channels, the systems holding each part, and where evidence is currently missing.
Which contact types can be automated safely under your risk profile, and which cannot.
Governance first, then technology. Explainable by design so the accountable Senior Manager can own it.
We do not stop at go live. We embed the behaviours and the measurement that keep the evidence intact.
Ten questions on how customers reach you, what gets recorded, and what you could evidence if the FCA asked tomorrow. You get a score, a benchmark against firms of similar size, and your two weakest areas.
We measure where contact is lost and where evidence is missing rather than asking you to describe it. Week one is discovery across your contact data and systems. Week two is analysis. Week three is the readout to your executive or risk committee.
The fee is credited in full against the first implementation phase if you proceed within 90 days. The findings are yours outright and portable to any provider.
Book a scoping callHow to scope and frame discovery before any technology decision, including the tractability questions to work through first.
Yes, provided you can evidence good outcomes rather than good intentions. That means interaction logging, retrievable audit trails, and outcome metrics such as resolution quality and consumer understanding and vulnerability escalation rate. Deflecting a contact is not the same as resolving it, and only resolution evidences a good outcome.
Accountability fits inside your existing structures and does not require a standalone AI Officer role. In practice AI risk sits with the Chief Risk Officer under SMF4 or the Chief Operations Officer under SMF24. A named Senior Manager is already accountable, which is why we design the governance framework before anything goes live.
In most cases yes, and often without touching the core platform at all. Where a modern API exists the connection is direct. Where a legacy core exposes nothing usable, automation can work at the interface layer, reading documents and driving the screens your staff already use. One building society automated three roles of back office data entry this way without the core platform being modified.
Detection sits in the contact layer and runs on every interaction rather than depending on which agent takes the call. Indicators of distress and confusion and financial difficulty are identified in real time, and a documented protocol escalates to a person with the full record preserved. The AI never decides vulnerability status on its own.
Usually, and the blocker is often not the technology. Pilots stall on governance sign off, on IT capacity, or because the use cases in scope were never agreed. Establishing the boundaries and the evidence model first is what gets them moving, which is what the review is for.
Three minutes for a read on where you stand, or a scoping call if you want us to go and measure it properly.