Sales, Service and Complaint Management

Introduction and Context

Customer relationship management (CRM) becomes strategically meaningful when it shapes what an organisation does before, during and after a sale. Sales create the relationship; service sustains it; complaint management tests whether the organisation can learn and recover when the relationship is damaged. These activities should not be treated as separate departments. A customer experiences one organisation, even when the organisation divides responsibility among sales representatives, account managers, contact-centre agents, technicians, digital channels and complaint specialists.

For brand-oriented organisations, this integration is especially important. Every sales promise creates a service expectation. Every service interaction communicates the brand’s values. Every complaint reveals a gap between the customer’s expected and experienced relationship. CRM therefore links commercial performance with customer experience, operational information and organisational learning.

This chapter examines how CRM supports sales pipelines, account management, service operations, contact centres, self-service, complaints, service recovery and closed-loop feedback. The emphasis is application: students should be able to translate CRM concepts into process designs, performance measures and managerial decisions.

Learning Objectives

By the end of this chapter, you should be able to:

1. Explain how CRM supports sales pipelines and account development.
2. Distinguish transactional selling, consultative selling and strategic account management.
3. Design principles for CRM-enabled service operations and contact centres.
4. Evaluate self-service and omnichannel service journeys.
5. Analyse complaint causes and design appropriate service recovery.
6. Apply closed-loop customer feedback processes and relevant performance metrics.
7. Identify ethical, legal, technological and managerial risks in sales and service CRM.

1. CRM in the Customer Relationship Lifecycle

A CRM system is not merely a database or software package. It is an organisational capability that combines customer information, processes, employee practices, technologies and performance management. In sales and service, this capability should answer five practical questions:

• Who is the customer and what is known about the relationship?
• What need, opportunity or problem is currently being addressed?
• Which employee or channel owns the next action?
• What outcome did the interaction produce?
• How will the organisation learn from the interaction?

A useful lifecycle is:

Prospect identification → qualification → opportunity development → sale and onboarding → service delivery → retention and expansion → feedback and learning

The lifecycle is not necessarily linear. Customers may enter through service, become sales opportunities, complain before renewal, or use self-service without speaking to an employee. CRM must therefore support continuity across journeys rather than impose a rigid sequence.

Relationship value and brand promise

Sales activity creates revenue, but effective CRM considers the longer-term value and risk of the relationship. A low-margin customer may be strategically important because of referrals, future potential or influence in a business network. Conversely, a high-revenue account may be costly to serve or expose the organisation to ethical and reputational risk.

A brand promise is operationally credible only when the organisation can deliver it consistently. A brand positioned around simplicity, for example, should offer clear contracts, accessible support and low-effort complaint resolution. Misalignment between sales claims and operational capability is a major source of dissatisfaction.

2. CRM-Enabled Sales Management

2.1 The sales pipeline

A sales pipeline represents the stages through which a qualified opportunity progresses. Typical stages include:

1. Lead or enquiry: a person or organisation has shown possible interest.
2. Qualification: need, authority, timing, budget and fit are assessed.
3. Discovery: the salesperson investigates the customer’s situation and desired outcomes.
4. Proposal: a solution, value proposition and commercial terms are presented.
5. Negotiation or evaluation: objections, risks and alternatives are considered.
6. Commitment: the customer accepts, signs or authorises the purchase.
7. Onboarding: the customer is transferred into delivery and relationship management.

CRM supports the pipeline by recording contacts, interactions, needs, decision makers, probability, expected value, next actions and reasons for loss. The purpose is not to generate administrative records for their own sake. The purpose is to improve prioritisation, coordination, forecasting and customer continuity.

A pipeline becomes unreliable when stages are defined by salesperson opinion rather than observable customer evidence. For example, an opportunity should not be labelled “proposal” merely because a salesperson intends to send one. A stronger definition is that the customer has confirmed a need, decision process and evaluation criteria, and a documented proposal has been delivered.

