Customer Service Training Activities

Good customer service training is mostly practice. Reps get better by working through real situations, and a slide deck does not do much when a hard ticket lands. 

This post is a library of customer service training activities, sorted by the skill each one builds, and every activity comes with the steps to run it this week. 

You should match each activity to the work your team actually does, since B2B SaaS support, retail, and an internal IT help desk are not training for the same things.

How to use these activities effectively?

There are a few best practices that you can follow to use these activities effectively. The first one is to group them by skill. Also, every activity you run should connect back to a real ticket or a real scenario your team has actually had, because a role-play with no real context to it does not stick with the reps. 

You should run a debrief after each of the activities too, because that debrief is usually where the learning actually happens, and skipping it wastes the activity. Where you can, it helps to mix the in-person sessions with the async ones, as some skills like active listening or de-escalation really need the live practice, and a few others like empathy will do fine on async. Beyond these, try to keep each session under about 90 minutes, because the group's attention tends to drop off fairly fast once you go past that.

Activity template, what to expect

Every activity below follows the same layout. That is on purpose. It should make them quick to scan. Each one starts with the skill it builds, then the time it takes, the number of people, and the materials if there are any. Then come the steps to run it. After that come the debrief questions, and a line on running it remotely. So you do not have to read all of them. Find the skill you want, take that one, and use it.

Empathy training activities

Empathy is the one customers notice most. It is also the hardest thing to teach from a slide deck. These empathy training activities for customer service get reps practicing it on the real situations they actually deal with.

Empathy mapping

• Skill targeted: Empathy, seeing the situation from the customer's side
• Time: 30 to 45 minutes
• Participants: 3 to 8 in a group
• Materials: a whiteboard or a shared doc, plus a few customer persona cards made up beforehand

How to run:

1. Hand each group a persona card. Something like a frustrated new user, or a customer whose renewal is coming up.
2. Draw the map. Four boxes on the board, for what the customer is thinking, feeling, saying, and doing.
3. The group fills in each box for their persona, from the customer's side and not the company's.
4. Give it about 15 minutes. Let them argue a bit over what the customer actually feels, that is the useful part.
5. Each group then walks the rest of the room through their map.
6. Pin the maps up somewhere the team can see them later.

Debrief questions:

• What surprised you about what the customer was feeling?
• Where were you guessing, and where did you actually know?
• Does anything on the map change how you would reply to that customer?

Remote adaptation: Use Miro or Mural for the boxes, or just one shared doc split into four. Smaller groups work better here, so keep it to three or four people.

Walk in the customer's shoes (role reversal)

• Skill targeted: Empathy, feeling what the customer actually goes through
• Time: 20 to 30 minutes
• Participants: pairs, or small groups of 3
• Materials: a few real support scenarios written on cards, no other kit needed

How to run:

1. Pair everyone up. One person is the customer, the other is the agent.
2. Give the customer a scenario card, and let them play it the way a real annoyed customer would, not a polite one.
3. The agent handles it as normal.
4. Halfway through, they swap. The agent becomes the customer.
5. Run it again with a fresh scenario so both people have been on the customer side.

Debrief questions:

• What did the customer side feel like that you had not expected?
• Did anything the agent said make it worse, even if it was correct?
• What will you do differently on your next real ticket?

Remote adaptation: Run the pairs in Zoom breakout rooms. Give each pair their scenario in a DM so the other one does not see it first.

Storytelling, sharing a difficult customer interaction

• Skill targeted: Empathy, learning from each other's hard cases
• Time: about 30 minutes
• Participants: the whole team, up to around 10
• Materials: none, people just bring a story

How to run:

1. Everyone picks one real difficult customer they had. Not a made-up one, a real one.
2. Go round the room. Each person gets a couple of minutes to tell it, what the customer wanted, where it went wrong, how it ended.
3. Everyone else listens. Questions later, after the story is done.
4. Then the group says what they reckon the customer was really upset about underneath it all.
5. Next person.

Debrief questions:

