Customer Perception, Expectations & Satisfaction: Models, Gaps & Strategies

TAKEAWAYS:

• Customer perception is shaped by pre-purchase cues (ads, word-of-mouth) and post-purchase experiences (service delivery), but confirmation bias distorts reality.
• Expectations are set by zone of tolerance (desired vs. adequate service) and personal needs (e.g., a Daraz user expects 24h delivery but accepts 48h as "adequate").
• The 5 gaps model (knowledge, standards, delivery, communication, perceived) explains why NTC’s customer complaints spike after service failures.
• Satisfaction = Performance – Expectations, but dissatisfaction (e.g., Pathao’s late pickups) spreads 2.5x faster than praise.
• Recovery paradox turns complaints into loyalty if handled well (e.g., Khalti’s instant refunds after failed transactions).
• Net Promoter Score (NPS) predicts growth: Nabil Bank’s NPS of 42 (2023) correlates with 12% loan approval uptick.

1. Customer Perception: How Customers "See" Services

Perception is subjective—it’s not what you do, but what customers interpret. For services, perception is influenced by 5 key factors:

mindmap
  root((Customer Perception))
    Factors
      Pre-Purchase
        Ads & Promotions
        Word-of-Mouth (e.g., "My friend got a Khalti refund in 10 mins!")
        Past Experiences (e.g., "NTC’s last outage lasted 3 days")
      During Service
        Employee Behavior (e.g., **Daraz delivery agent’s attitude**)
        Physical Evidence (e.g., **cleanliness of a hospital waiting room**)
      Post-Purchase
        Follow-Up (e.g., **eSewa’s SMS confirmation**)
        Complaint Handling (e.g., **Ncell’s 24/7 helpline**)
    Biases
      Confirmation Bias ("I *knew* Pathao would be late!")
      Selective Perception ("I only remember the slow checkout at Himalayan Java")
      Halo Effect ("Great app design = great service")

Worked Example: NTC’s Power Outage Perception

• Scenario: A blackout hits Thapathali during peak hours.
• Perception Gaps:
  • Customer’s view: "NTC is unreliable; they never fix issues fast."
  • Reality: "The outage was due to a tree fall, and repairs took 4 hours."
• Why? NTC’s lack of real-time updates amplifies frustration. Solution: Use WhatsApp alerts (like Khalti’s transaction status) to close the communication gap.

2. Customer Expectations: The "Zone of Tolerance"

Expectations are not static—they vary by:

• Desired Service (what customers hope for)
• Adequate Service (what they accept)
• Zone of Tolerance (the range between the two)

graph LR
  A["Desired Service"] -->|"High"| B["Zone of Tolerance"]
  B -->|"Moderate"| C["Adequate Service"]
  D["Actual Service"] -->|"Above Zone"| E["Delight"]
  D -->|"Within Zone"| F["Satisfaction"]
  D -->|"Below Zone"| G["Dissatisfaction"]

TABLE: Expectations in Nepali Services

Real-World Tie-In: Daraz’s Delivery Expectations

• Desired: Same-day delivery (like Amazon Prime).
• Adequate: 2-day delivery (Daraz’s standard).
• Zone of Tolerance: 3-day max (otherwise, discounts or refunds).
• Strategy: Daraz uses predictive analytics to set dynamic expectations (e.g., "Delivery by 6 PM" if weather is clear).

3. The Expectations-Performance Gap Model

Satisfaction = Performance – Expectations. If performance > expectations → Delight. If performance = expectations → Satisfaction. If performance < expectations → Dissatisfaction.

flowchart TD
  A["Customer Expectations"] --> B["Service Performance"]
  B --> C{"Performance > Expectations?"}
  C -->|"Yes"| D["Delight"]
  C -->|"No"| E{"Performance = Expectations?"}
  E -->|"Yes"| F["Satisfaction"]
  E -->|"No"| G["Dissatisfaction"]
  G --> H["Complaint / Churn"]

Case Study: Himalayan Java’s Coffee Experience

• Expectation: "Fast, friendly service in 5 mins."
• Performance:
  • Branch A (Lalitpur): Barista took 10 mins → Dissatisfaction.
  • Branch B (Kathmandu): Pre-order via app → Delight (met expectation).
• Solution: Train staff on speed-of-service (like Starbucks’ barista training).

4. The 5 Gaps Model: Why Services Fail

Most service failures stem from 5 gaps between what customers want and what they get:

mindmap
  root((5 Gaps Model))
    Gap 1: Knowledge Gap
      "Management doesn’t know what customers want"
      Example: **NTC assumes customers don’t care about outage alerts**
    Gap 2: Standards Gap
      "Poor service standards set internally"
      Example: **Daraz’s delivery agents not trained on polite behavior**
    Gap 3: Delivery Gap
      "Failure to meet standards"
      Example: **Khalti’s app crashes during peak hours**
    Gap 4: Communication Gap
      "Overpromising or misleading ads"
      Example: **eSewa ads say "Instant refund" but takes 24h**
    Gap 5: Perceived Gap
      "Customer’s perception ≠ reality"
      Example: **Ncell users think 4G is slow, but it’s actually 5G**