2.2 Lead qualification and prioritisation

Qualification should be evidence-based and proportionate. Common criteria include strategic fit, customer need, urgency, authority, financial viability, serviceability and ethical risk. Automated scoring can assist prioritisation, but it should not replace professional judgement. A score may reflect digital activity rather than genuine purchase intent, and historical data may reproduce discriminatory patterns.

A practical qualification record should contain:

• the customer’s stated problem or objective;
• the consequences of leaving the problem unresolved;
• relevant stakeholders and decision rights;
• expected timing and procurement process;
• proposed value and likely implementation requirements;
• legal, privacy, credit and reputational considerations;
• the agreed next step and responsible owner.

2.3 Forecasting and pipeline discipline

Managers often estimate expected pipeline value using:

where E is expected pipeline value, Vᵢ is the monetary value of opportunity i, and pᵢ is the estimated probability that opportunity i will close. Probabilities must be between 0 and 1, and values must use the same currency and time basis. The calculation is an expectation, not a guaranteed forecast. It assumes that the probabilities are meaningful and that opportunities are not treated as independent evidence when they are strongly correlated.

Worked example. A salesperson has three opportunities: £20,000 at a 0.30 probability, £50,000 at 0.50, and £10,000 at 0.80.

The expected value is £39,000. This does not mean that exactly £39,000 will be realised. It is useful for comparing portfolios, identifying gaps and testing scenarios. Managers should also inspect pipeline age, stage conversion, deal concentration, sales-cycle length and the quality of next actions.

2.4 Consultative selling and value creation

Transactional selling focuses on product availability, price and immediate purchase. Consultative selling begins with the customer’s situation and links the proposed solution to measurable outcomes. In CRM, this requires recording customer objectives rather than only product codes and quotation values.

The salesperson’s role includes problem diagnosis, expectation management and coordination with service or technical teams. An opportunity should not be won by promising delivery capabilities that operations cannot provide. Incentive systems that reward only bookings may encourage over-selling, poor qualification and avoidable complaints. Balanced measures should include retention, implementation quality, customer outcomes and compliance.

3. Account Management and Customer Development

Account management concerns the continuing governance of an organisational relationship after, and often during, the initial sale. It is especially important in business-to-business markets, subscriptions, professional services and complex consumer relationships.

Account planning

An account plan may include:

• customer strategy and business context;
• current products, services and usage;
• stakeholder map and relationship strength;
• customer goals, risks and upcoming events;
• value delivered and unresolved issues;
• renewal, cross-sell or expansion opportunities;
• service commitments and escalation routes;
• actions, owners, dates and success measures.

Good account management is not indiscriminate cross-selling. Expansion is appropriate when it improves customer outcomes and fits the customer’s needs. CRM data should support “next best action,” but recommendations must be explainable, relevant and easy for employees to challenge.

Customer lifetime value as a decision aid

A simplified contribution-based customer lifetime value model is:

where mₜ is expected contribution margin in period t, rₜ is the probability of retaining the customer into period t, d is the discount rate per period, and AC is acquisition and attributable onboarding cost. The model is applicable when periods, margins, retention probabilities and costs are estimated consistently. It should not be interpreted as an exact personal valuation of a customer. It is a planning estimate affected by assumptions, uncertainty and allocation choices.

Managers should use CLV alongside fairness, strategic fit, service feasibility and customer welfare. A high predicted value does not justify neglecting lower-value customers or delivering unequal access to essential services.

4. Service Operations and Contact Centres

4.1 Designing service around customer journeys

Service operations convert a brand promise into repeated encounters. Design begins by mapping the customer journey: the customer’s goal, stages, touchpoints, emotions, effort, information needs, failure points and desired outcome. The organisation’s internal process should then be mapped behind the journey. This exposes handoff failures that are invisible when departments optimise separately.

Important design principles include:

• Reliability: deliver the promised service accurately and consistently.
• Responsiveness: reduce unnecessary waiting and act promptly when recovery is needed.
• Competence: provide the knowledge and authority needed to solve the issue.
• Empathy: recognise the customer’s circumstances without using scripted sympathy alone.
• Accessibility: provide usable channels for customers with different abilities, languages and connectivity.
• Transparency: explain status, constraints, charges and next steps.
• Ownership: ensure that someone remains responsible until the agreed outcome is achieved.

4.2 Contact-centre CRM

A contact centre may combine telephone, email, chat, social messaging, video, messaging applications and back-office work. CRM should provide a unified interaction history, customer authentication, knowledge articles, case status, routing rules, service-level commitments and escalation information.

A good interaction record is concise but sufficient. It should capture the issue, diagnosis, action, commitment, customer preference, risk indicators and unresolved work. Requiring agents to enter excessive fields can reduce attention to the customer and create low-quality data.

Contact-centre performance should be balanced. Common measures include:

• first-contact resolution;
• customer effort or satisfaction;
• average speed of answer and abandonment rate;
• response and resolution time;
• repeat contact rate;
• quality and compliance scores;
• employee occupancy, wellbeing and turnover;
• complaint recurrence and root-cause closure.

No single metric is a complete measure of service. For example, reducing average handling time may increase repeat contacts if agents end conversations prematurely. Similarly, high first-contact resolution may be misleading if complex cases are improperly closed.

4.3 Service-level measures

A service-level agreement should define the service, measurement method, exclusions, responsibilities, remedies and review process. “Respond within four hours” must specify whether response means an automated acknowledgement, a human investigation or a substantive resolution. Clear definitions prevent apparent performance that does not reflect customer outcomes.

Operational dashboards should distinguish volume from difficulty. A sudden rise in contacts may indicate successful access to support, a product defect, confusing communication or a marketing campaign. Data requires interpretation rather than automatic blame of agents or customers.

5. Self-Service and Omnichannel Service

Self-service enables customers to find information, complete transactions or resolve problems without direct employee assistance. Examples include knowledge bases, account portals, automated payment, chatbots, diagnostic tools and community forums.

Self-service is effective when the task is suitable, information is accurate, navigation is clear and escalation is easy. It is inappropriate to force self-service for emotionally sensitive, high-risk or highly complex cases. A customer should not have to repeat information after moving from a chatbot to an agent.

Omnichannel principles

Omnichannel service differs from multichannel service. Multichannel means that several channels exist; omnichannel means that the journey remains coherent as the customer moves among them. Core requirements include:

1. a shared or synchronised case identity;
2. consistent policies and information;
3. visibility of prior interactions;
4. channel choice without unfair penalty;
5. clear handoff and escalation;
6. accessibility and privacy controls.

Automation should disclose when a customer is interacting with a system rather than a person. Customers should have a practical route to human assistance, particularly when the issue concerns money, safety, vulnerability, discrimination or repeated failure.

6. Complaint Management

A complaint is an expression of dissatisfaction that expects or implies a response. It is not merely negative sentiment. Complaints can be direct, indirect, formal, public or communicated through an intermediary. Treating complaints as nuisance events destroys valuable information about process failure and customer expectations.

6.1 Complaint-management process

A robust process normally includes:

1. Receive: make complaints easy to submit through accessible channels.
2. Acknowledge: confirm receipt and explain what will happen next.
3. Classify: record issue type, severity, customer impact, vulnerability and regulatory significance.
4. Investigate: establish facts, chronology, responsibility and contributing conditions.
5. Respond: explain the decision, remedy and rationale in plain language.
6. Escalate: provide independent or senior review where appropriate.
7. Close: confirm the agreed outcome and record unresolved concerns.
8. Learn: identify systemic causes, corrective action and verification.

A complaint should not be marked closed merely because an employee has sent a response. Closure requires an appropriate outcome, an auditable record and, where feasible, confirmation that the customer’s substantive issue has been addressed.