• Whose story was closest to a ticket you have had?
• Was the customer really angry about that, or something else?
• Anything you would take from how someone else dealt with theirs?

Remote adaptation: Do it on Zoom, cameras on, the tone matters here. Keep the group small, or split into two so people are not waiting around.

First-call simulation (for new hires especially)

Skill targeted: empathy under pressure, getting a new hire through a first real call
Time: 20 to 30 minutes each
Participants: a new hire, someone as the customer, maybe an observer
Materials: a realistic scenario and the actual tools they will be on

How to run:

1. The whole setup should be made to look like a real shift. Same tools, the same login they will use, and the same ticket queue that comes up on their first day.
2. One of the teammates can play the customer for it. Keep the scenario a normal one, nothing too extreme for a first go at it.
3. The new hire is then left to run the whole thing on their own, from start to end.
4. This is the important part of it. You should let them fumble around a bit, and you should not be jumping in to rescue them every time.
5. There should be someone else watching who notes down where it all went wrong, and that becomes the thing you talk through in the debrief after.
6. The debrief should happen right away, while the thing is still fresh in their head.

Debrief questions:

• Where did it start to go wrong for you?
• What is the one thing that would have helped in that moment?
• Was there a tool or a step that slowed them down?

Remote adaptation: the whole thing can be done over Zoom, with the new hire sharing their screen, since a lot of them are going to be working that way regardless. The observer just keeps an eye on the shared screen.

First-call simulation (for new hires especially)

• Skill targeted: Staying calm and empathetic on a first live-style call
• Time: Around 25 minutes for each person
• Participants: One trainee, one acting as the caller, an optional watcher
• Materials: A believable ticket or call scenario, and whatever software the role uses

How to run:

1. You want to recreate the conditions a trainee would meet on day one, right down to the login and the software they will be handling.
2. A colleague takes the caller role and brings a fairly ordinary problem to the table, nothing dramatic for a first attempt.
3. From there the trainee should handle the case on their own, all the way through to closing it out.
4. Try not to step in when they stumble. The stumbling is usually where the value is.
5. A quiet observer can note down the moments that tripped them up, just as material for the talk afterwards.
6. You should run the review while it is all still recent for them.

Debrief questions:

• At what point did the call feel like it slipped away from you?
• Looking back, what single bit of support would have made a difference there?
• Did any part of the software get in the way more than the caller did?

Remote adaptation: Move it onto a video call and ask the trainee to share what is on their screen, which mirrors how plenty of support gets done now. Whoever is observing follows along on that shared view.

Active listening training activities

Most reps believe they already listen well, but real listening under pressure takes practice. These active listening customer service training activities give them that practice on actual conversations.

Mirrored listening pairs

• Skill: Active listening, paraphrasing back what you heard
• Time: About 20 minutes
• Participants: Pair
• Materials: None really, maybe a couple of scenario prompts

How to run:

1. Put people into pairs. One talks, one listens, then they switch.
2. The talker describes a problem for a minute or two, something like a real customer complaint.
3. The listener is not allowed to jump straight to a solution. They should first repeat back what they heard, but in their own words.
4. The talker then says whether that summary actually matched what they meant.
5. Swap the roles and run it again.

Debrief questions:

• How close was the summary to what you were actually trying to say?
• As the listener, what did you miss the first time around?
• Did having to repeat it back change how closely you listened?

Remote adaptation: This one runs fine on a video call, just put each pair in their own breakout room for the few minutes they need.

The blindfold direction challenge

• Skill: Active listening, following spoken instructions precisely
• Time: About 15 minutes
• Participants: Pairs
• Materials: A blindfold and a small obstacle course set up in the room

How to run:

1. Blindfold one person in each pair. The other one is the guide.
2. Set up a small course, a few chairs to get around, an object to pick up, that kind of thing.
3. The guide can only use words. No touching, no pointing at anything.
4. The blindfolded person has to get through it just based on what they hear.
5. Time it, then swap over and try a slightly different course.

Debrief questions:

• Where did the instructions break down, and was it the talking or the listening?
• As the guide, how did you change your wording when it was not landing?
• How does this map onto guiding a customer through steps on a call?

