CRM Practices in Nepal & Global Context: Models, Challenges & Success Stories

TAKEAWAYS:

• CRM in Nepal relies heavily on personalized service (e.g., Nabil Bank’s relationship managers) and low-tech solutions (e.g., Daraz’s call-center-based loyalty programs) due to infrastructure limitations.
• Global CRM leverages AI-driven personalization (e.g., Netflix’s recommendation engine) and data analytics (e.g., Amazon’s dynamic pricing) for scalability.
• Key challenges in Nepal: High customer churn (e.g., mobile operators like Ncell), low digital literacy, and fragmented supply chains (e.g., eSewa’s payment failures).
• Implementation phases follow a PDCA cycle (Plan-Do-Check-Act) but often skip "Check" due to budget constraints.
• Cultural context matters: High-context communication (e.g., Nepali trust-based relationships) requires face-to-face CRM over digital-only approaches.
• Cost-benefit tradeoff: Nepali SMEs prioritize immediate ROI (e.g., Kathmandu’s loyalty cards) over long-term data-driven CRM.

1. Defining CRM Practices: Nepal vs. Global Context

CRM practices are not one-size-fits-all. They adapt to market maturity, technology access, and customer expectations. Below is a comparison of Nepal’s CRM landscape (relationship-driven, low-tech) vs. global CRM (data-driven, automated).

mindmap
  root((CRM Practices Comparison))
    Nepal
      "Low-tech focus"
      "Relationship over data"
      "Examples: Nabil Bank, Daraz, NTC"
      "Challenges: Power cuts, low internet"
    Global
      "AI/ML-driven"
      "Data analytics"
      "Examples: Amazon, Google, Toyota"
      "Challenges: Privacy laws, scalability"
    Key Differences
      "Personalization depth"
      "Implementation cost"
      "Customer trust factors"

Why the Difference?

2. How CRM Works in Nepal: Case Studies

Nepal’s CRM is human-centric due to limited digital infrastructure and high-context culture. Below are three real-world examples:

Case 1: Nabil Bank’s Relationship Banking

Problem: Low digital adoption among rural customers. Solution: Hybrid CRM (digital + human touch).

• Process:
  1. Branch visits: Relationship managers (RMs) track customer interactions manually.
  2. Loyalty programs: Points for deposits, waived fees for long-term clients.
  3. SMS alerts: Basic transaction notifications (no app-based tracking).
• Why it works:
  • Trust: Face-to-face interactions overcome digital skepticism.
  • Low cost: No need for expensive CRM software.
• Limitation: No predictive analytics → misses cross-selling opportunities.

flowchart TD
  A["Customer Visits Branch"] --> B["RM Records Interaction\n(Paper/Digital Hybrid)"]
  B --> C["Loyalty Points Added\n(Manual Entry)"]
  C --> D["SMS Alert Sent\n(Basic Transactional)"]
  D --> E["Next Visit Triggered\n(No AI Prediction)"]

Worked Example: A farmer deposits Rs. 50,000 in Nabil Bank. The RM notes:

• Occupation: Farmer
• Loan history: None
• Behavior: Visits branch monthly Action: RM offers a low-interest agricultural loan (based on trust, not data). Outcome: Farmer takes loan, bank earns Rs. 20,000/year in interest.

Case 2: Daraz’s "Daraz Plus" Loyalty Program

Problem: High cart abandonment (70% of users don’t complete orders). Solution: Tiered loyalty program (like Amazon Prime but simpler).

• How it works:
  • Tier 1 (Bronze): Free shipping after 3 orders.
  • Tier 2 (Silver): 10% discount on birthdays.
  • Tier 3 (Gold): Early access to sales.
• Tech used:
  • Manual entry (no automated data warehouse).
  • SMS/email (no app push notifications).
• Challenge: Fraud risk (fake accounts for discounts).

Case 3: NTC’s Customer Complaint System

Problem: Low customer satisfaction due to unresolved complaints. Solution: Multi-channel CRM (phone, email, in-person).

• Process:
  1. Customer calls 1660 or visits a center.
  2. Complaint logged in Excel sheet (no CRM software).
  3. Follow-up via SMS (e.g., "Your complaint #1234 is being processed").
• Limitation: No integration with billing or service records.

sequenceDiagram
  participant C as Customer
  participant A as NTC Agent
  participant D as Database (Excel)
  C->>A: Calls 1660: "My bill is wrong!"
  A->>D: Logs complaint #1234 (Manual)
  D-->>A: Returns ticket number
  A->>C: SMS: "Complaint #1234 logged. ETA: 7 days."
  loop Follow-up
    A->>C: SMS: "Update: Still investigating."
  end

3. Global CRM Practices: Lessons from Giants

Global companies use data-driven, automated CRM to scale. Below are three models:

Model 1: Amazon’s "Anticipatory Shipping"

• How it works:
  1. Data sources: Purchase history, browsing behavior, location.
  2. AI prediction: "You’ll need this by Friday" → ships before order.
  3. Result: 35% faster delivery for Prime users.
