Genesys Cloud CX for financial services contact centres

The FCA's Consumer Duty makes customer support one of the outcomes a firm must deliver. Its consumer support rules require firms to design and deliver support that meets customers' needs, including those with characteristics of vulnerability, and that does not put unreasonable barriers in their way, whether they are making a general enquiry, submitting a claim, making a complaint or cancelling a contract. The FCA's rules apply that whatever the channel, including social media, and where firms outsource their interactions with customers in whole or in part.

Firms must also regularly monitor the outcomes customers receive from their communications and their customer support, and have processes to find the root causes when outcomes fall short. For a contact centre, that turns everyday design choices into evidence: how long customers wait, how easily they reach a person, whether leaving or complaining is as easy as buying, and whether journeys work as well by message as by phone. We design Genesys Cloud CX so those measures are captured as part of the service, through flow outcomes, interaction data, quality evaluations and speech and text analytics, rather than reconstructed later.

The FCA describes a vulnerable customer as someone who, due to their personal circumstances, is especially susceptible to harm, particularly when a firm is not acting with appropriate levels of care. Its guidance asks firms to understand their customers' needs, give their people the skills to respond, design products and services with vulnerability in mind, and monitor the outcomes. Much of that lands on the contact centre, because it is often where a customer's circumstances first become visible.

On Genesys Cloud CX, data actions can read a flag or note your systems already hold, so the IVR offers a direct route to a trained team and the agent's script shows what has been shared before, with the customer's consent. Routing can send those customers to agents with the right skills, callbacks can avoid long waits, and every journey keeps a clear way to a person. Speech and text analytics can help quality teams find conversations where vulnerability was disclosed but not acted on, so coaching and process changes follow the evidence.

Taking card payments by phone brings PCI DSS, now at version 4.0.1, into the contact centre. Genesys states that Genesys Cloud is a Service Provider Level 1 compliant with PCI DSS version 4.0, and that its secure flows and secure pause have been validated by an external Qualified Security Assessor. A secure flow lets a caller enter card details in the IVR without agents hearing them or the system recording them, and secure pause stops recording while sensitive details are spoken. We design payment journeys so card data stays out of agents' hearing and out of recordings, and agree with your compliance team which approach suits each journey.

Recording rules depend on what the firm does. The FCA's rules in SYSC 10A require firms such as MiFID investment firms to take all reasonable steps to record relevant telephone conversations and keep electronic communications, generally for five years and up to seven where the FCA requests it. Other firms set retention by their own policies and data protection duties. Genesys Cloud recording policies set what is recorded and for how long, and recordings can be protected from deletion for a legal hold, so we design retention around your obligations rather than the platform's defaults.

The FCA's operational resilience rules required firms to identify their important business services and set impact tolerances by March 2022, and to have mapped and tested them by March 2025. In the EU, the Digital Operational Resilience Act has applied since 17 January 2025. For many firms, customers' ability to reach the contact centre is part of an important business service, so its dependencies, failure modes and recovery need the same care as any other system.

Genesys lists DORA among the frameworks covered by its trust centre, alongside certifications such as ISO 27001 and SOC 2. The contact centre design still matters: what happens when a carrier, an integration or a site fails, which messages callers hear in an incident, and how quickly operations can change routing without a release. We build failure paths for every integration, emergency routing that supervisors can switch on through data tables, and carrier and number plans that avoid single points of failure, then test them so the evidence exists before anyone asks for it.

Customers increasingly expect to check a balance, a claim, a payment or an account without waiting for an agent, and firms want to free their people for the conversations that need them. The risk is self-service that traps customers or asks them to prove who they are more than once. We design voice and digital bots that verify callers once, using data actions against your own systems, carry what they learn to the agent, and always offer a way to a person.

For a national stock exchange, we designed and moved to production more than 150 voice bot flows giving shareholders, financial professionals and those acting for estates real-time self-service in two languages. For a digital banking technology provider separating from its former parent, we built a single unified flow that combines the caller's intent with live Salesforce lookups to route by product. For a global insurer, we carried more than 10,000 knowledge articles from a retired platform to Genesys Cloud CX.

We muster a multidisciplinary team from our own bench, with leadership in contact centre technology since 1984, and every delivery team member holds, or is completing, Genesys Cloud certification. Discovery includes your compliance, risk and information security teams from the start, so obligations become requirements with owners, and every requirement is traced through design to a test. We work directly with firms and through global systems integrators and reseller partners, and we are a Genesys referral partner, not a reseller.

Whether the work is a migration, a new contact centre, self-service or a single integration, the documents your auditors and second line will ask for are produced as we go: requirements specifications, designs, test evidence and go-live method statements. That is how a contact centre goes live with its evidence already in place.