Remote adaptation: Harder to do remotely, but you can run a version where one person describes an image, and the other draws it blind, just from the words.

Telephone (yes, the childhood game)

• Skill: Active listening, and seeing how information gets lost in handoffs
• Time: About 10 minutes
• Participants: A group of 6 or more
• Materials: None, just a made-up customer message

How to run:

1. Line everyone up, or put them in a circle.
2. Give the first person a fairly detailed customer message, a few facts in it, a name, an order number, a specific complaint.
3. They pass it quietly to the next person, who passes it on, all the way down the line.
4. The last person says out loud what they got.
5. Compare that to the original, usually half of it is gone or changed.

Debrief questions:

• Which details survived, and which ones dropped off?
• What does this say about how a ticket gets handed between agents?
• What could you write down so the next person does not lose the thread?

Remote adaptation: Do it in a chain of DMs, each person messages the next privately, and the last one posts what they ended up with.

Repeat-back demo calls

• Skill: Active listening, paraphrasing on a live-style call
• Time: About 30 minutes
• Participants: The whole team, or small groups
• Materials: A recorded support call, and a way to play it and pause it

How to run:

1. Play a recorded support call for the group, a real one if you can get consent to use it.
2. Pause it every so often, right after the customer has said something important.
3. Ask someone to paraphrase what the customer just said, and what they actually want underneath it.
4. Play a bit more, pause again, ask a different person.
5. Keep going to the end of the call.

Debrief questions:

• How often was the paraphrase close, and how often was it off?
• Did people catch what the customer wanted, or just the words they used?
• Where would a quick repeat-back have helped the real agent on the call?

Remote adaptation: Share the audio on a video call, pause it the same way, and let people take turns paraphrasing over the mic.

Communication and problem-solving activities

Good service is half how you say things, half how you figure out the problem in the moment. These customer service skills training activities work on both sides of that.

"Yes, and..." improv exercises

• Skill: Communication, thinking on your feet, building on what the customer says
• Time: About 20 minutes
• Participants: Small groups of 4 to 6
• Materials: None

How to run:

1. Get a group going with a simple made-up scenario, a customer asking for something a bit unusual.
2. One person starts, and the next has to answer beginning with "yes, and", then add something of their own.
3. It goes round the group, each person taking what came before and putting another line on top.
4. Nobody is allowed to shut it down with a flat "no".
5. Run it a couple of times with different scenarios.

Debrief questions:

• How did it feel to build on the last person instead of correcting them?
• Where does "yes, and" actually fit with a real customer, and where would it not?
• Did blocking the idea change the mood in the room?

Remote adaptation: Works on a video call, just go in a set order so people are not talking over each other.

Find a way to say it (rephrasing exercise)

• Skill: Communication, turning a blunt message into something a customer can actually hear
• Time: About 20 minutes
• Participants: Small groups or pairs
• Materials: A few blunt or cold example messages to start from

How to run:

1. Hand each group a few messages that are technically correct but come off cold, like a flat "that is not possible".
2. Their job is to rewrite each one so it lands better, without changing what it actually says.
3. Give them a few minutes, then have each group read their versions out.
4. The group picks which rewrite works best, and why.
5. You can pull the starting messages from your real macros, the ones that always seem to get complaints.

The customer service phrases organized by situation give reps a bank to rework here, so they are not starting from a blank page.

Debrief questions:

• What made the better version better? Was it the words or the tone?
• Did any rewrite change the meaning by accident?
• Which of these could go straight into your real replies?

Remote adaptation: Easy to run async, drop the messages in a shared doc and have people add their rewrites underneath.

Customer service Jeopardy

• Skill: Product knowledge and communication, under a bit of friendly pressure
• Time: About 30 minutes
• Participants: The whole team, split into 2 or 3 teams
• Materials: A set of questions in categories, and a way to keep score

How to run:

1. Build a board of categories, things like product features, common issues, policies, tricky scenarios.
2. Teams take turns picking a category and a point value.
3. Read the question out, the first team to answer right gets the points.
4. Wrong answers hand the question over to the other team.
5. The highest score at the end wins, keeping the stakes light and fun.

