Poornima_Gupta_aZ3h

Position: Reject or Rethink the Change — View B

This is a classic case of the AI efficiency versus customer experience trade-off — and it is one of the most common mistakes organisations make when deploying AI for the first time. This organisation measured three things — handling time, cost per interaction, and cases per day. None of those three metrics measure whether the customer actually got what they came for. That is the entire problem.

Why the Efficiency Gains Here Are an Illusion, Not a Win
Imagine you run a bakery. You find a way to serve customers 30% faster. But the bread tastes worse, customers feel rushed, and half of them stop coming back. Did you win? No. You just moved the cost from the counter to the empty shop.
That is exactly what is happening here.
The core error in View A is treating cost-per-interaction as a profit driver when it is actually a cost-deferral mechanism. When first-contact resolution drops and satisfaction falls 8–10%, the organisation is not saving money. It is moving costs downstream. Customers who feel rushed and misunderstood do not disappear. They call back, escalate to supervisors, churn, and tell others. Every single one of those outcomes costs more than the handling time saved.
This is called the efficiency-satisfaction trap — internal numbers look better while the outcomes customers actually care about quietly get worse, until the real cost shows up in churn, complaints, and lost revenue.
The most damning number in this scenario is not the 8–10% satisfaction drop. It is the first-contact resolution decline. That one number tells you everything. Customers are not getting their problems solved. They are calling back. Every repeat call costs more than the time saved on the first one. The efficiency gain is already negative — the organisation just has not counted it yet.

Real World Evidence — From Banking, Where I Work
1. NatWest Cora+ — The Closest Mirror to This Scenario
NatWest launched a virtual assistant called Cora back in 2017. Sound familiar? It handled routine queries quickly but customers felt like they were talking to a wall. Interactions felt cold, transactional, and unhelpful. The system pointed people to existing content instead of actually solving their problem. Efficiency was there. The customer experience was not.
Rather than shrugging and moving on, NatWest stopped and rethought the entire design. In 2024 they rebuilt Cora into something called Cora+ — powered by generative AI and IBM watsonx technology. The new version actually understood what customers were asking and answered them directly in plain language. The guiding principle was beautifully simple — when someone is worried about their money, they need to feel understood, not processed.
The results spoke for themselves. Customer satisfaction improved by 150%. Human intervention dropped. Efficiency went up. Experience went up. Both at the same time. NatWest also saw Customer Lifetime Value double and Net Promoter Score triple — not soft feel-good numbers, but hard revenue outcomes. By H1 2025 they had deployed 24 more AI models, all built around the same idea — better experience first, efficiency as the reward.
The lesson: You do not have to choose between efficiency and experience. Fix the experience and efficiency follows.

2. DBS Bank — The Most Direct Comparison to This Scenario
DBS Bank in Singapore faced the exact same challenge described in this question — how to handle over 250,000 customer service calls every single month without losing quality. Their answer was not to make conversations shorter. It was to make agents smarter.
They built a Gen AI tool called CSO Assistant — a live co-pilot that sits alongside the agent during every call. It listens, transcribes in real time, searches the knowledge base instantly, and surfaces the right answer while the conversation is still happening. The agent stays in control. The customer still feels heard. And the problem gets solved faster because the agent is not scrambling to find information.
Pilots showed transcription and solutioning accuracy of nearly 100%, call handling time reduced by up to 20%, and close to 90% of customer service officers said it had a positive impact on their work. Across all its AI initiatives in 2024, DBS delivered SGD 750 million in economic value — more than double the previous year.
The design difference is everything. DBS reduced time without removing the human. The scenario we are discussing removed the human without solving the problem. That single decision is what separates success from failure.

3. Bank of America Erica — The Gold Standard
Bank of America had a simple rule when building their AI assistant Erica — start with what the customer needs, not what is easiest to automate. Erica has now handled over 2.5 billion customer interactions with a 98% success rate. Customers either get their answer from Erica or are passed smoothly to a human. No dead ends. No frustration. Bank of America was ranked the most satisfying mobile banking app of any national bank.
The sequencing lesson here is critical. Experience and revenue came first. Efficiency came second. That is the right order. That is why it worked.