6.2 Root-cause analysis

Complaint categories are useful but insufficient. A category such as “billing problem” describes a symptom. Root-cause analysis asks why the problem occurred and why it was not prevented. Techniques include the five-whys method, process mapping, Pareto analysis, fault-tree thinking and review of interaction samples.

Causes may be technical, procedural, informational, human, incentive-related or cultural. A repeated delivery complaint may result from inaccurate inventory data, unrealistic sales promises, poor carrier integration or an incentive that rewards dispatch speed over delivery accuracy.

6.3 Complaint metrics

Useful measures include complaint rate, repeat complaint rate, time to acknowledgement, time to resolution, escalation rate, remedy cost, recurrence rate and post-resolution satisfaction. Rates require a denominator. For example:

The multiplier 1,000 is a reporting convention, not a universal requirement. The denominator must match the population and period being studied. If 240 complaints occur across 60,000 transactions, the complaint rate is:

The rate should be segmented by product, location, channel, customer type and issue. A low complaint rate can mean excellent service, but it can also indicate that customers cannot complain or have abandoned the relationship.

7. Service Recovery

Service recovery is the organisation’s response when service has failed. Effective recovery is not simply compensation. It includes acknowledgement, explanation, correction, prevention and respectful treatment.

A practical recovery sequence is:

• listen without premature defensiveness;
• acknowledge the customer’s experience;
• apologise when the organisation is responsible;
• investigate and explain what is known;
• offer a proportionate remedy;
• restore confidence through a specific commitment;
• prevent recurrence and communicate learning where appropriate.

Remedies may include correction, replacement, refund, credit, expedited service, apology, policy change or practical assistance. Proportionality matters. A small voucher may appear insulting when the customer has suffered serious loss, while a large payment may create inconsistency or reward fraudulent claims.

The idea that a failure can create stronger loyalty than flawless service should be treated cautiously. Recovery can restore trust when the failure is limited, the response is fair and the organisation learns. It cannot reliably compensate for repeated, severe or deceptive failures. Recovery should therefore complement prevention, not substitute for it.

8. Closed-Loop Customer Feedback

Closed-loop feedback means that customer information leads to action and that the outcome of the action is tracked. It has two levels:

• Inner loop: an individual customer receives follow-up, resolution or explanation.
• Outer loop: the organisation analyses patterns, changes processes and verifies improvement.

A typical feedback cycle is:

Collect → interpret → prioritise → assign → act → inform customer or stakeholders → verify → institutionalise learning

Feedback sources include surveys, complaints, reviews, contact reasons, usage data, interviews, social listening and frontline observations. Each source has bias. Survey respondents may not represent silent customers; public reviews may overrepresent extreme experiences; operational data may show behaviour without motives.

Feedback measures

A widely used recommendation measure is the Net Promoter Score (NPS):

Respondents usually rate likelihood to recommend on a 0–10 scale; promoters are commonly scores 9–10 and detractors 0–6. The result ranges from −100 to +100. Passives are not included in the subtraction. NPS is a sentiment indicator, not a direct measure of profit, service quality or causation. It should be combined with behavioural, operational and qualitative evidence.

Customer effort measures how easy it was to accomplish the task. Satisfaction measures the customer’s evaluation of the interaction or outcome. These measures answer different questions and should not be treated as interchangeable.

Governance of feedback

Every important feedback theme should have an owner, action, deadline and success measure. Governance meetings should examine whether actions were completed and whether the original problem declined. Closing the loop also requires communicating honestly when a requested change is not feasible. False promises damage trust more than a transparent explanation of constraints.

9. Ethics, Privacy and Regulation

Sales and service CRM processes substantial personal and sometimes sensitive information. Organisations should collect only information needed for a legitimate purpose, explain how it will be used, maintain appropriate security, control access, retain it no longer than justified and provide applicable rights of access, correction or deletion. Exact legal duties vary by jurisdiction, sector and customer status; managers must consult current law and specialist advice.

