Use case

Handling a frustrated omnichannel customer who has already called and written in

He submitted his claim through the app, sent two emails, opened a chat, called once, and nothing has moved. When this frustrated omnichannel customer calls again, the agent who picks up gets three weeks of irritation. The agent has to read the history before asking a single question, then keep ownership of the case until it's resolved.

A frustrated customer, phone to her ear in front of her laptop and an opened parcel, waits for an answer
Situation
A customer who has already written and called without getting an answer calls back, annoyed
For
Customer service agents, omnichannel support teams and their supervisors
Length
A 5 to 10 minute simulated call, followed by the scorecard and the AI coach
What's evaluated
Picking up the history, acknowledging the customer's effort, resolution, commitment to closing the case

The frustrated omnichannel customer.

Ryan Mitchell paid $312 out of pocket at his dentist and submitted the claim to his insurer through the app on February 3. With no news, he sends two emails. The chat tells him his file is complete, while the reply to his second email asks for the receipt he already sent. He calls on February 20 and is told the claim will be processed within 48 hours. Three weeks later, he calls again.

Each channel gave him a different answer, and none of them solved the problem. The agent can see five contacts on the same case in the system, as long as they open them.

In short

A member has been waiting since February for a $312 reimbursement. He calls back after five contacts across four channels, and conflicting answers.

What makes the call hard.

The agent comes in last, and takes the anger built up on the other channels. The customer has already told his story several times. A question whose answer is already in the file (“Could you give me the date of the treatment again?”) confirms what he suspects: nobody reads what he sends.

The agent still has to verify his identity, and sometimes ask a question again, which goes better with a reason attached. The case stays assigned to the team that opened it, the agent can't always chase the claims handler, and the easy way out is to promise another 48 hours.

In short

The agent takes anger built up elsewhere, and every question already asked on another channel makes it worse. Without a process for this case, the temptation is to promise another deadline.

What research says.

In 2010, Matthew Dixon, Karen Freeman and Nicholas Toman, of the Corporate Executive Board, published a study in Harvard Business Review covering more than 75,000 customers over three years, on their contacts with customer service by phone, on the web, by chat or by email.

56%of customers surveyed had to re-explain their issue
62%had to contact the company repeatedly to get it resolved

The authors also measured how much effort customers had to put in to get an answer. Among customers who had a hard time solving their problem, 81% intended to speak negatively about the company, compared with 1% of those who reported low effort.

In 2013, Jeff Joireman, Yany Grégoire, Berna Devezer and Thomas Tripp studied what happens when a company's attempt to fix a problem fails in turn, which researchers call a double deviation. The customer's reaction then depends on the motive they attribute to the company. When they infer a good motive, the desire to reconcile outweighs the desire for revenge, and an apology combined with compensation can shift the inferred motive in that direction. After five contacts and two conflicting answers, Mr. Mitchell believes his insurer isn't looking at his file.

In short

More than half the customers surveyed had to re-explain their issue or contact the company again. After a second failure, an apology and compensation can change the motive the customer attributes to the company.

The scenario to practice.

The agent takes the call with the history of all five contacts in the system.

ElementIn the scenario
The customerRyan Mitchell, a member for four years. He had never contacted customer service before this claim.
His historyThe claim submitted on February 3, two emails, the chat (“file complete”), a reply asking for the receipt, a call on February 20 (“processed within 48 hours”). The file shows the receipt was attached to the wrong member ID by mistake.
What he says up front“This is the fifth time I've contacted you about the same claim. Read the file, it's all there.”
What he keeps to himselfHe has drafted a written complaint and plans to send it tonight if nothing moves. He needs the $312 before the end of the month. He only mentions it if the agent asks what he expects from the call.
The agent's goalSummarize the history without making him repeat what's in the file, acknowledge his effort and the conflicting answer, find the misattached receipt, start the reimbursement with a date, and leave him a named contact until it's paid.

In the simulation, the customer gets annoyed as soon as he's asked something the file already answers. An agent who opens with “I can see your claim from February 3, your two emails, the chat and your call on the 20th” has an easier time getting the information still missing.

The scenario can be adapted by type of problem and channels already used, for example an internet box still down after two chat sessions. It's one of the scenarios in our call center simulator.

In short

The agent has to read the file, find the misattached receipt and stay the customer's contact until the reimbursement is paid.

The scorecard.

CriterionWhat to listen for
Picking up the historyThe agent summarizes the previous contacts before asking questions, and only asks for what's missing, with a reason.
Acknowledging the effortThe agent acknowledges the number of contacts and the conflicting answer, without criticizing colleagues or other channels.
Customer's expectationThe agent asks what the customer expects from the call and plays it back.
ResolutionThe cause is found during the call, or a specific action is started with a date.
OwnershipThe customer leaves with a named contact or a direct reference, and a callback date if needed.
ClosingThe agent recaps what was done and checks that nothing else is open on the case.

If the reimbursement can't be paid right away, the agent has to say so clearly, with a date, as in our use case on how to deliver bad news to customers. If Mr. Mitchell says he's switching insurers, the conversation becomes a retention call, covered in when a customer wants to cancel.

In Engramm, the scenario starts from the typical history of a stuck case and the team's procedures. After the call, the scorecard might show, for example, that the agent summarized the history well but gave no date. The AI coach goes back over the first minute of the call with the agent, and the supervisor tracks results by agent and by scenario in the dashboard.

Template to download: omnichannel customer call scenario sheet and scorecard

The trainer's scenario sheet, with what the customer keeps to himself and the variants, then the observer's scorecard, as a two-page PDF.

In short

The scorecard rates picking up the history and acknowledging the customer's effort first, then resolution and ownership of the case until it's closed.

Frequently asked questions.

How do you handle an angry customer who keeps calling back?

Read the history before asking anything, and start by summarizing what you see. Acknowledge the steps they've already taken, look for the cause of the problem during the call and give them a date. If they need a follow-up, leave them a named contact and a callback date.

What is an omnichannel customer?

A customer who contacts a company through several channels, such as the app, email, chat and phone. In the study published in Harvard Business Review in 2010, 57% of inbound calls came from customers who had gone to the website first.

What is the Customer Effort Score?

A measure of how much work a customer had to do to get a request handled, introduced in 2010 by Matthew Dixon and his coauthors. It asks a single question, “How much effort did you personally have to put forth to handle your request?”, scored from 1 (very low effort) to 5 (very high effort).

Sources.

  • Matthew Dixon, Karen Freeman and Nicholas Toman (2010), “Stop Trying to Delight Your Customers”, Harvard Business Review, July-August 2010: hbr.org
  • Jeff Joireman, Yany Grégoire, Berna Devezer and Thomas M. Tripp (2013), “When Do Customers Offer Firms a ‘Second Chance’ Following a Double Deviation? The Impact of Inferred Firm Motives on Customer Revenge and Reconciliation”, Journal of Retailing, 89(3), 315-337: doi.org

Geoffrey Mathern

Director of Operations, Engramm

Geoffrey Mathern has been Director of Operations at Engramm since October 2025. He works with the training teams and sales leaders of Engramm's customers, from scenario design to tracking results. Before Engramm, he spent more than ten years in digital marketing and SEO, including almost six at Fabernovel.

LinkedIn profile
Newsletter

Get the next resources.

An email every two weeks with new guides, customer stories and webinars.

See Engramm on one of your topics.

In 45 minutes, we show you the platform on a topic your teams work on.

Book a demo
Book a demo