What Axis Bank Gets Right About Customer Centricity

Most banks talk about putting customers first. Axis Bank built a programme around it, gave it a name, staffed it across 5,800 branches, and embedded it into the annual calendar. That is worth examining — not to applaud, but to understand what separates a genuine customer-centricity strategy from a well-branded internal initiative.

The honest answer is that Axis Bank gets several things meaningfully right, and at least one structural thing wrong. Both lessons are instructive for any organisation serious about achieving customer centricity at scale.

What Customer Centricity Actually Means (Before We Judge Anyone)

Customer centricity is the organisational discipline of consistently making decisions — operational, financial, cultural — that prioritise long-term customer value over short-term internal convenience. It is not a values statement, a service training, or a metric on a dashboard. It is a design principle that must be embedded into how work gets done, how people are hired and rewarded, and how trade-offs are resolved when customer interest and business interest diverge.

That definition matters here because it sets the bar. Many organisations conflate customer centricity with customer satisfaction. Satisfaction is an outcome; centricity is a structural condition that makes sustained satisfaction possible. You can have a good satisfaction score in a quarter where you happened to make things easy. You cannot sustain it without the underlying architecture.

For a deeper look at the definitional distinction, this piece on the SAFe definition of customer centricity and its three most common mistakes is a useful companion.

What Axis Bank Gets Right: The Sparsh Programme

Launched in fiscal year 2022, Sparsh is Axis Bank's flagship customer-obsession initiative. The name means "touch" in Sanskrit — a deliberate signal that the programme is about human contact, not process optimisation. Its four pillars are: crafting delightful journeys, creating employees as delight advocates, building institutional capabilities, and measuring and acting on customer feedback.

By fiscal year 2025, Sparsh operates across all of the bank's 5,800-plus branches and involves all 105,000-plus employees. That is not a pilot. That is a bank-wide operating commitment.

Three specific elements of Sparsh deserve attention from a CX design perspective:

• Sparsh Week: An annual bank-wide event — the October 2023 edition ran from the 9th to the 13th — that features Call Listening Sessions (staff hear real customer calls to identify pain points), a MasterClass Inspire Series with external industry leaders, and customer protection fraud-awareness campaigns. The Call Listening Sessions are particularly well-designed: they force proximity between the people who make decisions and the people who experience consequences.
• Siddhi: An analytics-based virtual coaching platform that delivers hyper-personalised nudges to front-line staff, helping them improve customer conversations and sales interactions. Behavioural nudges at the point of action — rather than generic training delivered once and forgotten — is exactly how you change embedded habits.
• Kaleidoscope: A tool that gives staff a single chronological view of a customer's footprint across channels, improving first-contact resolution. Reducing the number of times a customer has to repeat themselves is one of the highest-leverage friction reductions a bank can make — and it requires exactly this kind of cross-channel data integration.

Together, these components address three of the most persistent failure modes in large-organisation CX: leadership disconnection from front-line reality, generic training that doesn't change behaviour, and siloed channel data that forces customers to re-explain their situation at every interaction.

The CRM Result That Validates the Approach

In partnership with CRMNEXT, Axis Bank deployed an enterprise-wide CRM system covering over 35 million customers and 80,000 users. The implementation won the Best CRM Implementation award at the Asian Banker Financial Technology Innovation Awards 2022, with the bank reporting a 75% improvement in customer satisfaction and a 230% rise in campaign efficiency following deployment.

Those are significant numbers. The satisfaction figure in particular suggests the CRM was not merely an operational efficiency play — it had a measurable effect on the customer's experience of the bank. That is the right outcome to optimise for, and it is the right way to present the business case: customer satisfaction and operational efficiency moving in the same direction.

This is the business case for customer centricity made concrete. When you reduce the effort required to serve a customer well — through better data, better tooling, better front-line capability — you simultaneously reduce cost and improve experience. The two are not in tension; the tension is usually a symptom of poor design.

The Behavioural Mechanics Behind What Works

It is worth naming why these specific interventions work, because the mechanism matters more than the initiative name.

The Call Listening Sessions during Sparsh Week exploit a well-documented principle: the affect heuristic. When decision-makers hear a real customer voice — frustrated, confused, or delighted — their emotional response to that voice changes the weight they assign to customer impact in subsequent decisions. Abstract data does not do this. A recorded call of a customer trying and failing to resolve a billing dispute does. Axis Bank has institutionalised the conditions under which empathy is not a personality trait but a designed experience for its own staff.

The Siddhi nudge platform applies choice architecture at the front line. Rather than relying on staff to recall training from a classroom session weeks earlier, it delivers contextually relevant prompts at the moment of decision. This is how you reduce the gap between what people know they should do and what they actually do under time pressure — which is the gap that kills most CX programmes.

Kaleidoscope, meanwhile, directly addresses friction — specifically the category Richard Thaler distinguishes as sludge: effort imposed on customers by systems designed for the organisation's convenience rather than the customer's. Asking a customer to re-authenticate, re-explain their history, or navigate between departments is sludge. A unified chronological view of the customer relationship removes it at the source.

What Axis Bank Does Not Yet Get Fully Right

Here is the structural tension: Sparsh is an excellent programme for improving how the bank serves customers within its existing model. It is less clearly a mechanism for questioning whether the model itself serves customers well.

