Rahul Sharma

CX Design · Omni-channel · India BFSI

Customer experience is designed in the gaps between channels.

A customer never meets a bank one screen at a time. They meet it as an app at 11 pm, a call the next morning, a branch visit with a relative, a WhatsApp thread, a letter they never opened. CX design makes all of that behave like one conversation, especially at the moment one channel fails.

7 channels 37 touchpoints 10 failover rules One Customer
Customer Mobile App WhatsApp Web Call Center Retail · Branch Email Social

The universe of CX: seven channels in orbit around one shared memory. Lose a planet and the rest of the system has to know.

Definitions

UX is a screen. CX is the memory.

Three words that get used as one. They are not.

User experience

UX

One product, one task, one screen at a time. Can the customer find it, understand it and finish it without help?

Customer experience

CX

Everything the customer remembers about you across app, web, branch, calls, WhatsApp, email and social, including the handoffs, the waits, and the day something broke.

Service design

The backstage

The people, policies, systems and outside dependencies (NPCI, UIDAI, bureaus, couriers) that make the frontstage possible. Most CX failures are born here.

Why it matters in banking and insurance

Trust is not built when things work. It is decided when they don’t.

The failure moment is the brand.

Nobody remembers the UPI payment that went through. Everyone remembers the one that stayed “pending” at 11 pm, and whether the bank knew before they called.

Every disconnected channel is a place to repeat yourself.

Seven channels without a shared memory are seven versions of “please tell me your problem”. One Customer (auth level, open cases, money objects, the last three lines of the conversation) makes them one conversation.

Friction flows downhill into cost.

A failed self-serve step becomes a call. A 15-minute queue becomes a branch visit. An unanswered branch visit becomes a public complaint with a 30-day clock on it.

Recovery is now regulated.

Reversal timelines with per-day compensation, Key Fact Statements, Ombudsman rights, harassment-free collections. The recovery path is no longer optional design. It is the product.

The instruments

Four views of one system.

This is how I design CX in a bank or an insurer. Each view is live in the simulator below, so you can see how a single failure travels through all four.

Web of CX

Every channel and touchpoint drawn as one web around the Customer, with the failure → recovery pathways between them. It shows where a customer lands when a channel drops them.

Live as: Web of CX
Service blueprint

Nine stages of the relationship × frontstage, backstage, systems and dependencies. When a touchpoint fails, the cells that own that failure light up. Usually more of them than the team expects.

Live as: Service blueprint
Omni empathy map

Think · Feel · Say · Do for the customer across channels. It changes with the failure and with the customer’s emotional state. Panic and delight need different sentences.

Live as: Omni empathy map
Channel failover logic

For each of the ten ways a channel fails: the detector, the primary and secondary fallback, what the customer context carries across, the auto-escalation rule and the SLA.

Live as: Channel failover

What the customer expects after a failure

One thread, many channelsA human two taps awayA promise with a dateVerifiable identity at the moment of riskAutomatic compensation

CX Simulator · India BFSI omni-channel

Break a channel. Watch the system respond.

Pick a failure, set how much friction a touchpoint carries, choose the channel this customer reaches for first and how they feel. The Web of CX, the Service Blueprint, the Empathy Map and the KPIs recompute live.

1Trigger a failure2Click any touchpoint, set its friction3Set channel preference4Set the emotional state
ScenarioBaseline — no failure

Journey risk (Σ / 370)Journey risk

Low
Σ 0

Touchpoints at risk (≥7)At risk

0of 37
Friction 7 or more

SLA exposureSLA

—
From the active failover rule

Predicted NPS zoneNPS zone

Passive0
8 × emotion − 3 × touchpoints at risk

Inputs

Failure triggerPick one of the 10 failover rules; the failed channel, its fallbacks and the home touchpoint update everywhere.
Channel preferenceWhich channel this customer reaches for first.
Customer emotional stateSets the Feel quadrant, the tone rule and the predicted NPS delta.
Neutral·Plain language, one next step
Onboarding & V-KYCFriction 0 · Stable

Selected touchpoint · click any node on the map

Onboarding & V-KYC
Channel Mobile App  ·  Stage Onboard
Friction score0Stable
012345678910
0–3 Stable4–6 Watch7–8 Risk9–10 Fail

Failure mode

Recovery playbook

Web of CX — live

Node fill = friction status · red ring = failed channel · coral ring + arrows = fallback route · dotted ring = preferred channel

Service blueprint — live

A touchpoint’s friction lights the stage × layer cells that own its failure mode; the stage header takes the worst cell.

Tap a cell to see the touchpoints it owns.

Channel failover — active rule

If this fails

—

Detector

Primary fallback

Secondary fallback

Context carried

Auto-escalation rule

SLA

Preferred channelNo preference set

Omni empathy map — live

Quadrants switch with the failure trigger; Feel also follows emotional state.

TTHINK

FFEEL

SSAY

DDO

What the customer expects after a failure

One thread, many channelsA human two taps awayA promise with a dateVerifiable identity at the moment of riskAutomatic compensation

Why this exists

A system is designed at its failure modes.

I built this to make a point I keep making in rooms with product, operations and risk: CX is a system, not a screen. If the recovery path lives in a slide, it does not exist. The simulator is the omni-channel model I use to design one for Indian banking and insurance.