Worked Example: NTC’s Customer Complaints

• Gap 1: NTC surveys show customers want real-time outage maps (but they ignore this).
• Gap 3: Technicians take 6 hours to fix a pole, exceeding the 2-hour SLA.
• Gap 4: Ads say "Reliable 24/7 service" but downtime is 8h/year.
• Solution: Implement Gap 1 fix (customer feedback loops) + Gap 3 fix (faster repair teams).

5. Measuring Satisfaction: NPS, CSAT, and Recovery Paradox

Recovery Paradox: Turning Complaints into Loyalty

• Example: Khalti’s instant refund policy.
  • Scenario: User’s transaction fails.
  • Action: Khalti auto-refunds + 10% bonus within 1 hour.
  • Outcome: 85% of complainants become repeat users.

6. Strategies to Manage Perceptions and Expectations

Case Study: Nabil Bank’s Digital Transformation

• Problem: Low NPS (38 in 2020) due to slow loan processing.
• Solution:
  1. Reduced Gap 1: Conducted customer journey mapping (found 30% drop-off at loan approval).
  2. Reduced Gap 3: Introduced AI-driven loan approval (now 24-hour turnaround).
  3. Closed Gap 4: Stopped misleading ads (e.g., "Instant loans" → now "24-hour processing").
• Result: NPS jumped to 42 (2023) + 12% increase in loan approvals.

In the Real World

1. eSewa’s Service Recovery

   • Idea Used: Recovery Paradox + Gap 5 (Perceived Gap)
   • How? When a payment fails, eSewa auto-sends a refund + 10% bonus within 1 hour. 85% of users who complained became repeat customers.
   • Why It Works: Closes the perceived gap between "failed transaction" and "resolved issue."

2. Pathao’s Dynamic Pricing & Expectations

   • Idea Used: Zone of Tolerance + Gap 3 (Delivery Gap)
   • How? Pathao adjusts pickup times based on traffic (e.g., "10–15 mins" vs. "5–10 mins"). If late, they offer a discount or refund.
   • Real Example: During monsoon season, Pathao increases surge pricing but also extends the tolerance window (from 15 mins to 20 mins).

3. Nabil Bank’s NPS-Driven Growth

   • Idea Used: Net Promoter Score (NPS) + Gap 1 (Knowledge Gap)
   • How? Nabil Bank surveys customers monthly and links NPS to employee bonuses. In 2023, their NPS of 42 correlated with a 12% increase in loan approvals.
   • Key Insight: Happy customers = more business.

Exam Tip

1. For short-answer questions (e.g., "Factors influencing customer expectations"):

   • Use the 5 gaps model or zone of tolerance as frameworks.
   • Example Answer:

     *"Customer expectations are shaped by (1) past experiences, (2) word-of-mouth, (3) personal needs, (4) advertising promises, and (5) service recovery efforts. For example, a Pathao user’s expectation of a 10-minute pickup is set by ads (Gap 4) and past delays (Gap 3)."*

2. For case studies (e.g., "Sparkle Fitness Club"):

   • Step 1: Identify the gap (e.g., Gap 3: Delivery Gap if members complain about slow service).
   • Step 2: Suggest solutions (e.g., train staff on speed, introduce pre-booking).
   • Step 3: Link to real-world examples (e.g., "Like Himalayan Java’s pre-order system").

3. For numerical questions (e.g., "Calculate satisfaction score"):

   • Use the formula: Satisfaction Score = (Performance Rating – Expected Rating) × 100
   • Example:

     *"If a customer expects NTC’s outage time to be ≤2h but experiences 4h, their satisfaction score is (2–4) × 100 = –200 (Dissatisfaction)."*

4. Avoid common mistakes:

   • ❌ Saying "satisfaction = performance" (forget expectations).
   • ❌ Ignoring Gap 5 (Perceived Gap) in case studies.
   • ❌ Using theory without examples (always tie to eSewa, NTC, or Daraz).

Final Visual Summary

flowchart LR
  A["Customer Expectations"] --> B["Service Performance"]
  B --> C{"Performance > Expectations?"}
  C -->|"Yes"| D["Delight<br/>(NPS: +50)"]
  C -->|"No"| E{"Performance = Expectations?"}
  E -->|"Yes"| F["Satisfaction<br/>(NPS: 0)"]
  E -->|"No"| G["Dissatisfaction<br/>(NPS: -50)<br/>Complaint"]
  G --> H["Recovery Paradox<br/>(If handled well → Loyalty)"]
  H --> D
  A --> I["Gap 1: Knowledge"]
  A --> J["Gap 2: Standards"]
  B --> K["Gap 3: Delivery"]
  A --> L["Gap 4: Communication"]
  B --> M["Gap 5: Perceived"]