Debrief questions:

• Which category did the team struggle on the most?
• Were the gaps about the product itself, or about how to explain it?
• What is worth turning into a proper training follow-up?

Remote adaptation: Runs fine on a video call with a shared slide deck for the board, and one person acting as host to keep score.

Case study workshops

• Skill: Problem-solving, judgment, learning from real tickets
• Time: About 40 minutes
• Participants: Small groups of 3 to 5
• Materials: A real ticket transcript, anonymized, plus a couple of guiding questions

How to run:

1. Give each group a real ticket transcript, with the names and any private details taken out.
2. They read through it and mark the points where it went well, and the points where it went off.
3. Each group talks through how they would have handled it differently.
4. Bring everyone back together and compare what the groups picked up on.
5. Pull out one or two things the whole team can start doing from the next shift.

Debrief questions:

• What did the original agent do that you would keep?
• Where did the ticket lose the customer, if it did?
• What is the one change worth making across the team?

Remote adaptation: Put each group in a breakout room with the transcript in a shared doc, then regroup to compare notes.

De-escalation and stress management activities

Nothing tests a rep like an angry customer. No phrase magically fixes one either. These activities are about staying steady under it and bringing the heat down a bit.

Angry customer role-play (with a real debrief)

• Skill: De-escalation, staying calm, and reading the emotion under the complaint
• Time: About 30 minutes
• Participants: Pairs, plus the rest of the team watching
• Materials: A few escalated scenarios written up

How to run:

1. One person plays an angry customer, the other is the rep. Give them a scenario with a real reason to be upset.
2. Let it run for a few minutes. It can get uncomfortable, that is fine.
3. The important bit comes after, when you stop and talk through what just happened.
4. Ask the rep what they felt, what they tried, and where it started working or not.
5. Then ask the room what they noticed from the outside.

Debrief questions:

• What actually calmed the customer down, if anything did?
• Where did the rep's own stress start to show?
• What would you try next time you get a real one like this?

Remote adaptation: Do the role-play on video so tone comes through, and keep the watchers on mute until the debrief.

Deep breathing and reset breaks

• Skill: Stress management, resetting between hard tickets
• Time: 5 minutes, or whenever it is needed
• Participants: Anyone, on their own or as a team
• Materials: None

How to run:

1. After a rough ticket, the rep steps away for a couple of minutes before taking the next one.
2. A few slow breaths, or a short walk, whatever actually resets them.
3. The point is to not carry the last customer's mood into the next chat.
4. As a team, you can make it normal to take a reset, so it does not feel like slacking off.

A positive attitude in customer service is built on small resets like these as much as on anything bigger.

Debrief questions:

• Does the team actually feel able to take a reset, or does it feel frowned on?
• What is a realistic reset that fits between back-to-back tickets?

Remote adaptation: Even easier remote, a rep can mute, step away from the desk, and come back before picking up the next one.

"First World Problems" empathy game

• Skill: Patience and taking a customer's small-seeming problem seriously
• Time: About 15 minutes
• Participants: The whole team
• Materials: None, people bring their own examples

How to run:

1. Ask everyone to think of a problem that seems tiny to them and is a huge deal to some customer.
2. Go round and have people share theirs, no judging the examples.
3. For each one, the group works out why it matters so much to that customer.
4. Keep it light, the whole point is building a bit of patience.

Debrief questions:

• Whose example changed how you would react to that kind of ticket?
• Where do you catch yourself thinking a customer is overreacting?
• How do you take a small-seeming issue seriously without faking it?

Remote adaptation: Works as a quick round on a video call, or even async in a Slack thread where people drop their examples.

Product knowledge activities

You cannot help a customer with a product you do not really know. These activities push reps to learn it deeper than a support script ever goes.

Product demo by reps (teach to learn)

• Skill: Product knowledge and explaining it in plain language
• Time: About 20 minutes per rep
• Participants: The whole team, one presenting at a time
• Materials: Whatever the rep needs to show the feature