Important ethical risks include:

• manipulative sales pressure and dark patterns;
• discriminatory lead scoring or service prioritisation;
• surveillance beyond reasonable customer expectations;
• recording calls without appropriate notice;
• exposing complaint details to unauthorised staff;
• using vulnerable customers’ data to increase sales;
• automated decisions that cannot be explained or challenged;
• suppressing complaints or rewarding staff for avoiding escalation.

AI can assist with summarisation, routing, forecasting, knowledge retrieval and anomaly detection. It should be governed through data-quality checks, human oversight, testing for bias, audit trails, security controls and clear escalation. AI-generated customer responses require review where accuracy, empathy, legal rights or financial consequences are significant. Automation should reduce effort, not transfer work and risk invisibly to customers.

10. Integrated Applied Case: Northstar Home Energy

The following is a fictional illustrative case.

Background

Northstar Home Energy sells household energy plans and smart thermostats. Its brand promise is “simple control and dependable support.” Sales, installation and customer service use separate systems. The company has grown rapidly through digital advertising and telephone sales.

Problem

Within six months, complaints about unexpected charges and delayed installation doubled. Sales representatives recorded “customer agreed” without consistently documenting tariff explanations. The contact centre measured average handling time and rewarded rapid closure. Customers who began with the chatbot had to repeat their information to agents. Management initially proposed increasing agent productivity targets.

Analysis

CRM review found four connected causes:

1. Sales scripts emphasised monthly estimates but did not explain variable charges clearly.
2. Installation capacity was not connected to the sales calendar.
3. The chatbot could answer billing questions but could not identify vulnerable customers or transfer case history reliably.
4. Agents closed cases after sending a generic explanation, even when the underlying charge remained disputed.

Complaint data also showed that the highest-value accounts were receiving faster escalation, while customers with language and accessibility needs experienced longer resolution times. This created both fairness and reputational risks.

Approach and solution

Northstar redesigned the process as follows:

• CRM qualification required recorded confirmation of tariff type, estimated-use assumptions and installation constraints.
• The sales pipeline included an operational feasibility checkpoint before commitment.
• A shared case ID preserved chatbot, telephone and email history.
• Complaint classification separated billing explanation, incorrect charge, installation delay and vulnerability-related needs.
• Agents received authority to correct small errors without managerial approval.
• Closure required either customer confirmation or documented evidence that the dispute had been resolved and escalation rights had been provided.
• Weekly outer-loop reviews assigned root causes to sales, billing, technology and operations owners.
• Performance management balanced handling time with first-contact resolution, repeat contact, complaint recurrence, quality and customer effort.
• AI-assisted summaries were introduced only after human review controls and an audit process were established.

Outcome

After two quarters, installation-related complaints declined and repeat contacts fell. The company also identified that some complaints had been incorrectly classified as “general enquiries,” so reported complaint volume initially rose before the data became more reliable. Management judged the programme successful not because every complaint disappeared, but because customers received clearer commitments, employees could resolve issues, and recurring causes were assigned for correction.

Learning points

The case demonstrates that complaint management begins before the complaint, through accurate selling and feasible fulfilment. It also shows that service metrics can create failure when they reward speed without resolution. Finally, omnichannel CRM is a process and governance challenge, not merely a technology integration project.

11. Implementation Guidance and Professional Implications

A practical implementation can proceed in stages:

1. Map priority customer journeys and identify failure points.
2. Define common customer, opportunity, case and complaint data standards.
3. Establish ownership for pipeline stages, service cases and feedback actions.
4. Configure technology around the redesigned process rather than automating current inefficiencies.
5. Train employees in diagnosis, communication, privacy and escalation.
6. Pilot with a controlled customer segment and monitor unintended effects.
7. Compare operational, customer and employee measures.
8. Review outcomes with frontline employees and customers.
9. Scale only when data quality, governance and service capacity are adequate.

