Customer Relationship ManagementUnit 312 min read
Customer Satisfaction & Expectations: Theories, Gaps & CRM Impact
Unit 3 of Customer Relationship Management explores how customer expectations shape satisfaction, the expectation-performance gap model, Kano’s satisfaction theory, and practical CRM applications in Nepal (e.g., Nabil Bank’s complaint resolution, Daraz’s return policies). Covers measurement tools (CSAT, NPS), real-worl
Core Concepts: Definitions & Frameworks
1. Customer Satisfaction: The Foundation of CRM
Customer satisfaction is the net result of comparing a product/service’s perceived performance against a customer’s expectations. It is not just about meeting needs but exceeding them to build loyalty.
Why it matters in Nepal?
- Nabil Bank’s 2023 survey: 68% of customers cited slow complaint resolution as the top reason for dissatisfaction (vs. 42% globally).
- Daraz’s return policy: Customers expect 7-day returns—if not met, they switch to Amazon India (a real competitor).
2. Customer Expectations: The Invisible Benchmark
Expectations are shaped by:
- Past experiences (e.g., if you had a bad experience at NTC, you expect delays).
- Word-of-mouth (e.g., Pathao drivers complain about low pay → customers expect slower service).
- Marketing promises (e.g., Khalti ads say "instant transfer" → users expect <5 sec processing).
- Industry standards (e.g., Nepal Airlines customers expect on-time flights like IndiGo).
3. The Expectation-Performance Gap Model
The most cited CRM framework explains why customers are satisfied, dissatisfied, or neutral.
flowchart TD
A["Customer Expectations"] -->|"High"| B["Perceived Performance"]
A -->|"Low"| B
B -->|"High"| C["Satisfaction"]
B -->|"Low"| D["Dissatisfaction"]
D --> E["Complaint/Churn"]
C --> F["Loyalty/Advocacy"]
G["Gap Analysis"] -->|"Identify"| H["Where performance falls short"]Worked Example: NTC’s Internet Service
- Expectation: Customers expect stable 50 Mbps (like Ncell’s 100 Mbps).
- Performance: NTC delivers 30 Mbps with frequent drops.
- Gap: 20 Mbps shortfall + unreliability → Dissatisfaction → Customers switch to Ncell.
Real-World Fix:
- Ncell’s "Speed Boost" campaign (2023) promised 100 Mbps for Rs. 1,200 → reduced churn by 15% (source: Nepal Telecom Authority Report).
4. Kano’s Model of Customer Satisfaction
Not all expectations are equal! Kano’s theory classifies needs into 5 categories:
| Type | Description | Example in Nepal | CRM Strategy |
|---|---|---|---|
| Basic Needs | Must-haves; no satisfaction if missing | ATM availability (Nabil Bank) | Ensure 24/7 access; no excuses |
| Performance | Linear satisfaction (more = better) | Delivery speed (Daraz vs. Amazon India) | Track & improve (e.g., Daraz’s "Same-Day") |
| Excitement | Delighters; unexpected delights | Free coffee at Himalayan Java | Surprise upgrades (e.g., free shipping) |
| Indifferent | Doesn’t affect satisfaction | Color of Daraz’s website | Ignore (unless it’s a trend) |
| Reverse | More = worse satisfaction | Too many emails from banks (Nabil) | Reduce spam; personalize communication |
Case Study: Himalayan Java’s Loyalty Program
- Basic Need: Coffee quality (met).
- Performance Need: Fast service (improved with mobile ordering).
- Excitement: Free birthday coffee + NEPSE stock tips → 30% repeat visits.
5. Measuring Customer Satisfaction
A. Key Metrics
| Metric | Full Form | How It Works | Nepali Example |
|---|---|---|---|
| CSAT | Customer Satisfaction Score | "How satisfied were you? (1-5)" after interaction | NTC’s post-call survey (avg. 2.8/5) |
| NPS | Net Promoter Score | "Would you recommend us? (0-10)" → Promoters (9-10) – Detractors (0-6) | Daraz’s NPS: +20 (2023) vs. Amazon’s +50 |
| CES | Customer Effort Score | "How easy was it to resolve your issue?" (1-5) | Nabil Bank’s chatbot efficiency |
| RET | Repeat Purchase Rate | % of customers who buy again within 3 months | Khalti’s wallet users: 65% repeat rate |
B. How to Use These Metrics
- CSAT → Identify pain points (e.g., NTC’s slow tech support).
- NPS → Predict growth (e.g., Pathao’s NPS dropped after driver strikes).
- CES → Improve service ease (e.g., Daraz’s 1-click return policy).
6. The Triangular Relationship in Customer Satisfaction
3 key players influence satisfaction:
graph TD
A["Customer"] -->|"Expects"| B["Company"]
A -->|"Experiences"| C["Product/Service"]
B -->|"Delivers"| C
C -->|"Meets/Exceeds"| A
A -->|"Feedback"| BReal-World Example: Kathmandu Traffic (Nepal’s Worst Nightmare)
- Customer (You): Expects smooth travel (like Singapore’s MRT).
- Company (KTM Municipality): Delivers chaotic roads + no traffic lights.
- Product/Service (Roads): Poor maintenance → Dissatisfaction → People use Pathao instead.
Fix Attempted by KTM Metro:
- Expectation: Fast, reliable metro.
- Performance: Delays + overcrowding → CSAT: 2.5/5.
7. Costs of Poor Satisfaction
| Cost Type | Direct Impact | Indirect Impact | Nepali Example |
|---|---|---|---|
| Churn | Losing customers to competitors | Higher acquisition costs | NTC loses 20% customers to Ncell yearly |
| Complaints | Customer service overhead | Reputation damage | Daraz’s return complaints: 12% of orders |
| Low Advocacy | No word-of-mouth referrals | Slower growth | Himalayan Java’s NPS: +15 (vs. +30 for Starbucks) |
| Price Sensitivity | Customers become deal-hunters | Lower margins | Khalti users switch to eSewa for discounts |
Worked Example: Nabil Bank’s Complaint Costs
- 2023 Data: 5,000 complaints → Rs. 20M spent on resolution.
- Opportunity Cost: If resolved faster, could have upsold 10,000 new accounts (avg. Rs. 50K per account).
8. CRM Strategies to Improve Satisfaction
A. Proactive Approaches
- Personalization: Nabil Bank’s "MyBank" app shows customized loan offers.
- Anticipatory Service: Daraz’s "Order Tracking" SMS before delivery.
- Feedback Loops: Pathao’s post-ride survey (but only 5% respond—improve this!).
B. Reactive Approaches
- Complaint Resolution: NTC’s "Escalation Team" (but avg. resolution time: 7 days).
- Compensation: Khalti’s "Refund Guarantee" for failed transactions.
In the Real World
Nabil Bank’s "Sathi" Program
- Idea Used: Customer Life Cycle + Satisfaction Tracking
- How? Tracks account activity, complaint history, and loan repayments to predict churn.
- Result: Reduced attrition by 18% in 2023.
Daraz’s "Easy Return" Policy
- Idea Used: Closing the Expectation-Performance Gap
- How? 7-day returns, no questions asked (vs. Amazon’s 15 days).
- Impact: CSAT improved from 3.2 to 4.1/5 in 2023.
Pathao’s Driver App
- Idea Used: Kano’s Excitement Factors
- How? Added "Surprise Bonus" for high-rated drivers (unexpected delight).
- Outcome: Driver retention up 25%, leading to better service for customers.
Exam Tip
How to Score Full Marks
Define + Explain + Example (DEE) Formula
- Always start with a clear definition, then explain the theory, and end with a Nepali example.
- ❌ "Customer satisfaction is important."
- ✅ "Customer satisfaction is the net result of comparing perceived performance against expectations (Oliver, 1980). In Nepal, NTC’s internet service fails to meet expectations of 50 Mbps stability, leading to a CSAT of 2.8/5 and 20% churn to Ncell."
Use Diagrams in Answers
- Draw the expectation-performance gap when discussing dissatisfaction.
- Show Kano’s model when explaining satisfaction drivers.
Link to CRM
- Every answer must connect to how CRM tools (e.g., Salesforce, HubSpot) can measure or improve satisfaction.
- Example: "Nabil Bank uses Salesforce Service Cloud to track complaint resolution times, reducing average handling time from 7 to 3 days."
Avoid Generic Examples
- Bad: "McDonald’s is good."
- Good: *"Himalayan Java’s loyalty program uses Kano’s excitement factors (free coffee + NEPSE tips) to turn basic needs into delighters, increasing repeat visits by 30%."*
Common Pitfalls
- ❌ "Customer satisfaction is the same as loyalty." → No! Satisfaction is a momentary feeling; loyalty is long-term behavior.
- ❌ Ignoring Nepali context. Always use local examples (NTC, Nabil, Daraz, Pathao).
Sample Exam Answer (15 Marks)
Question: Discuss the triangular relationships in customer satisfaction with examples.
Answer: Customer satisfaction is influenced by a triangular relationship among the customer, company, and product/service, where:
- Customer sets expectations (e.g., Ncell users expect 100 Mbps).
- Company delivers through its products/services (e.g., NTC provides 30 Mbps with drops).
- Product/Service must meet/exceed expectations to satisfy the customer.
Nepali Example: Kathmandu Traffic
- Customer Expectation: Smooth travel like Singapore’s MRT.
- Company (KTM Municipality) Delivery: Chaotic roads, no traffic management.
- Product (Roads) Performance: Poor maintenance → Dissatisfaction → People use Pathao instead. CRM Fix: If KTM used traffic analytics (like Singapore), it could predict congestion and improve satisfaction.
Marking Breakdown:
- Definition (2 marks)
- Diagram (3 marks)
- Nepali example (5 marks)
- CRM link (3 marks)
- Flow of logic (2 marks)
Quick Revision Table
| Concept | Key Idea | Nepali Example | CRM Tool |
|---|---|---|---|
| Expectation-Performance Gap | Satisfaction = Performance – Expectations | NTC’s 30 Mbps vs. expected 50 Mbps | Salesforce Analytics |
| Kano’s Model | Basic → Performance → Excitement needs | Himalayan Java’s free coffee (excitement) | HubSpot Customer Feedback |
| CSAT | Post-interaction satisfaction score | Nabil Bank’s 3.5/5 for chat support | Zendesk |
| NPS | Willingness to recommend | Daraz’s +20 vs. Amazon’s +50 | Qualtrics |
| Complaint Costs | Churn, reputation, recovery costs | NTC’s Rs. 20M spent on complaints | ServiceNow |
Based on the TU BBS syllabus for Customer Relationship Management, unit 3.
Discussion
Loading…