How to run:

1. Each rep gets a feature or a part of the product to present to everyone.
2. They have to actually teach it, not just click through it, so the rest of the team could handle a ticket on it after.
3. The team can throw the awkward questions a customer would ask.
4. Rotate through so everyone teaches something over a few weeks.

Debrief questions:

• What did you understand better once you had to teach it?
• Which customer questions did the presenter struggle with?
• What is still fuzzy enough to need a proper doc?

Remote adaptation: Screen share on a video call works, and you can record it so it turns into a little training library over time.

Mystery shopper/competitor call

• Skill: Product knowledge and seeing how other support teams handle things
• Time: About 30 minutes, plus a share-back
• Participants: Individuals, then the group
• Materials: None, just another company to contact

How to run:

1. Each rep contacts another company's support, as a normal customer with a normal question.
2. The point is to notice how it felt, what was good, what was slow, what they would copy.
3. Keep it honest and low-key, this is for learning and not for messing anyone around.
4. Everyone shares back what they picked up.

Debrief questions:

• What did another team do that you would want to steal?
• Where did their support feel worse than yours?
• What is one thing worth changing in your own replies from this?

Remote adaptation: This one is already remote, really, just do the share-back on a call or in a thread.

Bug-bash with the engineering team

• Skill: Deep product knowledge, finding the edges where it breaks
• Time: About 60 minutes
• Participants: Support reps, plus a few engineers
• Materials: A test environment, not the live product

How to run:

1. Get support and engineering in the same session for an hour.
2. Reps try to break the product on purpose, poking at the odd edge cases customers hit.
3. Engineers watch what happens and explain the why behind it.
4. Log anything that breaks, some of it becomes a bug fix, some becomes a support note.

Debrief questions:

• What broke that you did not expect to?
• Which of these will customers actually run into?
• What do reps now know that was not written down anywhere?

Remote adaptation: Works over a shared screen on a call, with everyone poking at the same test environment.

Customer service training activities for internal support teams

Internal support includes IT helpdesk, HR, internal ops, and other employee experience teams. The skills these teams have are similar to other external support teams. What makes it different is the people at the other end.

Your customer might be a coworker, or even your manager's manager. They usually already know the context, so scripted replies will not be the right choice to be sent to them. These internal customer service training activities take the earlier ones and fit them to that.

• Internal ticket triage workshop: Pull a batch of real internal tickets with the names on them, and have the team triage them live. Who gets it, how urgent is it, what order to work them in. 
• Cross-department empathy mapping: Practice empathy mapping from earlier aim it at another department this time. What does engineering need from IT, and surface the stuff each side assumes the other already knows.
• The "I'm your colleague" role-play: Practice the requests where the person asking outranks you, or is a friend, or both. A VP pinging you directly for a fix is a different thing to a normal ticket. Reps get to work out how to hold the process without being difficult about it.
• Internal NPS or sentiment debrief: If you run an internal CSAT or a pulse survey, go through the results with the team. Pick out the pain points that keep coming up, and pick one to actually fix this quarter.

A lot of internal teams run these requests inside Slack, in channels and DMs, which is where the work is happening anyway. Suptask just adds a bit of ticket structure on top of those Slack conversations, so the triage and tracking of these activities practice does not stay stuck in scattered DMs.

How to run customer service training remotely? 

There are a few general principles that help when you are running these activities remotely, such as:

• You should go async wherever you can, because live time is expensive, so keep it for the activities that really need everyone together, like the role-plays and the live discussions.
• Any activity that depends on the tone of voice or the facial expressions should be run on video, and not just on audio or text.
• The groups should also be kept smaller when you are remote, around three to five people in a breakout is usually the most that works well.
• For the activities you run async, you can use a Slack thread for the debrief, where everyone adds their answers, and you go through them afterwards.

On the tools side, most teams use some mix of Zoom, Miro, and Slack, which covers almost all of these. The wider set of communication tools breaks down what fits each job if you want something more specific.

A sample 90-minute training session

