L31: Firm Response to Customers

Good morning, everyone. Welcome back to MGA-301. Last lecture we covered service guarantee design. Today, Lecture 31, we explore Firm Response to Customers — the systematic management of all the ways a service firm interacts with customers when those customers reach out. [0–10 minutes: Introduction] Think about the last time you tried to reach a service company. Maybe you needed to dispute a credit card charge, check on a delivery, or make a special request for an upcoming hotel stay. What happened? Did the company make it easy to reach them? Were you kept on hold for twenty minutes? Did the automated system understand your problem, or did it loop you through the same menu options repeatedly? Did the human agent, when you finally reached one, actually resolve your issue, or did they pass you to someone else? The way a service firm responds to customers when they reach out is a critical moment of truth. And it is the moment that matters most — because the customer is reaching out precisely when they have a need or a problem. How the firm handles that moment will determine whether the customer relationship deepens or erodes. [10–40 minutes: Core Content] Five types of customer contact that service firms must manage. Type 1: Informational contacts. The customer wants information — what are your hours? What is the price? What is the status of my order? These are relatively straightforward but create enormous contact volume for many service firms. Type 2: Transaction contacts. The customer wants to initiate or complete a transaction — book an appointment, make a reservation, process a claim. These require both efficiency and accuracy. Type 3: Complaint contacts. The customer is dissatisfied and wants resolution. We covered the recovery framework in Lecture 22. These contacts require empathy, empowerment, and speed. Well-handled, they can convert a dissatisfied customer into a loyal advocate. Poorly handled, they cause churning and negative word-of-mouth. Type 4: Feedback contacts. The customer wants to share a suggestion, a compliment, or a general comment. These are valuable inputs for service improvement and should be captured systematically. Type 5: Special request contacts. The customer has a specific, personalised need — a dietary restriction, an accessibility requirement, a timing constraint. Handling special requests with grace is one of the most powerful loyalty builders in services. The channels through which these contacts are managed have proliferated dramatically. Today's service firms must manage customer contact across: telephone, email, live chat, chatbots and AI assistants, social media direct messages and comments, mobile app messaging, in-person service encounters, and self-service portals. Managing all these channels consistently — omnichannel customer service — is the gold standard, but it is extremely difficult to achieve because it requires data integration across all channels. The current state of firm response in Indian services through examples. IRCTC's customer response has historically been one of the most criticised in Indian service industries. Until relatively recently, reaching IRCTC customer service required calling a chronically overloaded phone line or submitting a complaint on a web portal that could take weeks to receive a response. The problem was both infrastructure (insufficient capacity) and process (no clear escalation pathway for most issue types). IRCTC has improved significantly with the introduction of its mobile app, chat function, and social media response team — but transformation is ongoing. Zomato's customer response system is one of the best in Indian services. When a customer reports an issue through the app — wrong order, missing item, poor quality — the system automatically identifies the nature of the complaint, routes it to the appropriate resolution action, and provides real-time updates. For most common issues, resolution happens within two to five minutes through automated flows. Human agents are reserved for complex cases. HDFC Bank's customer response system represents best practice in financial services. The bank offers multiple contact channels — branch, phone banking with short wait times, net banking secure messaging, mobile app chat, and social media response. Their social media team — particularly on Twitter — is notable for response speed and actually resolving issues publicly, which creates confidence in prospective customers watching the interaction. The Service Recovery Information System — a specific subset of the firm response function — does three things. First, it captures all customer contacts and complaint data in a searchable database. Second, it analyses the data for patterns — what issues are most common? Which products, which locations, which processes generate the most complaints? Third, it routes that analysis to the appropriate managers for corrective action. The analysis function is critical and often neglected. A bank that receives two hundred complaints per day about ATM card blocking procedures is being told clearly that its blocking and unblocking process is broken. If nobody is aggregating those complaints and reporting the pattern to the relevant process owner, the bank will continue to receive the same two hundred complaints per day indefinitely. Service Level Agreements — SLAs — are defined commitments for how quickly and how well a firm will respond to different types of customer contacts. A typical SLA might be: informational email queries answered within twenty-four hours; complaints escalated to a resolution team within one hour; regulatory complaints responded to within forty-eight hours. SLAs create accountability and allow measurement of response quality. An important principle from Lovelock: responses must match customer expectations, not just internal efficiency targets. A customer with an urgent health insurance claim query has very different expectations for response time than a customer with a general information query. Service firms should calibrate their SLAs to customer urgency and importance. [40–55 minutes: Activity and Discussion] Role-play and analysis exercise. Three volunteers. Volunteer 1 is a customer calling State Bank of India's customer care line to dispute an unauthorised charge of three thousand rupees on their account. Volunteer 2 is the first-level customer service agent. Volunteer 3 is the senior resolution officer. We will run the interaction for three minutes and then critique: Was the initial response empathetic? Was the routing appropriate? Was the resolution proportionate? Was the customer given a clear next step? [Run role-play. Debrief as a class. Focus on the procedural justice dimension — did the customer feel the process was fair and accessible?] Discussion question: As AI chatbots become more sophisticated, many service firms are replacing human agents with AI for an increasing range of customer contacts. What are the benefits and the risks of this shift? Are there types of customer contacts that should always involve a human? What determines that threshold? [The answer involves the emotional complexity of the contact and the value of the customer relationship. Complaint handling for high-value customers, and any contact involving significant distress, should involve a human.] [55–60 minutes: Summary and Assignment] Today we covered five types of customer contact — informational, transactional, complaint, feedback, and special request — and the omnichannel challenge of managing them consistently. We examined the Service Recovery Information System, Service Level Agreements, and the balance between technology automation and human empathy in firm response. Examples from IRCTC, Zomato, and HDFC Bank illustrated the range of current practice in India. Assignment: Conduct a firm response audit of any one service firm. Contact them through at least two different channels — phone, email, chat, or social media — with the same inquiry, and compare the response quality, speed, and consistency. Write a 300-word comparative evaluation. Next lecture — Lecture 32 — is our Unit III Review and CRM Case session. We will consolidate the CRM unit and work through a comprehensive CRM case study. See you then. Thank you.