MGF5690 Chap.5 Service Quality and Recovery
Service Quality and Recovery
Service quality is judged through the gap between what customers expect and what they perceive. SERVQUAL organises those judgements around reliability, assurance, tangibles, empathy and responsiveness, while the gaps model traces poor outcomes back through listening, design, delivery and communication. Measurement should identify causes rather than merely produce a score.
Prevention reduces failure demand, and recovery combines acknowledgement, fair remedy, speed, ownership and learning so that a single incident improves the wider operating system.
What this chapter covers
- 01
Reliability, assurance, tangibles, empathy and responsiveness
- 02
Customer gap and provider-side diagnostic gaps
- 03
Outcome, process and perception measures
- 04
Prevention, appraisal and failure costs
- 05
Continuous improvement and root-cause learning
- 06
Recovery ownership, remedy and follow-through
Worked example · free
Diagnose repeated missed appointments
- +2Separate the customer gap from possible listening, design, delivery and communication causes.
- +2Test scheduling rules, technician capacity and promise wording against complaint and arrival data.
- +2Give one owner authority to notify, rebook and remedy, then feed the cause into planning.
Key terms
- Customer gap
- The difference between expected service and the service the customer perceives.
- Reliability
- The ability to perform the promised service dependably and accurately.
- Failure demand
- Extra demand created because the service did not work correctly for the customer.
Service Quality and Recovery FAQ
Why is a satisfaction score insufficient on its own?
A score reports an outcome but may not identify whether the cause was a poor promise, process design, employee execution or customer communication. Diagnosis needs operational and qualitative evidence alongside the rating.
Does generous compensation guarantee good recovery?
No. Customers also judge speed, explanation, dignity, procedural fairness and whether anyone owns the case. A large remedy can still frustrate when the process is confusing or the failure repeats.
How should improvement priorities be selected?
Combine customer importance, frequency, consequence and preventability. Start with failures that matter to customers and reveal a recurring system cause, then assign an owner and monitor both quality and unintended trade-offs.
Assessment move
Practise moving in both directions through the gaps model: from a customer symptom to plausible provider causes, and from an operating change to the customer perception it should improve. Memorise SERVQUAL as a diagnostic vocabulary, not a checklist that replaces evidence. For every case, distinguish immediate containment, customer recovery and permanent prevention.
State which measure would reveal progress and pair it with a balancing measure so that speed, cost or standardisation does not hide declining reliability, fairness or employee capacity. Create a quality evidence table with four columns: customer statement, relevant dimension, possible provider gap and evidence needed.
A complaint that support is slow may indicate responsiveness, but the cause could be weak listening, unrealistic standards, inadequate delivery capacity or a promise that overstates availability. Keep several explanations open until process and customer evidence discriminate among them. Use SERVQUAL dimensions to describe what the customer judges, not to label the root cause automatically.
Reliability concerns dependable promise fulfilment; responsiveness concerns willingness and speed; assurance concerns confidence; empathy concerns individual understanding; tangibles concern physical or visible cues. One incident can affect several dimensions, so decide which is central to the argument. Follow the gaps model upstream.
Ask whether the organisation understood expectations, converted that understanding into workable standards, delivered to those standards and communicated a promise consistent with delivery. Recommendations should repair the evidenced gap. More training will not solve a schedule that structurally exceeds capacity, and a new survey will not solve a known design fault. Separate three time horizons when evaluating failure.
Containment protects the immediate situation, recovery restores the affected customer, and prevention changes the process. State who owns each horizon and what information must travel from the recovery case into improvement work. A sincere apology without learning can create recurring failure demand. Quality cost analysis helps defend prevention.
Identify resources spent preventing defects, checking work, correcting failures before delivery and responding after the customer is affected. Avoid assuming that less appraisal is automatically efficient; monitoring may be necessary while a redesigned process stabilises. Use the categories to expose where the organisation currently pays. For recovery, evaluate outcome, procedure and interaction.
Customers may judge the remedy, the ease and speed of obtaining it, the explanation and dignity of treatment. Choose a remedy proportionate to harm and state how repeat or severe cases escalate. A recovery paradox should never be treated as permission to fail. In assessment writing, triangulate ratings, complaint themes and operational measures because each reveals a different part of quality.
Track reliability, repeat contact, recovery time, customer effort and recurrence. Conclude with a learning review that asks whether the apparent improvement reflects prevention or merely quieter complaints. A balanced answer protects customer voice while testing the operating mechanism behind it.
Working through Service Quality and Recovery in MGF5690? Sia is AskSia’s AI Management tutor — ask any MGF5690 Service Quality and Recovery question and get a clear, step-by-step explanation grounded in how MGF5690 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