• Key tech: Machine learning (not manual tracking).

Model 2: Google’s "Customer Insights Hub"

• Use case: YouTube recommendations.
• Process:
  1. Data collected: Watch history, search terms, device type.
  2. Segmentation: Groups users by interests (e.g., "Nepali music lovers").
  3. Personalization: Shows Nepali music videos first to that segment.
• Outcome: 60% higher watch time for personalized content.

Model 3: Toyota’s "Total Customer Satisfaction" (TCS)

• Approach: Post-purchase feedback loops.
• Steps:
  1. Survey: Sent 30 days after purchase.
  2. NPS (Net Promoter Score): "On a scale of 0-10, how likely are you to recommend?"
  3. Action:
     • Detractors (0-6): Call center follow-up.
     • Passives (7-8): Discount on next service.
     • Promoters (9-10): Invited to Toyota events.

pie
  title Toyota NPS Distribution
  "Detractors (20%)" : 20
  "Passives (30%)" : 30
  "Promoters (50%)" : 50

4. Challenges of CRM Implementation in Nepal

Despite success stories, Nepal faces unique hurdles:

A. Technological Barriers

B. Cultural and Behavioral Issues

• High-context communication: Nepalis prefer face-to-face over digital CRM.
  • Example: A customer at Kathmandu Supermarket asks for a discount. The cashier knows their name (from manual records) and gives a 10% off—no need for a loyalty app.
• Distrust of digital: Many Nepalis don’t trust online payments (e.g., eSewa failures).

C. Organizational Resistance

• Silos: Sales, marketing, and service teams don’t share data.
  • Example: Ncell knows a customer complains about signal, but prepaid sales don’t get this info.
• Lack of training: Employees don’t know how to use CRM tools.

5. Step-by-Step CRM Implementation Framework for Nepal

Nepalese firms should follow a modified PDCA cycle (Plan-Do-Check-Act) with local adaptations:

flowchart TD
  A["Plan\n- Assess needs\n- Set budget (Rs. 50K-200K)\n- Choose low-cost CRM (e.g., Zoho, HubSpot free tier)"]
  B["Do\n- Pilot with 10% of customers\n- Train staff on manual + digital hybrid"]
  C["Check\n- Measure: Repeat visits, complaint resolution time\n- *Skip if budget is tight*"]
  D["Act\n- Scale up if successful\n- Integrate with accounting (e.g., Tally)"]
  A --> B --> C --> D

Key Considerations for Nepal:

1. Start small: Pilot in one branch (e.g., Nabil Bank’s Lalitpur branch).
2. Hybrid approach: Use Excel + basic CRM (e.g., Zoho CRM).
3. Focus on high-touch: Prioritize loyalty programs over automation.
4. Localize: Offer SMS-based CRM (not app-only).
5. Measure manually: Track repeat visits (not CLV).

6. Exam Tip: How to Score Full Marks

This unit is heavily tested on:

1. Comparisons (Nepal vs. global CRM).
2. Case studies (Nabil Bank, Daraz, NTC).
3. Challenges (tech, cultural, organizational).
4. Implementation steps (PDCA with local adaptations).

How to Structure Your Answer (30 Marks):

Common Mistakes to Avoid:

• Generic answers: Don’t write about "CRM in general"—focus on Nepal.
• Ignoring challenges: Examiners expect power outages, low digital skills, etc.
• No examples: Always name real companies (Nabil Bank, Daraz, NTC).
• Overcomplicating: Stick to simple models (e.g., loyalty tiers, not complex ML).

7. Real-World Deep Dive: How Pathao Uses CRM

Company: Pathao (ride-hailing app in Nepal). CRM Strategy: Driver-Customer Matching + Loyalty. How it works:

1. Data collected:
   • Customer: Pickup/drop locations, payment history.
   • Driver: Response time, ratings.
2. Personalization:
   • Frequent customers get priority booking.
   • Low-rated drivers are reassigned.
3. Tech used:
   • Basic CRM: Tracks rides but no predictive analytics.
   • SMS alerts: "Your driver is 2 mins away."
4. Challenge:
   • Driver churn: 30% quit due to low earnings.
   • Solution: Referral bonuses (e.g., "Invite 3 friends, get Rs. 500").

Why it’s a good example for exams:

• Shows hybrid CRM (digital + human touch).
• Highlights Nepal-specific challenges (driver management).
• Uses simple loyalty mechanics (easy to explain).

classDiagram
  class Customer {
    +pickupLocation
    +paymentHistory
    +loyaltyPoints
  }
  class Driver {
    +responseTime
    +ratings
    +earnings
  }
  class PathaoCRM {
    +matchCustomerDriver()
    +sendSMSAlert()
    +updateLoyalty()
  }
  Customer "1" --> "many" PathaoCRM : uses
  Driver "1" --> "many" PathaoCRM : managed by