7.4 → 4.1 min
Handle time
94%
Intent recognition
+24 pts
NPS
36
Journeys automated
Client
Leading Kuwaiti Bank
Sector
Banking & Financial Services
Duration
8 months
Team
22 specialists
01 · The challenge

Problem

Contact-centre handle time was 7.4 minutes per call. 60% of calls were repetitive servicing tasks. IVR navigation was a top customer complaint.

02 · How we delivered

Solution

AI conversational banking platform with retrieval-grounded LLM, voice + chat channels, and supervised handoff to human agents. Continuous evaluation with 12-week red-team.

03 · Outcome

Impact

Handle time cut 44% (7.4 → 4.1 min). Intent recognition at 94%. NPS up 24 points. 36 banking journeys fully automated.

How we delivered

Programme phases.

Five phases. One accountable team. Every phase had a named decision point and a measurable outcome.

Discovery & alignment

2–3 weeks

Workshops with the Leading Kuwaiti Bank executive team, baseline metrics, target outcome tree, programme governance set up.

Design & architecture

4–6 weeks

Reference architecture, security blueprint, joint squad model agreed. Data model and integration contracts published.

Build & live-parallel

Q2 onwards

Vertical slice built and run live-parallel against the existing system. Continuous integration, daily deploys, weekly business demos.

Cutover & scale

Mid-programme

Phased cutover, audit-aligned reconciliation, scaling out of squads, capability transfer to Leading Kuwaiti Bank teams.

Run & continuous improve

Steady state

Managed run with named SLOs, quarterly value reviews, and a 15% optimisation budget reserved for improvement work.

Engineering view

Architecture overview.

Foundations

Cloud landing zone, identity, network, security baseline. Data fabric with lineage-by-default. Audit-grade observability stack from day one.

Application & integration

Domain-aligned microservices behind a published API surface. Event-driven core with CDC into the data fabric. Live-parallel capability built in, not bolted on.

Trust & governance

RBAC, audit logs, lineage, policy-as-code. Model risk records for every production model. Compliance posture on the executive dashboard, not in a quarterly slide.

Built on

Technology stack.

Production-grade choices, defended by track record. The stack is one engineering decision among many — but a load-bearing one.

AWS Anthropic Claude OpenSearch Twilio Salesforce Datadog
Trust by design

Governance & assurance.

01

Programme assurance

Independent assurance reviews at each phase gate. Findings tracked in a single risk register with named owners and remediation deadlines.

02

Security & data

ISO 27001, SOC 2 Type II controls applied throughout. Data lineage captured by default; sensitive data tokenised at the edge.

03

Model risk management

SR 11-7-aligned model risk record per production model. Audit-trail evidencing model behaviour against benchmarks at the decision level.

04

Regulator engagement

Quarterly briefings to the regulator with reproducible explainability artefacts. First-attempt acceptance is the default expectation.

A bank that listens — properly — at scale. That is how we differentiate now.

C Chief Customer Officer · Leading Kuwaiti Bank

What we learnt

Three things we would do again.

  1. 01

    8 months from kickoff to first regulated outcome — squad density and decision velocity matter more than headcount.

  2. 02

    Joint squads with Leading Kuwaiti Bank engineers stayed in place after go-live. Ownership did not transfer in a hand-off — it grew in place.

  3. 03

    Live-parallel for a meaningful window before cutover bought us trust. The cutover itself was a flag flip, not a war room.

Book the partner

Want a programme like this one?

Tell us your sector and your timeline. A senior partner with sector experience will respond within one business day.