The Real Issue — The Scorecard Was Wrong From the Start

Here is a simple truth. The metric you choose to measure determines the result you will get. If you measure how fast you close a call, you will get fast call closures. If you measure whether the customer actually got what they needed, you will get satisfied customers. The organisation in this scenario chose speed. They got speed. And they lost trust.
HSBC proves what good metric design looks like — twice.
1.When HSBC used AI to transform their KYC onboarding process, they did not just measure how fast documents were processed. They measured accuracy alongside speed. The result — processing time dropped from 12 days to under 24 hours while accuracy jumped from 87% to 99%. Both improved because both were measured from day one.
2.When HSBC partnered with Google Cloud on their AML anti-money laundering system, most banks are still drowning in false positive alerts — flagging innocent customers and wasting thousands of investigator hours chasing nothing. HSBC measured what actually mattered — how accurately real criminals were being caught, how much time investigators spent on genuine cases, and how many innocent customers were being unnecessarily disrupted. The system identified two to four times more real suspicious activity while cutting false alerts by 60%. Investigators focused on actual crime. Innocent customers faced fewer unnecessary checks. Everyone won.
HSBC built the scorecard before they built the system. The organisation in this scenario did it the other way around. They measured what was easy to count — speed and cost — and got exactly those things. The problem was never the AI. The problem was the scorecard.

To Be Fair — When View A Can Actually Work
I do not broadly support View A. But a strong argument acknowledges the other side — because showing when something works makes it clearer why it fails here.
Amazon is the textbook example. When Kiva robots rolled into fulfillment centers in 2012, things got worse before they got better. Delivery updates became impersonal. Handling exceptions became harder. But picking efficiency jumped by over 50% and costs per order fell sharply. Here is the crucial part — Amazon did not keep those savings. They reinvested every penny into building next-day and same-day delivery. Today, fast reliable delivery is the number one reason customers love Amazon. The short-term experience dip funded a permanent experience upgrade.
Lloyds Banking Group shows the same thinking applied in banking. Lloyds automated data entry, transaction processing, and basic back-office inquiries. Tasks customers never see or feel. Nobody notices whether a human or a machine processed their data in the background. What customers noticed was faster, more accurate service. The efficiency metric and the satisfaction metric pointed in exactly the same direction because Lloyds chose the right processes to automate.
But this only works when all four conditions are true:
Efficiency gains are reinvested into customer experience — not kept as profit
The experience decline is temporary and fixable, not permanent
Customers have little reason to switch during the difficult period
AI is applied to routine back-office tasks — not emotionally sensitive conversations where trust matters
In the scenario presented, every single one of these four conditions fails.
The savings were not reinvested. The satisfaction decline is not a temporary blip — it is a structural signal that customers consistently feel unheard. Banking customers who lose trust do switch, and winning them back costs far more than any handling time saving ever delivered. And most critically, the AI was placed in exactly the wrong conversations — the moments when someone is worried about their money and needs a human being who actually listens.
That is not one mistake. That is four.

Final Verdict
The change should not be accepted. Not because efficiency does not matter — it absolutely does. But because this organisation has not yet earned the right to claim it.
The banks that get AI right — NatWest, DBS, Bank of America, HSBC — all made the same decision before they wrote a single line of code. They decided what success actually looked like from the customer's point of view. They built the scorecard first. Then they built the system.
NatWest asked — does the customer feel understood?
DBS asked — does the agent have everything they need to help?
Bank of America asked — does the customer get what they came for?
HSBC asked — are we catching criminals or just closing alerts?
The organisation in this scenario asked — how fast can we close the call?
That one question, measured alone, produced exactly the outcome described. Faster calls. Lower costs. Unhappy customers. Declining trust.
Fix the question you are measuring and you fix the outcome. That is the lesson. That is the only lesson.