Here is one way you could combine four of these into a single 90-minute session for a group of new hires. The rough shape would look something like this:

• 0:00 to 0:10, you should open with a quick welcome and lay out what the session is going to cover, so everyone knows what is happening.
• 0:10 to 0:30, you can start them on the empathy mapping, since it is a lower-stakes warm-up that gets people talking before the more difficult activities.
• 0:30 to 0:55, then you should move into the mirrored listening pairs, where they get some real practice at paraphrasing back.
• 0:55 to 1:20, after that you can run the angry-customer role-play with the full debrief, which is the heaviest part and works best once the group is warmed up.
• 1:20 to 1:30, you should wrap it up by having each rep name three things they are going to try on their own tickets this week.

Keep in mind this is only a template. You should swap the activities around to match wherever your own team is actually weakest, and there is no need to run this exact order every time.

Activities to avoid (and why)

There are also a few activities that you are better off skipping, and it is worth knowing why, such as:

• You should skip the generic trust falls and the physical icebreakers, because they end up building the wrong association, where the reps start to think that training is going to be embarrassing.
• You should also avoid the long lectures that are dressed up as activities, since if the reps are just sitting there and not actually practicing anything, then it is really only a presentation.
• A role-play that you run without any debrief afterwards is not worth much, because the real learning comes out of the conversation you have once it is over.
• You should stay away from the activities that have no connection to your real tickets, as the generic made-up customer scenarios do not really carry over to what the reps face in the actual queue.
• You should also not be putting individuals on the spot in front of everyone, because the whole point of the training is for people to learn, and doing it as a public test just makes them defensive.

How to measure if your training worked? 

There are a couple of ways you can tell whether the training actually did anything, such as:

• You should keep an eye on the trailing customer service metrics that tend to move when the training is working, like the CSAT, the first-contact resolution, and the ticket reopen rate. The average handle time can even go up a little at first while people slow down to do it properly, and then it should come back down over the following weeks.
• You should also run a short survey of the reps about 30 days after the training, and just ask them what they actually started doing differently on their tickets. That leading signal will often tell you more than the numbers do this early on.

If you want the training to actually stick, you should tie its outcomes into the performance review goals you set for each rep, so the improvement becomes something they are measured on.

Frequently asked questions

What are good customer service activities?

The good ones are the activities that get reps actually practicing a specific skill, and not just sitting through a talk about it. This post groups them by skill: empathy, listening, communication, de-escalation, and product knowledge, so you can pick whichever your team is weakest on. You should tie each one back to your own real tickets so it carries over to the queue.

How do you make customer service training fun?

The trick is mostly to keep it active and short. You should tie the activities to real tickets so they feel relevant, keep each session under about 90 minutes, and run a debrief so people feel like they got something out of it. The cheesy icebreakers usually do the opposite, so you can skip those.

What are the 5 elements of customer service training?

They usually come down to five, product knowledge, communication, empathy, problem-solving, and process knowledge, which is your own team's tools and SLAs. Most training programs cover some mix of these. You do not have to hit all five in a single session.

How long should customer service training be?

For a new hire, the training usually runs somewhere around one to two weeks before they are fully on the queue. For ongoing skill training, you are better off with short sessions of 45 to 90 minutes every week or two, because the rare long all-day sessions do not stick as well.

Are these activities free?

Yes, every activity in this post can be run without paying for any special software. The tools that help, like Miro, Slack, and Zoom, are either on a free tier or already in most teams' stacks anyway. So the only real cost is the time you put into running them.

What is the difference between customer service training and customer success training?

Customer service training is mostly about resolving issues and handling the day-to-day support. Customer success training leans more toward the proactive side, keeping customers and helping them get value over time. A lot of the activities like empathy and listening carry over both ways, and it is the scenarios and the metrics that end up being different.

What is the best customer service training activity for new hires?

For new hires specifically, the first-call simulation and the mirrored listening pairs tend to cover the most ground. One gets them used to a real-feeling call before they go live, and the other builds the listening habit early. The sample 90-minute session earlier shows one way you could put them together.