Building CRM and customer engagement for a next-generation digital bank

A digital bank still needs a human service operation

A greenfield digital bank starts without inherited branches, service processes or organisational muscle memory. That freedom is valuable, but it creates a harder question: when a customer needs help, how does the entire bank respond as one institution rather than a collection of channels and departments?

My remit covered both sides of that question. I led the CRM implementation and, in parallel, shaped the customer engagement strategy, established the Client Service Management team and worked across the bank to define how service should actually be delivered.

CRM was the operating backbone, not a database

We implemented Salesforce Service Cloud as the core service platform. The aim was not simply to record customer contacts. It was to give the bank a resilient operational layer where an interaction could become an owned case, follow the right workflow and remain visible until resolution.

Telephony was integrated into the same environment so agents could work with customer context rather than switch between disconnected systems. Service workflows were mapped end to end and automated inside CRM, creating consistent routing, ownership and escalation across the operation.

• Salesforce Service Cloud as the central service workspace
• Integrated telephony and customer context
• Mapped and automated service workflows
• Clear case ownership, routing and escalation

Stretching the platform beyond conventional CRM

A greenfield build rewards platforms that can solve adjacent problems without creating another operational silo. One example was an integrated branch visit management capability developed inside the core CRM. It allowed the physical service moment to remain connected to the same customer record and service process used by the rest of the bank.

That decision illustrates the broader architecture: channels could vary, but the operating truth should not. Reusing the CRM workflow, permissions and case model reduced fragmentation and gave teams one place from which to understand and act on customer needs.

The technology only worked because the organisation changed with it

A technically complete CRM does not create customer engagement on its own. The parallel work was to define the engagement strategy, stand up the Client Service Management function and make service quality a shared responsibility across departments.

That meant aligning teams around hand-offs, escalation paths and the outcome the customer should experience. It also meant translating recurring service issues into operational feedback, so the CRM became a mechanism for learning and improvement rather than only a system of record.

• Customer engagement strategy and service principles
• Client Service Management team design and mobilisation
• Cross-department ownership of the customer outcome
• Operational feedback loops from service into improvement

A service capability built to move and endure

The result was a CRM capability that could support the speed of a new digital bank without treating resilience as an afterthought. It connected frontline service, workflow automation and organisational accountability around the customer.

Salesforce later featured the work and invited me to discuss how ila Bank balanced digital-only banking with service excellence. The recognition mattered because it reflected the real achievement: not the installation of a platform, but stretching it into the operational backbone of the bank.