Employability in CRM requires more than software familiarity. Graduates should be able to interpret customer data, question unreliable metrics, document processes, communicate across departments, identify ethical risks and turn customer evidence into operational improvement. They should also recognise the limits of dashboards: a number is an invitation to investigate, not an explanation by itself.

Challenges and Limitations

CRM-enabled sales and service programmes face persistent limitations. Data may be incomplete, duplicated or inconsistent across systems. Attribution is difficult: retention may reflect product quality, price, competitor conditions or service. Customer feedback is selective and culturally shaped. Forecast probabilities can be overconfident. Automation can scale both good and bad decisions. Employees may resist systems that appear designed for surveillance rather than support.

There are also strategic trade-offs. Standardisation improves consistency but may reduce discretion. Personalisation can improve relevance but increase privacy risk. Self-service reduces cost for routine tasks but can exclude customers with low digital access. Compensation can restore fairness but may encourage opportunistic claims if controls are weak. Managers must therefore evaluate CRM as a socio-technical system involving people, processes, technology, incentives and institutional values.

Chapter Summary

CRM connects sales, service and complaint management across the customer relationship lifecycle. Effective pipeline management uses observable stage criteria, reliable next actions and cautious forecasting. Account management develops value through coordinated understanding of customer goals rather than indiscriminate cross-selling. Service operations should deliver reliability, responsiveness, competence, empathy, accessibility, transparency and ownership.

Contact centres require integrated histories and balanced measures; speed alone can damage resolution quality. Self-service works when tasks are suitable, information is accurate and human escalation remains available. Complaint management should make complaints accessible, investigate root causes, provide proportionate recovery and convert individual cases into organisational learning. Closed-loop feedback links customer evidence to assigned action, verification and communication.

Ethical CRM protects privacy, prevents unfair discrimination, governs automation and avoids incentives that suppress or distort customer voice. The central managerial principle is integration: promises, processes, employee authority, technology, measurement and learning must reinforce one another.

Key Terms

Account management: The planned governance and development of an ongoing customer relationship.

Closed-loop feedback: A process in which feedback leads to action, verification and learning.

Complaint: An expression of dissatisfaction that expects or implies a response.

Contact centre: An operation managing customer interactions across one or more communication channels.

Customer effort: The difficulty experienced by a customer when completing a task or obtaining support.

Customer lifetime value (CLV): An estimate of the discounted future contribution associated with a customer relationship.

First-contact resolution: Resolution of a customer issue during the first substantive interaction.

Inner loop: Follow-up and resolution for an individual customer.

NPS: Net Promoter Score, calculated as the percentage of promoters minus the percentage of detractors.

Omnichannel service: Coordinated service across channels with continuity of information and case ownership.

Outer loop: Organisational analysis and correction of systemic causes revealed by feedback.

Pipeline: The defined stages through which a sales opportunity progresses.

Qualification: Assessment of whether a lead has sufficient need, fit, authority, timing and viability to justify pursuit.

Root-cause analysis: Investigation of underlying conditions that produce a failure or complaint.

Self-service: Customer completion of information or service tasks without direct employee assistance.

Service recovery: Actions taken to correct a service failure and restore confidence.

Service-level agreement: A documented commitment defining service performance, measurement and responsibilities.

Touchpoint: Any interaction through which a customer encounters the organisation or brand.

Review Questions

Short Answer Questions

1. What is the purpose of a sales pipeline in CRM?
2. Why should complaint closure require more than sending a response?
3. Distinguish multichannel service from omnichannel service.
4. What is the difference between the inner and outer feedback loops?
5. Identify two risks of measuring contact-centre performance using average handling time alone.

Long Answer Questions