True customer centricity requires the willingness to redesign products, policies, and processes that are structurally inconvenient for customers — even when those products and processes are profitable. A Call Listening Session that surfaces the insight "customers find our fixed-deposit break penalty confusing and punitive" is only valuable if it has a pathway into product policy review. If the insight loops back into better scripting for how staff explain the penalty, the programme has improved satisfaction without improving the experience.

This is the most common mistake in large-organisation CX: optimising the interaction layer without touching the policy layer. The interaction becomes warmer and more efficient; the underlying frustration remains. Customers notice, eventually.

The bank's Customer Experience Index score of 72 in fiscal year 2020–21 — tracked alongside NPS across customer journeys — is a useful baseline, but the published reporting does not make clear how this score has trended since Sparsh's launch in 2022, or what the causal relationship is between specific programme interventions and index movement. Without that transparency, it is difficult to distinguish a programme that is working from a programme that is well-run. These are different things.

For organisations building their own measurement architecture, a structured Voice of Customer strategy is the mechanism that closes this loop — turning listening into evidence that can challenge policy, not just inform training.

The Common Customer Centricity Mistakes Axis Bank Illustrates (and Avoids)

Axis Bank's experience is instructive precisely because it sits at the boundary between genuine customer centricity and sophisticated customer-satisfaction management. The distinction is worth making explicit.

Mistakes Axis Bank appears to avoid:

• Treating CX as a marketing function rather than an operational one. Sparsh involves all 105,000 employees — this is not a brand campaign.
• Measuring only at the aggregate level. Tracking NPS across individual journeys, not just a single bank-wide score, is the right granularity.
• Deploying technology without a behavioural design layer. Siddhi and Kaleidoscope are tools in service of a defined behavioural outcome, not technology for its own sake.
• Running CX as a one-off initiative. Sparsh Week's annual cadence and the programme's multi-year scale suggest institutional commitment, not a project.

Mistakes that remain risks, based on the available evidence:

• Conflating programme activity with customer outcome. Scale and participation are inputs; customer effort, loyalty, and lifetime value are outputs. The causal chain needs to be explicit.
• Limiting the scope of "customer feedback" to service interactions rather than product and policy design. If feedback only informs how you deliver the product, not what the product is, you are listening but not hearing.
• Measuring satisfaction without measuring effort. The Customer Effort Score — how hard it was to get something done — is often a better predictor of loyalty than satisfaction, particularly in banking, where customers rarely feel delighted but frequently feel frustrated.

How to Apply These Lessons to Your Own Organisation

Whether you run a bank, a retailer, or a public service, the Axis Bank case surfaces a practical sequence for implementing customer centricity that goes beyond aspiration.

1. Name the programme and give it structural weight. Sparsh works partly because it has a name, a dedicated week, and a four-pillar framework. Unnamed initiatives die in the next reorganisation. Structural weight means budget, a named owner, and a board-level metric.
2. Design for proximity, not just awareness. Call Listening Sessions are more powerful than customer satisfaction reports because they create emotional proximity between decision-makers and customer reality. Build this into your operating rhythm, not just your annual offsite.
3. Nudge at the point of action, not in the classroom. Training changes what people know. Contextual nudges — delivered at the moment a decision is made — change what people do. Invest in the latter.
4. Remove sludge before adding delight. Most organisations have a backlog of friction that customers have learned to tolerate. Eliminating that friction — the repeated authentication, the unexplained fee, the three-department transfer — delivers more loyalty per pound of investment than any positive experience add-on.
5. Connect listening to policy, not just training. Voice of customer data must have a pathway into product and policy review, not just service delivery improvement. If it doesn't, you are running a sophisticated complaint-management system, not a customer-centricity programme.
6. Measure the trend, not the score. A CX Index of 72 is a number. A CX Index that moves from 72 to 79 over three years, with a documented causal link to specific interventions, is evidence. Build the measurement architecture that makes the causal story visible.

If you are unsure where your organisation sits on this spectrum, the CX Maturity Assessment provides an AI-scored diagnostic across twelve building blocks — a useful starting point before committing to a programme design.

The Deeper Question: Is Customer Centricity a Programme or a Condition?

The most honest critique of any named CX programme — Sparsh included — is that customer centricity, properly understood, should not require a programme. It should be the default condition of how decisions get made. The fact that organisations need to launch initiatives to become customer-centric is evidence that their default condition is something else: cost-centric, process-centric, or hierarchy-centric.

Programmes are necessary because organisations are not born customer-centric; they are built that way, deliberately, over time. But the goal of the programme is its own obsolescence — to embed customer-centricity so deeply into hiring, incentives, governance, and product design that it no longer needs a dedicated initiative to sustain it.

Axis Bank's Sparsh is a serious attempt to move in that direction. The four-pillar framework, the scale of deployment, and the tooling investment all suggest genuine institutional commitment. The question — for Axis Bank and for every organisation running a similar programme — is whether the programme is building the condition or substituting for it.

That question is worth asking before you name your own initiative, design your own measurement framework, or commission your next customer experience strategy. The answer determines whether you are building something durable or something that will require relaunching in three years under a different name.

Customer centricity is not what you call your programme. It is what survives when the programme ends.