1. Explain how CRM can align a brand promise with sales, onboarding and service operations.
2. Discuss the principles of effective account planning and responsible customer development.
3. Evaluate the role of self-service in an omnichannel customer journey.
4. Describe a complete complaint-management process, including root-cause analysis and governance.
5. Explain why balanced performance measures are necessary in contact centres and service operations.

Analytical / Application Questions

1. A company has high sales conversion but rising cancellation and complaint rates. Analyse possible CRM, incentive and service causes, and propose an investigation plan.
2. A retailer receives 180 complaints from 45,000 transactions. Calculate the complaint rate per 1,000 transactions and explain why segmentation is necessary before judging performance.
3. Design a closed-loop feedback process for a subscription business whose customers report repeated billing errors across email, chat and telephone channels.

Multiple Choice Questions with Answers

Question 1

Which condition provides the strongest evidence that a sales opportunity has reached the proposal stage?

A. The salesperson believes the customer is interested.

B. The customer has confirmed needs and evaluation criteria, and a documented proposal has been delivered.

C. The lead has opened a marketing email.

D. The opportunity has remained in the pipeline for 30 days.

Correct Answer: B. The customer has confirmed needs and evaluation criteria, and a documented proposal has been delivered.

Question 2

A pipeline contains opportunities of £20,000 at 0.30 probability and £10,000 at 0.80 probability. What is their combined expected value?

A. £14,000

B. £22,000

C. £26,000

D. £30,000

Correct Answer: B. £22,000

Question 3

Which measure most directly indicates whether an issue was resolved during the first substantive interaction?

A. Average speed of answer

B. First-contact resolution

C. Customer acquisition cost

D. Pipeline coverage

Correct Answer: B. First-contact resolution

Question 4

What distinguishes omnichannel service from merely multichannel service?

A. Omnichannel service uses only digital channels.

B. Omnichannel service eliminates human employees.

C. Omnichannel service maintains continuity as customers move among channels.

D. Omnichannel service offers fewer service options.

Correct Answer: C. Omnichannel service maintains continuity as customers move among channels.

Question 5

If 240 complaints arise from 60,000 transactions, what is the complaint rate per 1,000 transactions?

A. 0.4

B. 2

C. 4

D. 40

Correct Answer: C. 4

Question 6

Which action belongs primarily to the outer feedback loop?

A. Calling an individual customer about a case.

B. Sending an acknowledgement of a complaint.

C. Changing a recurring billing process after analysing complaint patterns.

D. Providing a refund to one customer.

Correct Answer: C. Changing a recurring billing process after analysing complaint patterns.

Question 7

Why is average handling time an insufficient standalone contact-centre measure?

A. It cannot be recorded in a CRM system.

B. Reducing it may encourage premature closure and repeat contacts.

C. It measures only customer profitability.

D. It always increases employee wellbeing.

Correct Answer: B. Reducing it may encourage premature closure and repeat contacts.

Question 8

Which response best represents proportionate service recovery?

A. Offering the same compensation for every failure regardless of impact.

B. Ignoring the complaint if the customer has low predicted value.

C. Acknowledging the failure, correcting it, and offering a remedy related to the customer’s impact.

D. Transferring every complaint to a legal department.

Correct Answer: C. Acknowledging the failure, correcting it, and offering a remedy related to the customer’s impact.

Question 9

What is the principal limitation of using NPS as the sole measure of service quality?

A. It cannot be calculated from survey responses.

B. It directly measures operational resolution time.

C. It is a sentiment indicator and does not by itself establish quality or causation.

D. It includes only customers who have made complaints.

Correct Answer: C. It is a sentiment indicator and does not by itself establish quality or causation.

Question 10

Which practice is most appropriate when deploying AI for complaint-response assistance?

A. Allowing the system to close all complaints automatically.

B. Using AI without informing employees or customers.

C. Applying human oversight, auditability and escalation for high-risk cases.

D. Optimising only for the shortest response time.

Correct Answer: C. Applying human oversight, auditability and escalation for high-risk cases.