{"id":78882,"date":"2024-10-03T18:32:29","date_gmt":"2024-10-03T18:32:29","guid":{"rendered":"https:\/\/whatfix.com\/blog\/?p=78882"},"modified":"2026-06-09T16:10:29","modified_gmt":"2026-06-09T16:10:29","slug":"role-playing-scenarios-customer-support","status":"publish","type":"post","link":"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/","title":{"rendered":"44 Roleplaying Scenario Examples for Support Teams (+Scripts)"},"content":{"rendered":"<p><a href=\"https:\/\/www.sciencedirect.com\/science\/article\/abs\/pii\/S0260691722003550\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">Research<\/span><\/a><span style=\"font-weight: 400;\"> on <\/span><a href=\"https:\/\/whatfix.com\/blog\/simulation-training\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">simulation-based training<\/span><\/a><span style=\"font-weight: 400;\"> found that scenario-based learning significantly improved teamwork and communication compared with traditional approaches, with roleplay participants performing roughly in the 66th percentile for teamwork and 70th percentile for communication against control groups.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">While this research comes from the healthcare sector, it supports the broader value of roleplay-based training: structured simulations help teams practice communication, collaboration, and decision-making before they face high-pressure, real-world situations.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This <\/span><a href=\"https:\/\/whatfix.com\/blog\/user-readiness\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">user readiness<\/span><\/a><span style=\"font-weight: 400;\"> matters because poor customer experiences carry direct revenue risk. Qualtrics estimates that organizations globally are putting nearly <\/span><a href=\"https:\/\/www.qualtrics.com\/articles\/news\/businesses-risk-3-trillion-sales-poor-customer-experiences-consumers-cut-spending\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">$3 trillion<\/span><\/a><span style=\"font-weight: 400;\"> in sales at risk in 2026 due to bad customer experiences, with 34% of consumers reducing spending and 13% stopping spending entirely after a negative interaction.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Well-designed roleplaying scenarios help agents build the confidence, judgment, and workflow accuracy required to respond clearly, follow the right process, and resolve issues under pressure.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This guide includes 44 roleplaying scenarios for customer support teams across different industries such as banking, healthcare, insurance, retail, and more, all with script starters, agent responses, evaluation criteria, and ways to use AI roleplay to make practice more consistent and scalable.<\/span><\/p>\n<h2><b>What Are Roleplaying Scenarios for Customer Support?<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Roleplaying scenarios for customer support are structured training exercises that simulate real customer interactions, such as billing disputes, technical issues, refund requests, escalation calls, or frustrated customers. They help agents practice how to respond, follow the right process, and escalate issues before handling similar situations with live customers.<\/span><\/p>\n<h2><b>44 Roleplaying Scenarios for Customer Support Teams<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">The following roleplay scenarios help place frontline and service team members into situations that put agents soft skills, procedural knowledge, product awareness, and more to the test.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Each scenario should be adapted to your team\u2019s contextual needs, whether that is support channel, product complexity, customer segment, or agent experience level.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We\u2019ve also broken up our contact center and customer service roleplay scenarios into the following categories:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"#general\"><span style=\"font-weight: 400;\">General support scenarios (industry-agnostic)<\/span><\/a><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"#banking\"><span style=\"font-weight: 400;\">Banking scenarios<\/span><\/a><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"#healthcare\"><span style=\"font-weight: 400;\">Healthcare scenarios<\/span><\/a><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"#insurance\"><span style=\"font-weight: 400;\">Insurance scenarios<\/span><\/a><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"#retail\"><span style=\"font-weight: 400;\">Retail and e-commerce scenarios<\/span><\/a><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"#saas\"><span style=\"font-weight: 400;\">SaaS provider scenarios<\/span><\/a><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"#telecom\"><span style=\"font-weight: 400;\">Telecom and utilities scenarios<\/span><\/a><\/li>\n<\/ul>\n<h3><b><a id=\"general\"><\/a>General scenarios (industry-agnostic)<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Every support team must prepare their agents for frustrated callers, unclear problems, and policy pushback from customers. These core, general customer service scenarios help agents practice the core skills behind great service: active listening, empathy, ownership, clear communication, and confident resolution.<\/span><\/p>\n<h4><strong>Scenario 1. Angry Customer After a Repeated Unresolved Issue<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">A customer has contacted support multiple times about the same issue and feels the team has failed to take ownership. The agent\u2019s goal is to acknowledge the frustration, review the customer\u2019s history, and move the issue toward a clear next step.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI\u2019ve already contacted support three times about this, and I still don\u2019t have a solution. Why should I keep explaining the same issue again?\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Rebuild trust by acknowledging the repeated effort, taking ownership of the issue, and setting a clear path forward.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the customer\u2019s frustration without sounding defensive.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Asking the customer to repeat the full issue from the beginning.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Review previous case notes before asking new questions.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Blaming another team, previous agent, or the customer.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Summarize what has already been tried.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving vague reassurance like \u201cwe\u2019ll look into it.\u201d<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain the next action and who owns it.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Making promises without confirming feasibility.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Escalate with full context if the issue needs specialist review.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ending the interaction without a clear next step.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Empathy, ownership, issue summary, next-step clarity, escalation judgment, and follow-through.<\/span><\/p>\n<h4><strong>Scenario 2. Technical Troubleshooting Under Time Pressure<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">A customer is blocked by a technical issue while trying to complete an urgent task. The agent\u2019s goal is to diagnose the issue quickly, guide the customer through the right steps, and keep the interaction calm and focused.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI need this fixed right now. I\u2019m in the middle of something important and this issue is blocking me.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Diagnose the issue efficiently while keeping the customer focused, informed, and confident in the troubleshooting process.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the urgency and explain the troubleshooting approach.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Rushing into random fixes without understanding the issue.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Ask targeted questions about the task, error message, device, browser, or workflow step.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Overloading the customer with too many questions at once.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Guide the customer through one step at a time.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Using technical language the customer may not understand.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document what has been tested and what changed.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Repeating steps without explaining why they matter.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Escalate when the issue needs technical investigation or admin support.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Keeping the customer waiting without status updates.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Troubleshooting accuracy, question quality, pacing, instruction clarity, documentation, and escalation judgment.<\/span><\/p>\n<h4><strong>Scenario 3. Account Access or Login Issue<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">A customer cannot log in, reset their password, or access the right account permissions. The agent\u2019s goal is to help the customer regain access while following identity verification and security protocols.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI\u2019m locked out of my account and need access immediately. Can you just reset it for me?\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Restore account access safely without bypassing required verification steps or exposing sensitive account information.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the customer\u2019s urgency.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Resetting access before verifying the customer\u2019s identity.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Complete the required identity verification steps.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sharing account information with an unverified user.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Determine whether the issue is related to password reset, multi-factor authentication, permissions, or account status.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Overpromising immediate access.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Walk the customer through the approved recovery process.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Blaming the customer for being locked out.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Escalate the issue if verification fails or admin approval is required.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving vague next steps like \u201ctry again later.\u201d<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Security compliance, verification accuracy, troubleshooting clarity, patience, escalation judgment, and avoidance of unsafe shortcuts.<\/span><\/p>\n<h4><strong>Scenario 4. Customer Immediately Asks for a Manager<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">A customer refuses to continue with the frontline agent and asks to speak with a manager. The agent\u2019s goal is to acknowledge the request, stay composed, and understand the issue before escalating.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI don\u2019t want to talk to you. Get me your manager.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Keep the interaction professional, gather enough context, and determine whether manager escalation is required.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the customer\u2019s request calmly.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Taking the request personally.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Ask for brief context so the issue can be routed correctly.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Refusing escalation outright.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Try to understand the customer\u2019s desired outcome.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Arguing about whether a manager is needed.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain what can be done immediately and what requires manager review.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Transferring without documenting the issue.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Escalate with clear notes if manager involvement is appropriate.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Making the customer repeat the issue unnecessarily.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Composure, professionalism, issue clarification, ownership, escalation judgment, and handoff quality.<\/span><\/p>\n<h4><strong>Scenario 5. Service Outage or Known Incident<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">A customer is affected by downtime, degraded performance, or a known issue that is already being investigated. The agent\u2019s goal is to communicate clearly, share what is known, and set expectations without overpromising.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cYour service is down and it\u2019s affecting my work. When is this going to be fixed?\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Provide accurate incident information, offer any approved workaround, and set realistic expectations for updates.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the disruption and business impact.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Guessing a resolution time without confirmation.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Share the latest confirmed incident update.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Minimizing the issue or using vague language.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain any available workaround.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Blaming internal teams or external vendors.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Tell the customer where and when to expect updates.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving conflicting information across channels.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document the customer\u2019s impact if escalation or follow-up is needed.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ending the conversation without a follow-up path.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Transparency, accuracy, expectation-setting, workaround guidance, follow-up clarity, and incident communication.<\/span><\/p>\n<h4><strong>Scenario 6. Customer Refuses Troubleshooting Steps<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">A customer is frustrated and does not want to repeat basic troubleshooting steps they believe they have already completed. The agent\u2019s goal is to acknowledge the customer\u2019s effort, explain why verification matters, and adapt the troubleshooting flow where possible.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI already tried everything. Don\u2019t make me repeat the same steps again.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Avoid unnecessary repetition while still verifying the steps needed to diagnose and resolve the issue correctly.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge what the customer has already tried.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Starting from the beginning without reviewing prior actions.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Ask which steps were completed and what happened after each one.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sounding scripted or dismissive.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain why a specific verification step is necessary.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Saying \u201cwe have to do this\u201d without context.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Skip or adapt steps when enough evidence exists.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ignoring troubleshooting protocol completely.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document verified steps to prevent future repetition.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Escalating too early without enough diagnostic information.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Patience, adaptability, explanation quality, troubleshooting discipline, tone, and documentation.<\/span><\/p>\n<h4><strong>Scenario 7. Multiple Issues in One Interaction<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">A customer brings up several unrelated problems in the same conversation, making the interaction difficult to manage. The agent\u2019s goal is to organize the issues, confirm priorities, and handle each one in a clear order.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI have three different problems, and I need all of them fixed today.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Structure the conversation so each issue is captured, prioritized, and handled without losing context.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Summarize each issue back to the customer.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Jumping between issues without a clear order.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Confirm which issue is most urgent.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ignoring lower-priority issues without documenting them.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Handle one issue at a time.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Promising all issues will be resolved in the same interaction.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Create separate tickets or follow-ups when needed.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Mixing unrelated problems into one unclear case note.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Set expectations for what can be resolved now and what needs follow-up.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ending the interaction without confirming next steps for each issue.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Prioritization, summarization, conversation control, follow-up planning, documentation, and expectation-setting.<\/span><\/p>\n<h4><strong>Scenario 8. Abusive or Inappropriate Customer Behavior<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">A customer becomes verbally abusive, uses inappropriate language, or crosses a professional boundary during the interaction. The agent\u2019s goal is to stay calm, set a clear boundary, and follow the company\u2019s escalation or interaction-closure policy.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cThis is ridiculous. You people are completely useless.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Maintain professionalism, set respectful communication boundaries, and continue support only if the interaction can proceed safely.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Stay calm and professional.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Matching the customer\u2019s tone or arguing back.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the issue without accepting abusive behavior.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ignoring abusive language if policy requires a warning.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Set a clear boundary using approved language.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Threatening the customer or sounding punitive.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Redirect the conversation back to the issue.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Continuing indefinitely if the customer remains abusive.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Escalate or end the interaction according to company policy.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Handling unsafe behavior without documenting it.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Composure, boundary-setting, professionalism, policy adherence, safe escalation, and documentation.<\/span><\/p>\n<h4><strong>Scenario 9. Language Barrier or Accessibility Need<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">A customer needs extra support because of a language barrier, disability, assistive technology requirement, or difficulty understanding the instructions. The agent\u2019s goal is to make the interaction easier to follow and confirm the customer can complete the next step.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI\u2019m having trouble understanding these instructions. Can you explain it another way?\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Make the support experience clear, accessible, and manageable without making the customer feel rushed or dismissed.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Slow down and use plain language.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Repeating the same explanation louder or faster.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Break instructions into smaller steps.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Using jargon, acronyms, or unclear product terms.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Check understanding after each step.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Assuming the customer understands because they did not interrupt.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Offer approved accessibility or language support options when available.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Treating accessibility needs as an inconvenience.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Summarize the next step clearly before moving on.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ending the interaction without confirming completion or understanding.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Clarity, patience, inclusive communication, accessibility support, confirmation of understanding, and customer reassurance.<\/span><\/p>\n<h4><strong>Scenario 10. Escalation Handoff to Tier 2 or Technical Support<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">The issue cannot be resolved by the frontline agent and needs to be transferred to Tier 2, technical support, engineering, billing, or another specialist team. The agent\u2019s goal is to explain the handoff clearly, document the case context, and set expectations so the customer does not feel passed around.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cCan you transfer me to someone who can actually fix this?\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Escalate the issue with complete context while maintaining customer confidence and reducing the need for repeated explanations.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain why escalation is needed.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Making the customer feel dismissed or passed off.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document the issue, actions taken, and desired outcome.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Transferring without case notes.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Share what the next team will review or do.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Saying \u201csomeone will get back to you\u201d without detail.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Set expectations for timeline, channel, or follow-up process.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Overpromising resolution from the next team.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Reassure the customer that context will be passed along.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Forcing the customer to restart the conversation with the next team.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Handoff quality, documentation, expectation-setting, customer reassurance, escalation accuracy, and ownership.<\/span><\/p>\n<h3><b><a id=\"banking\"><\/a>Banking scenarios<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Support conversations in banking and financial services contact centers are high-stakes because customers are dealing with money, identity, credit, and financial security. Agents must be able to de-escalate quickly, verify identities, follow fraud and privacy protocols, and explain policies without increasing customer anxiety.<\/span><\/p>\n<h4><b>Scenario 11. A Customer Sees a Suspicious Transaction<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer notices a charge or withdrawal they do not recognize and is worried their account or card has been compromised. The agent\u2019s goal is to verify the customer\u2019s identity, gather transaction details, and follow the bank\u2019s fraud-reporting process.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cThere\u2019s a charge on my account that I don\u2019t recognize. Has someone stolen my card information?\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Help the customer report the suspicious transaction while following identity verification, fraud, and account security protocols.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the customer\u2019s concern and urgency.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Confirming sensitive account details before verification.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Complete required identity verification steps.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Telling the customer it is definitely fraud before investigation.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Ask for the transaction date, amount, merchant name, and account or card type.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Making promises about refunds, credits, or investigation outcomes.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Follow the approved process for reporting suspicious activity.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Skipping fraud-reporting steps to move faster.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain what happens next, including card lock, dispute review, provisional credit, or follow-up timelines if applicable.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving vague next steps like \u201csomeone will look into it.\u201d<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Verification accuracy, fraud protocol compliance, urgency, clarity, expectation-setting, and avoidance of unsafe account disclosures.<\/span><\/p>\n<h4><b>Scenario 12. A Customer Is Locked Out of Online Banking<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer cannot access online banking because of a password issue, multi-factor authentication failure, device change, or account lock. The agent\u2019s goal is to restore access safely while protecting the customer\u2019s account.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI can\u2019t log in to my online banking, and I need to transfer money today. Can you unlock it right now?\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Help the customer regain access without bypassing identity verification, authentication, or account security controls.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the urgency and explain that security verification is required.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Unlocking access before verifying identity.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Confirm whether the issue is password-related, MFA-related, device-related, or account-status related.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Asking the customer to share passwords, PINs, or full security answers aloud.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Walk the customer through the approved recovery flow.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Suggesting workarounds that bypass bank security controls.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain any waiting period, admin review, or additional authentication step.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Overpromising immediate access if security review is required.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Escalate if the lockout is linked to suspected fraud or failed verification.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Blaming the customer for failed login attempts.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Security compliance, verification accuracy, troubleshooting clarity, patience, and safe escalation.<\/span><\/p>\n<h4><b>Scenario 13. A Customer Is Upset About an Overdraft Fee<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer is frustrated after being charged an overdraft fee and believes the fee is unfair. The agent\u2019s goal is to acknowledge the concern, explain the policy clearly, and review any available resolution options.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cWhy did you charge me an overdraft fee? I deposited money the same day.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Explain the overdraft fee clearly, review the account timeline, and offer approved options without making unauthorized fee reversals.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the customer\u2019s frustration.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Saying \u201cthat\u2019s just the policy\u201d without explanation.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Review the transaction and deposit timing carefully.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Reversing a fee without confirming eligibility.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain how overdraft rules, posting order, cutoff times, or available balance apply.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Using confusing banking jargon.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Check whether the customer qualifies for a fee review, waiver, or account option.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Blaming the customer for the overdraft.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Offer prevention guidance if appropriate, such as alerts or account settings.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Overpromising that future fees will not occur.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Empathy, policy explanation, account review accuracy, resolution options, and responsible communication.<\/span><\/p>\n<h4><b>Scenario 14. A Customer Wants to Dispute a Charge on Their Card or Account<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer calls about a specific charge on their debit card, credit card, or bank account and wants to dispute it. The agent\u2019s goal is to confirm the details, identify the correct dispute path, and set expectations for review timelines.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cThere\u2019s a charge on my card that I didn\u2019t make. I want it removed from my account.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Start the correct dispute process while gathering required details and explaining what the customer can expect next.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Verify the customer\u2019s identity before discussing account activity.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Discussing transaction details before verification.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Confirm the transaction amount, date, merchant, and card or account involved.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Assuming the dispute will be approved.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Ask whether the card is still in the customer\u2019s possession and whether they recognize the merchant.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Telling the customer the charge will be removed immediately unless policy allows it.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain the dispute process, documentation needs, and review timeline.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Skipping required disclosures or compliance steps.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Follow the correct path for fraud, merchant dispute, duplicate charge, or billing error.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Treating every charge dispute as the same type of case.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Compliance, documentation quality, transaction-detail accuracy, expectation-setting, and dispute-path selection.<\/span><\/p>\n<h4><b>Scenario 15. A Customer Is Confused About Loan or Credit Card Terms<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer does not understand a loan, credit card, interest rate, repayment term, fee, or statement detail. The agent\u2019s goal is to explain the information clearly using approved language without giving unauthorized financial advice.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI don\u2019t understand why my payment changed. Can you explain what I\u2019m actually being charged for?\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Clarify the customer\u2019s account or product terms accurately while staying within approved communication and disclosure guidelines.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Ask which term, fee, rate, payment, or statement detail is unclear.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving personal financial advice outside the agent\u2019s role.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Use plain language to explain the relevant term or calculation.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Using technical terms without explanation.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Reference approved disclosures, statements, or policy language.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Speculating about future rates, approvals, or outcomes.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Confirm the customer understands before moving on.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Rushing through complex financial details.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Escalate to a licensed or specialist team if the question requires it.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Interpreting legal or financial terms beyond approved guidance.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Clarity, accuracy, responsible communication, disclosure adherence, customer understanding, and escalation judgment.<\/span><\/p>\n<h4><b>Scenario 16. A Customer Is Denied a Mortgage Loan<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer is upset after receiving a mortgage denial and wants the agent to explain or reverse the decision. The agent\u2019s goal is to respond with empathy, explain the next steps within approved guidelines, and route the customer to the right team or documentation.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI was denied my mortgage, and I don\u2019t understand why. I need someone to fix this.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Help the customer understand the approved next steps after a mortgage denial without making unauthorized promises or giving lending advice.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the disappointment and seriousness of the situation.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Saying or implying that the decision can be reversed on the call.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Confirm what information the agent is permitted to discuss.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sharing restricted credit, underwriting, or decisioning details without authorization.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Direct the customer to the official denial notice, reason codes, or appropriate lending team if applicable.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving personal advice on how to qualify for a loan.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain the appeal, reconsideration, documentation, or next-step process if one exists.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Speculating about underwriting decisions.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document the interaction and route the customer to the right specialist when needed.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sounding dismissive or treating the denial as a routine inconvenience.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Empathy, compliance, responsible communication, expectation-setting, escalation accuracy, and documentation quality.<\/span><\/p>\n<h3><b><a id=\"healthcare\"><\/a>Healthcare scenarios<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Healthcare support requires extra sensitivity because customers may be dealing with pain, fear, confusing bills, test results, prescriptions, or access to care. Agents must communicate with patience while following strict privacy, consent, and HIPAA-related requirements.<\/span><\/p>\n<h4><b>Scenario 17. A Patient Is Confused About a Medical Bill<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A patient does not understand a medical bill, insurance adjustment, copay, deductible, or out-of-pocket charge. The agent\u2019s goal is to explain the bill clearly, show patience, and help the patient understand the next step without giving incorrect financial or coverage information.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI don\u2019t understand why I\u2019m being charged this much. I thought my insurance covered this.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Explain the billing details in plain language while confirming what can be reviewed, corrected, or escalated.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge that medical bills can be confusing and stressful.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sounding dismissive or implying the patient should already understand the bill.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Verify the patient\u2019s identity before discussing billing details.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sharing billing or health information before verification.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Walk through the charge, insurance adjustment, copay, deductible, or balance due in simple terms.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Using billing jargon without explanation.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain whether the next step is payer review, billing correction, payment plan, or specialist follow-up.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Promising that insurance will cover or remove a charge.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Escalate to billing specialists when the issue requires deeper review.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving vague next steps like \u201ccall your insurance\u201d without context.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Billing explanation, patience, identity verification, sensitivity, clarity, and escalation judgment.<\/span><\/p>\n<h4><b>Scenario 18. A Patient Cannot Access Their Online Patient Portal<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A patient cannot log in to the patient portal, reset a password, complete MFA, view information, or use an accessibility feature. The agent\u2019s goal is to troubleshoot access while protecting patient privacy and making the steps easy to follow.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI can\u2019t get into my patient portal, and I need to see my appointment details.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Restore portal access through the approved support process without exposing protected health information or bypassing security controls.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the urgency, especially if the patient needs appointment, prescription, or care information.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Discussing protected health information before verification.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Complete required identity verification steps.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Resetting access without confirming the patient\u2019s identity.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Determine whether the issue is password, MFA, browser, device, permissions, or account-status related.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Assuming the patient is at fault or technically inexperienced.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Walk the patient through the approved recovery process step by step.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Rushing through instructions or using technical jargon.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Offer accessibility or alternate support options when available.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Leaving the patient without a clear next step if portal access cannot be restored immediately.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Privacy compliance, troubleshooting clarity, accessibility support, patience, verification accuracy, and safe escalation.<\/span><\/p>\n<h4><b>Scenario 19. A Patient Wants Test Results the Agent Cannot Share<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A patient calls asking for test results, lab results, imaging results, or clinical information that the support agent is not authorized to share. The agent\u2019s goal is to stay empathetic while following privacy, clinical communication, and escalation rules.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI can see that my test results are ready. Can you just tell me what they say?\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Protect patient privacy and clinical safety by routing the patient to the approved channel or care team for test result communication.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge that waiting for test results can be stressful.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Reading or interpreting test results if the agent is not authorized to do so.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Verify the patient\u2019s identity before discussing account or portal information.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sharing protected health information without verification.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain what information the agent can and cannot provide.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving clinical advice or interpreting medical terms.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Direct the patient to the appropriate provider, portal message, care team, or approved results process.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Saying \u201ceverything looks fine\u201d or \u201cyou should be worried\u201d based on visible information.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document the inquiry and escalate if the patient reports urgent symptoms or the process requires follow-up.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Leaving the patient without a clear next step.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> HIPAA-safe communication, privacy boundaries, empathy, next-step clarity, escalation judgment, and avoidance of unauthorized clinical guidance.<\/span><\/p>\n<h4><b>Scenario 20. A Caregiver Calls on Behalf of a Patient<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A caregiver, family member, or guardian calls to discuss a patient\u2019s appointment, bill, medication, portal access, or care information. The agent\u2019s goal is to verify consent or authorization before sharing information and to help within the allowed privacy boundaries.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI\u2019m calling for my father. He asked me to check his appointment and test results.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Confirm whether the caller is authorized to receive information and provide support without violating privacy or consent requirements.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the caregiver\u2019s intent to help.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sharing patient information before confirming authorization.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Verify the caller\u2019s identity and relationship to the patient according to policy.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Assuming a family member is automatically authorized.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Check consent, proxy access, power of attorney, guardian status, or approved caregiver permissions if applicable.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Discussing test results, diagnoses, prescriptions, or billing details outside approved access rules.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain what can be shared and what requires patient consent or a different process.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sounding accusatory when privacy rules limit the conversation.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Provide approved next steps for gaining access or routing the request.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ending the call without explaining how the caregiver can proceed appropriately.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Verification accuracy, consent handling, privacy compliance, empathy, boundary-setting, and next-step clarity.<\/span><\/p>\n<h3><b>Insurance scenarios<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Insurance support teams are often contacted after something has gone seriously wrong, such as a car accident, natural disaster, damaged property, or unexpected coverage issue. Agents must balance empathy with accuracy, helping customers navigate stressful moments while staying within policy, claims, documentation, and compliance requirements.<\/span><\/p>\n<h4><b>Scenario 21. A Policyholder Is Confused About Their Coverage<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A policyholder does not understand what their insurance policy covers, what is excluded, or why a deductible, limit, or condition applies. The agent\u2019s goal is to explain the policy in simple language without giving inaccurate coverage interpretations.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI thought my policy covered this. Why am I being told I may have to pay out of pocket?\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Explain coverage terms clearly, confirm what can be reviewed, and route the customer to the right claims or policy team when needed.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge that insurance terms can be confusing.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Using policy jargon without explanation.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Verify the customer and policy details before discussing coverage.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Confirming coverage before the policy and claim details are reviewed.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain relevant terms such as deductible, limit, exclusion, waiting period, or covered event in plain language.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving legal or claims advice outside approved guidance.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Clarify what the policy documents say and what still needs review.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Promising the claim will be paid or denied before review.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Escalate to a licensed agent, claims adjuster, or specialist if the question requires interpretation.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Leaving the customer without a clear next step.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Policy explanation, clarity, accuracy, verification, expectation-setting, and escalation judgment.<\/span><\/p>\n<h4><b>Scenario 22. A Customer Is Upset Their Claim Was Denied<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer is frustrated after receiving a claim denial and wants the agent to reverse the decision immediately. The agent\u2019s goal is to respond with empathy, explain the approved next steps, and avoid making promises outside the claims process.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI filed a claim because I needed help, and now you\u2019re telling me it was denied. This is unacceptable.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Acknowledge the customer\u2019s frustration, explain the denial review path, and guide them toward appeal, reconsideration, or documentation steps if available.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the stress and disappointment of a denied claim.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sounding dismissive or treating the denial as routine.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Verify the customer\u2019s identity and claim details.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sharing claim information before verification.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain what can be discussed based on the claim status and policy rules.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Saying the denial is wrong or promising reversal.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Clarify appeal, reconsideration, additional documentation, or review options if available.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving legal advice or personal opinions about the claim.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document the conversation and route the customer to the right claims team when needed.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ending the interaction without clear next steps.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Empathy, compliance, claim-process accuracy, expectation-setting, escalation judgment, and documentation quality.<\/span><\/p>\n<h4><b>Scenario 23. A Customer Needs Help Filing a Claim After an Accident<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer contacts support shortly after an accident and may be stressed, injured, or unsure what information is needed. The agent\u2019s goal is to guide the customer calmly through the first notice of loss or claim intake process.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI was just in an accident and I don\u2019t know what I\u2019m supposed to do next.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Help the customer begin the claim process calmly and accurately while prioritizing safety, required documentation, and next steps.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Start by checking whether the customer is safe or needs emergency assistance.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Jumping straight into forms before acknowledging the situation.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain the claim intake process one step at a time.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Overwhelming the customer with too many questions at once.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Collect required details such as date, location, parties involved, damage, photos, police report, or incident summary where applicable.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Asking for unnecessary or speculative details.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain what happens after the claim is filed.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Promising a payout, repair approval, or timeline that has not been confirmed.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document the claim accurately and provide the claim number or follow-up instructions.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Leaving the customer unsure about what happens next.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Calm guidance, empathy, claim intake accuracy, documentation quality, safety awareness, and expectation-setting.<\/span><\/p>\n<h4><b>Scenario 24. A Policyholder Wants to Lower Their Premium<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A policyholder says their premium is too high and wants help reducing the cost. The agent\u2019s goal is to explore approved options, explain trade-offs, and set expectations without making unsupported savings promises.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cMy premium is too expensive. What can you do to lower it?\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Help the customer understand available premium-reduction options while explaining how changes may affect coverage, deductibles, or eligibility.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the customer\u2019s cost concern.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Promising a lower premium before reviewing options.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Review approved options such as discounts, deductible changes, bundling, policy adjustments, or updated information where applicable.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Recommending changes without explaining coverage trade-offs.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain how each option may affect coverage, out-of-pocket costs, or future claims.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Pressuring the customer into reducing coverage.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Confirm whether the customer needs a licensed agent or specialist review.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving advice outside the agent\u2019s authorization.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document requested changes and next steps clearly.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Leaving the customer with unclear expectations about savings or eligibility.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Consultative support, expectation-setting, policy accuracy, responsible communication, and documentation.<\/span><\/p>\n<h4><b>Scenario 25. A Customer Missed a Payment and Fears Losing Coverage<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer missed an insurance payment and is worried their policy may lapse or already be canceled. The agent\u2019s goal is to reassure the customer, explain policy rules, and review payment or reinstatement options where available.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI missed my payment. Am I going to lose my coverage?\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Help the customer understand their payment status, coverage implications, and available next steps without misrepresenting policy rules.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the customer\u2019s concern and urgency.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Saying coverage is active or inactive before checking policy status.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Verify the customer and policy details.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Discussing payment or policy details before verification.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Review payment status, grace period, lapse status, cancellation notice, or reinstatement options where applicable.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Promising coverage continuation if policy rules do not allow it.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain payment options, deadlines, and next steps clearly.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Using unclear language about grace periods or reinstatement.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Escalate if the situation requires underwriting, billing, or licensed agent review.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Creating false reassurance or unnecessary panic.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Reassurance, policy-rule accuracy, payment-status review, clarity, escalation judgment, and compliance.<\/span><\/p>\n<h4><b>Scenario 26. Customer Requests a Policy Exception<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer asks the agent to make an exception to a policy rule, claim requirement, deadline, documentation request, fee, or coverage condition. The agent\u2019s goal is to show empathy while following approved exception or escalation procedures.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI know the deadline passed, but I need you to make an exception for me.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Explain what can and cannot be changed, document the customer\u2019s situation, and route the request through the approved exception process if one exists.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the customer\u2019s situation and why they are asking for flexibility.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Saying yes before confirming whether an exception is allowed.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Review the relevant policy rule, deadline, or documentation requirement.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Bypassing policy or compliance requirements.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain any approved exception, appeal, or review process.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Telling the customer \u201cthere\u2019s nothing we can do\u201d without checking the correct path.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document the context and supporting details accurately.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Making unauthorized promises about the outcome.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Escalate to the appropriate claims, policy, billing, or licensed team if required.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Treating the request casually when it has compliance implications.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Empathy, policy accuracy, boundary-setting, exception-path handling, documentation quality, and escalation judgment.<\/span><\/p>\n<h3><b><a id=\"retail\"><\/a>Retail and e-commerce scenarios<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Retail and e-commerce support teams deal with customers who expect fast answers on orders, returns, refunds, damaged products, discounts, and delivery issues. Agents must resolve problems efficiently while protecting margins, following return policies, and keeping a service issue from turning into a lost customer relationship.<\/span><\/p>\n<h4><b>Scenario 27. A Customer Wants to Return an Item Outside the Return Window<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer wants to return an item after the return period has ended and expects the agent to make an exception. The agent\u2019s goal is to explain the return policy clearly, show empathy, and offer approved alternatives where possible.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI know the return window ended last week, but I still want to return this. I barely used it.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Explain the return policy without sounding dismissive and check whether any approved alternatives are available.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the customer\u2019s request and disappointment.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Saying \u201cyou missed the window\u201d without explanation or empathy.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Verify the order date, return eligibility, item condition, and policy terms.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Approving a return without confirming eligibility.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain the return window and any exceptions in simple language.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Blaming the customer for not returning the item sooner.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Offer approved alternatives, such as exchange, store credit, warranty review, or escalation if applicable.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Making promises outside the return policy.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document the request and outcome clearly.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving vague next steps like \u201ctry contacting us again later.\u201d<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Policy communication, empathy, order review accuracy, alternative options, boundary-setting, and documentation.<\/span><\/p>\n<h4><b>Scenario 28. A Customer Received the Wrong Product<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer receives an item they did not order, such as the wrong size, color, model, quantity, or product. The agent\u2019s goal is to apologize, verify the order details, and guide the customer through the correction process.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI ordered a black jacket in medium, but I received a blue one in large. I need the right item sent.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Take ownership of the order error and help the customer receive the correct product with minimal effort.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Apologize for the incorrect item and acknowledge the inconvenience.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Making the customer feel responsible for proving the mistake.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Verify the order number, item received, and item originally purchased.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sending a replacement before confirming inventory or policy.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain the correction process, including replacement, return label, pickup, or refund if applicable.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving unclear instructions for returning the wrong product.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Confirm the next step and expected timeline.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Overpromising delivery dates that are not confirmed.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document the issue for fulfillment or warehouse review if needed.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ending the interaction without confirming the customer\u2019s preferred resolution.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Apology quality, order verification, ownership, resolution clarity, timeline accuracy, and documentation.<\/span><\/p>\n<h4><b>Scenario 29. A Package Says Delivered, but the Customer Never Received It<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer says the carrier marked the package as delivered, but they cannot find it. The agent\u2019s goal is to guide the customer through the investigation steps, check available order and shipping information, and set expectations for resolution.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cThe tracking says delivered, but I never received my package. Where is my order?\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Investigate the missing delivery while setting clear expectations for carrier review, replacement, refund, or next steps.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the customer\u2019s concern and urgency.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Assuming the customer misplaced the package.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Confirm the shipping address, delivery date, carrier, and tracking details.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Promising an immediate refund or replacement before checking policy.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Ask the customer to check approved locations, such as mailbox, front desk, parcel locker, or delivery photo if available.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sending the customer in circles between retailer and carrier.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain the investigation process and expected timeline.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving vague answers like \u201cwait a few more days\u201d without context.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document the case and follow the approved path for carrier claim, replacement, or refund.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Failing to set a clear follow-up or resolution path.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Investigation accuracy, empathy, expectation-setting, policy adherence, carrier-process clarity, and follow-up quality.<\/span><\/p>\n<h4><b>Scenario 30. A Customer Is Angry About a Discount Code That Failed<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer tried to use a discount code during checkout, but it did not apply or expired before purchase. The agent\u2019s goal is to troubleshoot the issue, explain eligibility rules, and offer approved resolution options.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cYour discount code didn\u2019t work, and now I\u2019ve been charged full price. I want the discount applied.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Determine why the code failed and resolve the issue fairly within promotion rules and approved support policy.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the frustration and ask for the code or promotion details.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Assuming the customer used the code incorrectly.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Check expiration date, product eligibility, account eligibility, minimum cart value, and exclusions.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Applying discounts outside approved promotion rules.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain why the code did or did not apply in clear terms.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Using vague phrases like \u201cthe system rejected it.\u201d<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Offer approved options, such as price adjustment, store credit, alternate code, or escalation if applicable.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Promising a discount before confirming eligibility.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document the issue if the code failed due to a technical or checkout problem.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ignoring patterns that may indicate a promotion setup issue.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Troubleshooting, fairness, promotion-policy accuracy, clarity, resolution options, and documentation.<\/span><\/p>\n<h4><b>Scenario 31. A Customer Received a Damaged Product<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer receives an item that is broken, defective on arrival, leaking, torn, cracked, or otherwise damaged. The agent\u2019s goal is to acknowledge the issue, collect required evidence, and move quickly toward replacement, refund, or claim review.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cMy order arrived damaged. I waited a week for this, and now I can\u2019t even use it.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Resolve the damaged-product issue quickly while following evidence, replacement, refund, or shipping-claim requirements.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Apologize for the damaged delivery and acknowledge the inconvenience.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Making the customer feel blamed for the damage.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Verify the order, item, delivery date, and damage details.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Asking for unnecessary information that slows resolution.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Request required photos or evidence if policy requires it.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Promising replacement or refund before confirming eligibility.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain the next step, such as replacement, refund, return, disposal instructions, or carrier claim.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Leaving the customer unclear on whether they need to return the damaged item.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Escalate urgent or high-value cases according to policy.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Delaying resolution without explaining why.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Empathy, speed, evidence collection, policy accuracy, replacement-process clarity, and ownership.<\/span><\/p>\n<h4><b>Scenario 32. Refund Request Outside Policy<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer asks for a refund even though the order, item, condition, time window, or reason does not meet the company\u2019s standard refund policy. The agent\u2019s goal is to explain the policy clearly and offer any approved alternatives without escalating unnecessarily.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI want my money back. I don\u2019t care what your refund policy says.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Set a clear boundary around refund eligibility while preserving the customer relationship through approved options.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the customer\u2019s frustration.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Starting with a blunt refusal.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Review the order, purchase date, item condition, return history, and refund eligibility.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Issuing refunds outside policy to end the conversation quickly.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain the specific reason the refund is outside policy.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Using policy language that sounds cold or confusing.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Offer approved alternatives, such as exchange, store credit, warranty review, repair, replacement, or escalation if applicable.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Saying there are no options without checking.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document the decision and any alternative offered.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving inconsistent answers across channels.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Empathy, refund-policy accuracy, boundary-setting, alternative options, consistency, and documentation.<\/span><\/p>\n<h4><b>Scenario 33. Product Defect or Service Failure<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer reports that a product stopped working, did not perform as described, or failed after purchase. The agent\u2019s goal is to determine whether the issue is a defect, misuse, shipping damage, warranty case, or service failure, then route the customer to the right resolution path.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI bought this product two weeks ago, and it already stopped working. I want this fixed.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Gather the right details, identify the correct resolution path, and set expectations for repair, replacement, warranty review, refund, or escalation.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the customer\u2019s disappointment.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Assuming the customer damaged or misused the product.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Confirm order details, product model, purchase date, issue description, and usage context.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Treating every product issue as a standard return.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Check warranty, defect, service, or troubleshooting policy.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Promising replacement or refund before confirming eligibility.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Guide the customer through approved troubleshooting or evidence steps if needed.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Making the customer repeat information already captured.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Route the case to warranty, technical, repair, or specialist support when required.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ending the interaction without explaining the next step or timeline.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Issue intake, product knowledge, troubleshooting clarity, warranty or policy accuracy, expectation-setting, and escalation judgment.<\/span><\/p>\n<h3><b><a id=\"saas\"><\/a>SaaS provider scenarios<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">SaaS and IT technology support teams help users who may be blocked from doing their jobs because of bugs, login issues, confusing workflows, integrations, outages, or product changes. Agents must diagnose problems clearly, translate technical details into plain language, and set realistic expectations when fixes require escalation.<\/span><\/p>\n<h4><b>Scenario 34. A Customer Is Angry About the Platform Being Down<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer cannot access the SaaS platform or a critical feature, and the downtime is disrupting their work. The agent\u2019s goal is to acknowledge the urgency, determine whether the issue is isolated or part of a broader incident, and guide the customer to the right next step.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cYour platform is down again, and my team can\u2019t get any work done. What is going on?\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Triage the issue quickly, share confirmed information, and prioritize the case appropriately without guessing or overpromising.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the disruption and business impact.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Minimizing the issue or treating it like a routine question.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Check whether there is a known incident, degraded service, or account-specific issue.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Stating a root cause before it is confirmed.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Ask targeted questions about login status, affected users, error messages, location, browser, or feature area.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Asking the customer to perform unnecessary steps during a known outage.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Share any approved status update, workaround, or escalation path.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving an unconfirmed resolution timeline.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document business impact and route urgent cases based on severity rules.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Leaving the customer without a status page, case number, or follow-up path.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Urgency, troubleshooting accuracy, incident communication, prioritization, expectation-setting, and documentation quality.<\/span><\/p>\n<h4><b>Scenario 35. A Customer Reports a Bug That Cannot Be Fixed Immediately<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer reports a product bug that blocks or disrupts their workflow, but the support agent cannot resolve it during the interaction. The agent\u2019s goal is to gather complete details, document impact, explain next steps, and route the case appropriately.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cThis bug is breaking our workflow. I need you to fix it right now.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Capture enough technical and business context for escalation while setting realistic expectations about investigation and resolution.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the customer\u2019s frustration and workflow impact.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Saying \u201cthere\u2019s nothing I can do\u201d because the issue needs engineering review.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Collect reproduction steps, screenshots, error messages, affected users, environment, browser, integration, and frequency.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Asking for vague details that engineering cannot act on.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Check whether the bug is known, newly reported, or linked to a recent release.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Promising a fix date before it is confirmed.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Offer any approved workaround while the issue is investigated.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Hiding uncertainty or implying the bug is already solved.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Escalate with severity, impact, and complete notes.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Closing the case without a clear follow-up plan.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Transparency, technical intake quality, impact capture, workaround guidance, escalation accuracy, and expectation-setting.<\/span><\/p>\n<h4><b>Scenario 36. An Angry Customer After a Data Breach<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer is concerned that their data, users, or account may have been exposed after a suspected or confirmed security incident. The agent\u2019s goal is to respond with urgency, follow the approved incident communication process, and avoid sharing unverified or unauthorized information.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI heard there was a data breach. Was our account affected, and what are you doing about it?\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Provide approved security-incident guidance, protect sensitive information, and route the customer to the correct security or account team.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the seriousness of the concern.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Speculating about what happened or who was affected.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Verify the customer\u2019s identity and account permissions before discussing account-specific details.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sharing security, customer, or incident details before verification.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Use only approved incident messaging and escalation paths.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving personal interpretations of breach scope, cause, or liability.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain where the customer can find official updates or who will follow up.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Making unauthorized promises about remediation, compensation, or timelines.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Escalate to security, legal, privacy, or account teams when required.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Treating the issue like a standard support ticket without proper routing.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Urgency, security protocol adherence, privacy boundaries, approved communication, escalation judgment, and customer reassurance.<\/span><\/p>\n<h4><b>Scenario 37. Confused Customer During Onboarding<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A new customer is trying to set up the SaaS product but does not understand the next step, workflow, configuration, or required input. The agent\u2019s goal is to simplify the process, guide the customer through the immediate next action, and reduce onboarding friction.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI\u2019m new to this platform and I don\u2019t understand what I\u2019m supposed to do next.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Help the customer complete the next onboarding step clearly and confidently without overwhelming them with too much information.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Confirm where the customer is in the onboarding or setup flow.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Assuming the customer understands product terms or setup logic.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Break the workflow into one step at a time.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Explaining the entire product before solving the immediate issue.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Use plain language to explain required fields, permissions, integrations, or configuration choices.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Using internal product jargon.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Share relevant help resources or guided steps if available.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sending a long documentation link without explaining what to do next.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Confirm the customer completed the step and knows what comes next.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ending the interaction before confirming progress.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Clarity, product knowledge, patience, workflow guidance, confirmation of understanding, and onboarding support quality.<\/span><\/p>\n<h4><b>Scenario 38. Customer Requests a Feature Not Available<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer asks for a feature, integration, report, configuration option, or workflow capability the SaaS product does not currently support. The agent\u2019s goal is to set clear expectations, identify any workaround, and capture the customer\u2019s use case for product feedback.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cWhy doesn\u2019t your platform support this feature? We need it for our team.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Respond honestly without overpromising, offer approved alternatives, and document the business need behind the request.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the customer\u2019s need and ask about the use case.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Saying \u201cthat\u2019s not possible\u201d without exploring the goal behind the request.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Confirm whether the feature, integration, or configuration is currently available.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Suggesting unofficial workarounds that may create risk.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Offer approved alternatives, existing settings, APIs, integrations, reports, or process workarounds if available.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Promising the feature will be added to the roadmap.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Capture the customer\u2019s workflow, business impact, and desired outcome for product feedback.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Logging vague feedback with no context.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Set expectations on how feature requests are reviewed or followed up.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Implying the request will be prioritized without confirmation.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Expectation-setting, product knowledge, workaround quality, feedback capture, honesty, and customer reassurance.<\/span><\/p>\n<h4><b>Scenario 39. High-Value Customer Threatening to Churn<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A strategic customer says they may cancel, downgrade, or move to a competitor because of product issues, poor support, missing functionality, or unresolved escalations. The agent\u2019s goal is to capture the business impact, de-escalate the conversation, and route the case with the urgency it deserves.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cIf this does not get fixed, we\u2019re moving to another provider.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Preserve the relationship by acknowledging the risk, documenting the impact, and involving the right support, success, or account team.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the seriousness of the concern.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Treating the threat to churn like a routine complaint.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Ask what issue is driving the risk and how it affects the customer\u2019s business.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Becoming defensive about the product or support history.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Review existing tickets, prior escalations, account context, and open commitments.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Making promises to retain the customer without approval.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Route the case to the right support, customer success, account, or leadership team.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Letting the issue stay in a standard queue if it requires priority handling.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document business impact, urgency, requested outcome, and next step.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ending the interaction without ownership or follow-up.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Urgency, empathy, account awareness, business impact capture, escalation quality, and ownership.<\/span><\/p>\n<h3><b><a id=\"telecom\"><\/a>Telecom and utilities scenarios<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Telecommunications and utilities support conversations can become tense quickly because customers rely on these services for work, safety, communication, and daily life. Agents must handle outage complaints, billing disputes, technician delays, and cancellation risks with clear explanations, calm escalation, and precise expectation-setting.<\/span><\/p>\n<h4><b>Scenario 40. Internet or Service Outage<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer has lost internet, phone, electricity, gas, water, or another essential service and wants to know when service will be restored. The agent\u2019s goal is to acknowledge the disruption, check outage information, and set realistic expectations.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cMy service is down, and I need it back immediately. When will this be fixed?\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Communicate outage status clearly, explain available next steps, and avoid giving unconfirmed restoration timelines.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the disruption and its impact on the customer\u2019s day.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Minimizing the issue or treating it like a minor inconvenience.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Check whether there is a known outage, localized issue, or account-specific problem.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Guessing the cause or restoration time.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Share the latest confirmed update and any available estimated restoration window.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving a firm timeline if one has not been confirmed.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain any troubleshooting steps or workaround only if relevant.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Asking the customer to troubleshoot during a confirmed area outage.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Provide the status page, notification option, case number, or follow-up path.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ending the conversation without explaining how the customer will receive updates.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Outage communication, accuracy, empathy, expectation-setting, troubleshooting judgment, and follow-up clarity.<\/span><\/p>\n<h4><b>Scenario 41. A Customer Is Angry About a Higher-Than-Expected Bill<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer receives a telecom or utility bill that is higher than expected and believes they were overcharged. The agent\u2019s goal is to review the bill, explain the charges clearly, and de-escalate the conversation.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cMy bill is much higher than usual. I need you to explain why I\u2019m being charged this much.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Help the customer understand the bill and identify whether the increase is due to usage, fees, taxes, plan changes, equipment charges, late payments, or billing errors.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the customer\u2019s concern about the unexpected charge.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Saying the bill is correct before reviewing it.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Verify the customer and account details before discussing billing information.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sharing billing details before verification.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Break down the bill line by line in simple language.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Using billing codes, tax terms, or plan language without explanation.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Check for usage spikes, proration, promotions ending, late fees, equipment charges, or errors.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Blaming the customer for higher usage or missed details.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Offer approved options such as billing correction, payment plan, plan review, or escalation.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Promising a credit or adjustment before confirming eligibility.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Billing explanation, de-escalation, account review accuracy, clarity, resolution options, and expectation-setting.<\/span><\/p>\n<h4><b>Scenario 42. A Technician Missed a Scheduled Appointment<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer waited for a technician who did not arrive during the scheduled service window. The agent\u2019s goal is to apologize, investigate the missed appointment, reschedule service, and offer any approved service recovery options.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI took time off work, and your technician never showed up. This is unacceptable.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Take ownership of the missed appointment, explain the next available option, and reduce the customer\u2019s effort to reschedule.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Apologize for the missed appointment and acknowledge the inconvenience.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Blaming the technician, dispatch team, or customer.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Review appointment notes, technician status, access issues, and service-window details.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Rescheduling without checking why the appointment was missed.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain what happened if confirmed information is available.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Guessing why the technician did not arrive.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Offer the earliest available reschedule or escalation path.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Making the customer restart the entire scheduling process.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Share any approved credit, priority scheduling, or service recovery option if applicable.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Promising special treatment outside approved policy.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Apology quality, ownership, scheduling accuracy, service recovery, expectation-setting, and documentation.<\/span><\/p>\n<h4><b>Scenario 43. A Customer Wants to Cancel After Repeated Service Issues<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer wants to cancel service because they have experienced repeated outages, poor signal, technician delays, unresolved billing issues, or unsatisfactory support. The agent\u2019s goal is to understand the customer\u2019s reason, acknowledge the history, and route the case through the correct retention or cancellation process.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cI\u2019ve had enough. I want to cancel because this service keeps failing.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Understand the root cause of the cancellation risk, offer approved resolution or retention options, and process cancellation correctly if the customer chooses to proceed.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge the repeated frustration and ask what led to the cancellation decision.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Pressuring the customer to stay before understanding the issue.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Review prior outages, tickets, technician visits, billing disputes, or service credits.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ignoring the customer\u2019s support history.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Offer approved retention, service review, plan adjustment, technician escalation, or credit options if available.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Making unauthorized promises to prevent cancellation.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain cancellation terms, equipment return, final bill, or contract implications clearly.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Hiding fees, contract terms, or next steps.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Document the reason for cancellation or retention outcome.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Treating churn risk as a routine transaction with no context capture.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Empathy, retention judgment, account history review, policy clarity, escalation accuracy, and documentation.<\/span><\/p>\n<h4><b>Scenario 44. A Customer Does Not Understand Usage-Based Charges<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A customer is confused by usage-based telecom or utility charges, such as data overages, roaming, energy consumption, peak-time usage, water usage, or meter-based billing. The agent\u2019s goal is to explain usage clearly and help the customer understand how to monitor or manage future charges.<\/span><\/p>\n<p><b>Customer says:<\/b><span style=\"font-weight: 400;\"> \u201cWhy am I being charged extra? I don\u2019t understand where this usage came from.\u201d<\/span><\/p>\n<p><b>Agent goal:<\/b><span style=\"font-weight: 400;\"> Explain the usage-based charge in plain language and provide approved guidance for monitoring or reducing future usage.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>What agents should do<\/b><\/td>\n<td><b>Agents should avoid<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Acknowledge that usage-based charges can be confusing.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Assuming the customer knowingly exceeded limits.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Verify the account, billing cycle, usage period, and charge type.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Discussing account or billing details before verification.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Explain how the charge was calculated using simple terms.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Using technical meter, data, or tariff language without explanation.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Point to usage alerts, account dashboards, meter readings, plan options, or conservation tools if available.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Giving vague advice like \u201cjust use less.\u201d<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Offer approved plan review, billing review, or escalation if the customer disputes the usage.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Promising that charges will be removed without checking eligibility.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>Evaluate Criteria:<\/b><span style=\"font-weight: 400;\"> Usage explanation, billing transparency, clarity, account review accuracy, prevention guidance, and escalation judgment.<\/span><\/p>\n<h2><b>What Makes an Effective Roleplay Scenario?<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Traditional training often leans on passive instruction, slide-based learning, and memorized responses. Roleplay is more effective because agents have to make decisions, respond to customer inputs, and practice the workflows they will use in real support situations. The <\/span><a href=\"https:\/\/whatfix.com\/blog\/70-20-10-model\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">70-20-10 learning model<\/span><\/a><span style=\"font-weight: 400;\"> reinforces this idea: most workplace learning comes from <\/span><a href=\"https:\/\/whatfix.com\/blog\/hands-on-training\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">hands-on training<\/span><\/a><span style=\"font-weight: 400;\">, while formal instruction plays a smaller supporting role.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">High-impact customer support roleplay scenarios should include:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>System simulation that mirrors real workflows:<\/b><span style=\"font-weight: 400;\"> The scenario should reflect the systems agents use during live support, such as CRM, ticketing, billing, knowledge base, claims, portal, or order management tools.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Adaptive AI that responds to agent inputs:<\/b><span style=\"font-weight: 400;\"> AI roleplay can simulate different customer moods, objections, follow-up questions, and escalation paths based on how the agent responds.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Clear escalation paths:<\/b><span style=\"font-weight: 400;\"> The scenario should define when the agent can resolve the issue independently and when it needs escalation to a manager, specialist, fraud team, billing team, care team, or technical team.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Defined success criteria:<\/b><span style=\"font-weight: 400;\"> Each scenario should be scored against clear readiness criteria, such as empathy, issue diagnosis, policy accuracy, workflow completion, documentation quality, escalation judgment, and next-step clarity.<\/span><\/li>\n<\/ul>\n<h2><b>Best Practices for Creating Roleplay Training Programs for Support Teams<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Customer support roleplay works best when each scenario is treated as a structured practice exercise. Support enablement managers and L&amp;D teams should connect every scenario to a real support risk, a clear agent objective, and a measurable readiness outcome.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Follow this process to turn each scenario into a repeatable training exercise:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Choose scenarios based on real support risks.<\/b><span style=\"font-weight: 400;\"> Use ticket trends, QA findings, escalation patterns, customer complaints, product updates, and policy changes to decide what agents should practice.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Define what the agent needs to demonstrate.<\/b><span style=\"font-weight: 400;\"> The objective could be de-escalating an angry customer, explaining a billing decision, resolving a technical issue, completing account verification, or handing off a case to Tier 2 support.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Add the workflow step.<\/b><span style=\"font-weight: 400;\"> Connect the conversation to the task the agent must complete, such as updating a CRM record, creating a ticket, checking a knowledge base article, verifying account details, or documenting an escalation.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Run the scenario in the right channel.<\/b><span style=\"font-weight: 400;\"> Practice through the same channel agents use in live support, such as phone, chat, email, social, or in-app support.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Score, coach, and repeat.<\/b><span style=\"font-weight: 400;\"> Evaluate the agent\u2019s response, coach the specific gap, and repeat the scenario until the agent can complete both the conversation and the workflow accurately.<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">Use this rubric to evaluate whether agents can handle the customer conversation, follow the right process, and complete the required support workflow.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Scoring Area<\/b><\/td>\n<td><b>What to Assess<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Empathy and tone<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Did the agent acknowledge the customer\u2019s emotion and respond professionally?<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Issue diagnosis<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Did the agent understand the real problem before offering a solution?<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Policy accuracy<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Did the agent follow approved policies, rules, and exception paths?<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Resolution ownership<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Did the agent clearly explain the next step and take responsibility for follow-through?<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Workflow accuracy<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Did the agent complete the correct CRM, ticketing, billing, knowledge base, or product workflow?<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Escalation judgment<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Did the agent know when to resolve the issue and when to escalate it?<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Documentation quality<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Did the agent capture enough context for reporting, follow-up, or handoff?<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">Over time, roleplay scores should connect back to support performance metrics such as time-to-proficiency, first-contact resolution, escalation rate, average handle time, QA score, CSAT, repeat contact rate, and case documentation quality.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This helps managers see which agents are ready, which scenarios need more practice, and which workflows need better training or support.<\/span><\/p>\n<h2><b>4 Methods for Delivering Roleplay Scenarios<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Manual roleplay and static scripts still have a place in customer support training, but they become harder to scale when teams need consistent practice across agents, locations, support channels, and product changes.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Training Method<\/b><\/td>\n<td><b>What It Helps With<\/b><\/td>\n<td><b>Where It Falls Short<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Manual roleplay<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Live coaching, manager feedback, and discussion-based practice<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Depends on trainer availability and can vary by team<\/span><\/td>\n<\/tr>\n<tr>\n<td><a href=\"https:\/\/whatfix.com\/blog\/call-center-scripts\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">Static call center scripts<\/span><\/a><\/td>\n<td><span style=\"font-weight: 400;\">Standardizing approved responses and support language<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Gives limited practice for unpredictable customer emotions, edge cases, or policy exceptions<\/span><\/td>\n<\/tr>\n<tr>\n<td><a href=\"https:\/\/whatfix.com\/blog\/ai-scenario-training\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">AI roleplay<\/span><\/a><\/td>\n<td><span style=\"font-weight: 400;\">Practicing different customer moods, objections, escalation requests, and issue types repeatedly<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Works best when scenarios are reviewed and aligned with real support policies<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Simulated workflows and <\/span><a href=\"https:\/\/whatfix.com\/blog\/in-app-guidance\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">in-app guidance<\/span><\/a><\/td>\n<td><span style=\"font-weight: 400;\">Practicing the CRM, ticketing, billing, knowledge base, or product steps agents complete during support<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Works best when paired with realistic customer scenarios<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">The strongest support training combines conversation readiness with workflow readiness. AI roleplay helps agents practice what to say and how to respond, while simulated workflows help them practice what to do inside the systems they use during live support.<\/span><\/p>\n<h2><b>How Whatfix Helps Support Teams Turn Roleplay Scenarios Into Agent Readiness<\/b><\/h2>\n<p>Roleplay scenarios help agents prepare for the customer situations they will face on the job. <a href=\"https:\/\/whatfix.com\/?utm_source=blog&amp;utm_medium=link&amp;utm_campaign=simulation_training&amp;utm_term=whatfix&amp;utm_content=roleplay_scenario\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">Whatfix<\/span><\/a> helps support teams take that practice further by turning roleplay into a measurable agent readiness program.<\/p>\n<p>With Whatfix, teams can train agents on both sides of the support interaction. Agents can practice the application workflows they need to complete and the customer conversations they need to handle, before they move into live support environments.<\/p>\n<h3>Train Agents on the System and the Conversation Together<\/h3>\n<p>Support agents rarely handle customer conversations in isolation. They need to listen, diagnose the issue, navigate internal systems, follow policies, document the case, and resolve the request at the same time.<\/p>\n<p>Whatfix helps teams recreate this real support environment through a combination of application simulation and AI-powered roleplay. Agents can practice workflows such as verifying an account, checking order status, processing a refund, updating a case, handling a billing dispute, or escalating an issue while also responding to a realistic customer conversation.<\/p>\n<p>This helps agents build workflow accuracy, conversation confidence, and decision-making skills before they support real customers.<\/p>\n<p><img fetchpriority=\"high\" decoding=\"async\" class=\"alignnone size-large wp-image-90815\" src=\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2023\/06\/image6-1-1024x888.png\" alt=\"whatfix banking apps AI roleplay\" width=\"1024\" height=\"888\" srcset=\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2023\/06\/image6-1-1024x888.png 1024w, https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2023\/06\/image6-1-300x260.png 300w, https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2023\/06\/image6-1-768x666.png 768w, https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2023\/06\/image6-1.png 1255w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/p>\n<h3><strong>Practice Support Workflows in Replicated Application Environments<\/strong><\/h3>\n<p><a href=\"https:\/\/whatfix.com\/products\/mirror\/?utm_source=blog&amp;utm_medium=link&amp;utm_campaign=simulation_training&amp;utm_term=mirror&amp;utm_content=roleplay_scenario\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">Whatfix Mirror<\/span><\/a> helps teams create replicated versions of CRM, ticketing, billing, product, claims, order management, or knowledge base systems where agents can practice workflows without using live systems or customer data.<\/p>\n<p class=\"isSelectedEnd\">Agents can build hands-on familiarity with the screens, fields, process steps, and exception paths they will use during real customer interactions. This is especially useful for high-volume or high-risk workflows such as account verification, refund approvals, claims intake, case documentation, appointment scheduling, and escalation handoffs.<\/p>\n<p>By giving agents a safe place to practice, support teams can reduce live-environment risk and improve readiness before agents enter production.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-69661\" src=\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2024\/06\/Whatfix-Mirror-Capture-Screen-GIF.gif\" alt=\"Whatfix-Mirror-Capture-Screen-GIF\" width=\"600\" height=\"381\" \/><\/p>\n<h3><b>Scale Customer Conversation Practice With AI Roleplay<\/b><\/h3>\n<p><a href=\"https:\/\/whatfix.com\/ai\/?utm_source=blog&amp;utm_medium=link&amp;utm_campaign=simulation_training&amp;utm_term=AI&amp;utm_content=roleplay_scenario\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">AI roleplay<\/span><\/a> helps agents rehearse realistic customer conversations, objections, escalation requests, frustrated customers, compliance-sensitive moments, and complex issue types through repeatable practice.<\/p>\n<p>Support enablement teams can create roleplay scenarios for different products, customer segments, regions, policies, and support channels. Agents can then practice how to respond with the right tone, empathy, accuracy, and resolution approach.<\/p>\n<p>This gives teams a scalable way to prepare agents for high-pressure customer interactions without relying only on live shadowing, manager-led practice, or peer coaching.<\/p>\n<h3>Assess Agents Before Live Customer Interactions<\/h3>\n<p>Practice becomes more valuable when support leaders can measure whether agents are ready.<\/p>\n<p>With Whatfix assessments and analytics, teams can validate whether agents can complete required workflows, follow the right process, respond appropriately to customer scenarios, and meet readiness criteria before they support live customers.<\/p>\n<p>Teams can track assessment attempts, pass rates, completion rates, workflow-level performance, and learner progress. These insights help managers identify which agents are ready, which agents need more coaching, and which workflows or scenarios need additional training coverage.<\/p>\n<p>This helps support teams move from training completion to readiness proof.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-89732\" src=\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2024\/10\/Frame-2018776245-1.png\" alt=\"Mirror-AI-scenario-assessments\" width=\"789\" height=\"570\" srcset=\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2024\/10\/Frame-2018776245-1.png 789w, https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2024\/10\/Frame-2018776245-1-300x217.png 300w, https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2024\/10\/Frame-2018776245-1-768x555.png 768w\" sizes=\"(max-width: 789px) 100vw, 789px\" \/><\/p>\n<h3><strong>Guide Agents Through Live Support Workflows<\/strong><\/h3>\n<p>After agents move into production, <a href=\"https:\/\/whatfix.com\/products\/digital-adoption-platform\/\"><span style=\"font-weight: 400;\">Whatfix DAP<\/span><\/a> provides step-by-step in-app guidance inside the tools agents use every day.<\/p>\n<p>Teams can guide agents through workflows where accuracy and consistency matter, including identity verification, refund approvals, case categorization, troubleshooting steps, escalation handoffs, compliance scripts, and post-call documentation.<\/p>\n<p>This helps agents follow the right process in the flow of work, especially during onboarding, product launches, policy updates, process changes, or high-volume support periods.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-50024\" src=\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2023\/07\/image08.gif\" alt=\"whatfix flow\" width=\"512\" height=\"360\" \/><\/p>\n<h3><b>Give Agents Contextual Answers With Self Help<\/b><\/h3>\n<p class=\"isSelectedEnd\">Whatfix Self Help brings SOPs, policies, knowledge base articles, process guides, troubleshooting resources, and support documentation into the agent\u2019s workflow.<\/p>\n<p class=\"isSelectedEnd\">Agents can find answers while working inside the application, reducing dependency on managers, peers, side-by-side support, or separate documentation tabs.<\/p>\n<p>This helps support teams reduce internal \u201chow-to\u201d questions and gives agents faster access to the information they need during customer interactions.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-88389\" src=\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2019\/08\/image3.png\" alt=\"Whatfix self help\" width=\"632\" height=\"434\" srcset=\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2019\/08\/image3.png 632w, https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2019\/08\/image3-300x206.png 300w\" sizes=\"(max-width: 632px) 100vw, 632px\" \/><\/p>\n<h3><b>Reinforce Product, Policy, and Process Changes<\/b><\/h3>\n<p class=\"isSelectedEnd\">Contact center teams deal with constant change, including product releases, pricing updates, policy changes, new escalation rules, compliance updates, and revised support workflows.<\/p>\n<p class=\"isSelectedEnd\">Whatfix helps teams communicate and reinforce these changes directly inside the tools agents use. Teams can update guidance, Self Help content, and training simulations as processes change, helping agents adapt faster and keeping enablement content aligned with current workflows.<\/p>\n<p>This reduces the risk of outdated process knowledge showing up in live customer conversations.<\/p>\n<h3><b>Identify Agent Readiness and Workflow Gaps With Analytics<\/b><\/h3>\n<p><a href=\"https:\/\/whatfix.com\/products\/product-analytics\/?utm_source=blog&amp;utm_medium=link&amp;utm_campaign=simulation_training&amp;utm_term=analytics&amp;utm_content=roleplay_scenario\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">Whatfix Product Analytics<\/span><\/a>, guidance analytics, and assessment analytics help leaders understand where agents struggle, which workflows create friction, and where additional coaching or in-app support is needed.<\/p>\n<p>Support teams can identify workflow drop-offs, repeated help searches, incomplete assessments, low-performing scenarios, and cohort-level readiness gaps. These insights help teams improve roleplay scenarios, update training content, prioritize coaching, and focus enablement efforts on the workflows that have the greatest impact on support performance.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-88014\" src=\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2022\/04\/product-analytics.png\" alt=\"\" width=\"960\" height=\"609\" srcset=\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2022\/04\/product-analytics.png 960w, https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2022\/04\/product-analytics-300x190.png 300w, https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2022\/04\/product-analytics-768x487.png 768w\" sizes=\"(max-width: 960px) 100vw, 960px\" \/><\/p>\n<p>By connecting simulated practice, AI roleplay, assessments, in-flow support, Self Help, and analytics, Whatfix helps support teams improve the metrics that matter most in contact centers, including time-to-proficiency, first contact resolution, average handle time, escalation rate, QA consistency, CSAT, and agent confidence.<\/p>\n<p><span style=\"font-weight: 400;\"><a href=\"https:\/\/whatfix.com\/request-demo\/?utm_source=blog&amp;utm_medium=link&amp;utm_campaign=simulation_training&amp;utm_term=demo&amp;utm_content=roleplay_scenario\" target=\"_blank\" rel=\"noopener\">Request a demo<\/a> to see how Whatfix helps support teams turn roleplay scenarios into measurable agent readiness.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Research on simulation-based training found that scenario-based learning significantly improved teamwork and communication compared with traditional approaches, with roleplay participants performing roughly in the 66th percentile for teamwork and 70th&#8230;<\/p>\n","protected":false},"author":73,"featured_media":78883,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[785,18],"tags":[934,999,1001],"class_list":["post-78882","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-support","category-employee-training","tag-call-center","tag-customer-experience","tag-support"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>44 Roleplaying Scenario Examples for Support Teams (+Scripts)<\/title>\n<meta name=\"description\" content=\"Explore 40+ examples of roleplay scenarios for frontline teams and support agents to help build readiness and prepare them for real work.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"44 Roleplaying Scenario Examples for Support Teams (+Scripts)\" \/>\n<meta property=\"og:description\" content=\"Explore 40+ examples of roleplay scenarios for frontline teams and support agents to help build readiness and prepare them for real work.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/\" \/>\n<meta property=\"og:site_name\" content=\"The Whatfix Blog | Drive Digital Adoption\" \/>\n<meta property=\"article:published_time\" content=\"2024-10-03T18:32:29+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-06-09T16:10:29+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2024\/10\/role-playing-scenarios-for-customer-support.png\" \/>\n\t<meta property=\"og:image:width\" content=\"791\" \/>\n\t<meta property=\"og:image:height\" content=\"488\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Samantha Rohn\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Samantha Rohn\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"49 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/\"},\"author\":{\"name\":\"Samantha Rohn\",\"@id\":\"https:\/\/whatfix.com\/blog\/#\/schema\/person\/795eb085fee7451afcf700cc9bf50c0d\"},\"headline\":\"44 Roleplaying Scenario Examples for Support Teams (+Scripts)\",\"datePublished\":\"2024-10-03T18:32:29+00:00\",\"dateModified\":\"2026-06-09T16:10:29+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/\"},\"wordCount\":10820,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/whatfix.com\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2024\/10\/role-playing-scenarios-for-customer-support.png\",\"keywords\":[\"Call Center\",\"Customer Experience\",\"Support\"],\"articleSection\":[\"Support\",\"Training &amp; Readiness\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/\",\"url\":\"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/\",\"name\":\"44 Roleplaying Scenario Examples for Support Teams (+Scripts)\",\"isPartOf\":{\"@id\":\"https:\/\/whatfix.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2024\/10\/role-playing-scenarios-for-customer-support.png\",\"datePublished\":\"2024-10-03T18:32:29+00:00\",\"dateModified\":\"2026-06-09T16:10:29+00:00\",\"description\":\"Explore 40+ examples of roleplay scenarios for frontline teams and support agents to help build readiness and prepare them for real work.\",\"breadcrumb\":{\"@id\":\"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/#primaryimage\",\"url\":\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2024\/10\/role-playing-scenarios-for-customer-support.png\",\"contentUrl\":\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2024\/10\/role-playing-scenarios-for-customer-support.png\",\"width\":791,\"height\":488},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/whatfix.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Training &amp; Readiness\",\"item\":\"https:\/\/whatfix.com\/blog\/category\/employee-training\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"44 Roleplaying Scenario Examples for Support Teams (+Scripts)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/whatfix.com\/blog\/#website\",\"url\":\"https:\/\/whatfix.com\/blog\/\",\"name\":\"The Whatfix Blog | Drive Digital Adoption\",\"description\":\"Get tips and advice on driving digital adoption through better employee training, product adoption, digital transformation, and more.\",\"publisher\":{\"@id\":\"https:\/\/whatfix.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/whatfix.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/whatfix.com\/blog\/#organization\",\"name\":\"Whatfix\",\"url\":\"https:\/\/whatfix.com\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/whatfix.com\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2023\/02\/favicon-updated2.png\",\"contentUrl\":\"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2023\/02\/favicon-updated2.png\",\"width\":150,\"height\":150,\"caption\":\"Whatfix\"},\"image\":{\"@id\":\"https:\/\/whatfix.com\/blog\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/whatfix.com\/blog\/#\/schema\/person\/795eb085fee7451afcf700cc9bf50c0d\",\"name\":\"Samantha Rohn\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/whatfix.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/61c9244c0fc63efe760317a213a381d1cd65f04491f333b76b43d34a778ea50a?s=96&d=blank&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/61c9244c0fc63efe760317a213a381d1cd65f04491f333b76b43d34a778ea50a?s=96&d=blank&r=g\",\"caption\":\"Samantha Rohn\"},\"description\":\"Samantha is a Content Marketing Manager at Whatfix. Before joining, Sam spent 6+ years on the agency side at L2TMedia building its content and SEO operations. Sam closely monitors the CRM, CX, and service team space, analyzing emerging technologies, trends, and best practices. Sam also writer a bi-weekly LinkedIn column called the Digital Adoption Insider. Growing up in Chicago, Sam still calls the Second City her home. Before starting her career, she graduated from the University of Missouri's Journalism School. You can connect with Sam on LinkedIn or reach out via email at samantha.rohn@whatfix.com - her inbox is always open!\",\"sameAs\":[\"https:\/\/www.linkedin.com\/in\/samantha-rohn-56744468\"],\"url\":\"https:\/\/whatfix.com\/blog\/author\/sam\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"44 Roleplaying Scenario Examples for Support Teams (+Scripts)","description":"Explore 40+ examples of roleplay scenarios for frontline teams and support agents to help build readiness and prepare them for real work.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/","og_locale":"en_US","og_type":"article","og_title":"44 Roleplaying Scenario Examples for Support Teams (+Scripts)","og_description":"Explore 40+ examples of roleplay scenarios for frontline teams and support agents to help build readiness and prepare them for real work.","og_url":"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/","og_site_name":"The Whatfix Blog | Drive Digital Adoption","article_published_time":"2024-10-03T18:32:29+00:00","article_modified_time":"2026-06-09T16:10:29+00:00","og_image":[{"width":791,"height":488,"url":"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2024\/10\/role-playing-scenarios-for-customer-support.png","type":"image\/png"}],"author":"Samantha Rohn","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Samantha Rohn","Est. reading time":"49 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/#article","isPartOf":{"@id":"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/"},"author":{"name":"Samantha Rohn","@id":"https:\/\/whatfix.com\/blog\/#\/schema\/person\/795eb085fee7451afcf700cc9bf50c0d"},"headline":"44 Roleplaying Scenario Examples for Support Teams (+Scripts)","datePublished":"2024-10-03T18:32:29+00:00","dateModified":"2026-06-09T16:10:29+00:00","mainEntityOfPage":{"@id":"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/"},"wordCount":10820,"commentCount":0,"publisher":{"@id":"https:\/\/whatfix.com\/blog\/#organization"},"image":{"@id":"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/#primaryimage"},"thumbnailUrl":"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2024\/10\/role-playing-scenarios-for-customer-support.png","keywords":["Call Center","Customer Experience","Support"],"articleSection":["Support","Training &amp; Readiness"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/","url":"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/","name":"44 Roleplaying Scenario Examples for Support Teams (+Scripts)","isPartOf":{"@id":"https:\/\/whatfix.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/#primaryimage"},"image":{"@id":"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/#primaryimage"},"thumbnailUrl":"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2024\/10\/role-playing-scenarios-for-customer-support.png","datePublished":"2024-10-03T18:32:29+00:00","dateModified":"2026-06-09T16:10:29+00:00","description":"Explore 40+ examples of roleplay scenarios for frontline teams and support agents to help build readiness and prepare them for real work.","breadcrumb":{"@id":"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/#primaryimage","url":"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2024\/10\/role-playing-scenarios-for-customer-support.png","contentUrl":"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2024\/10\/role-playing-scenarios-for-customer-support.png","width":791,"height":488},{"@type":"BreadcrumbList","@id":"https:\/\/whatfix.com\/blog\/role-playing-scenarios-customer-support\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/whatfix.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Training &amp; Readiness","item":"https:\/\/whatfix.com\/blog\/category\/employee-training\/"},{"@type":"ListItem","position":3,"name":"44 Roleplaying Scenario Examples for Support Teams (+Scripts)"}]},{"@type":"WebSite","@id":"https:\/\/whatfix.com\/blog\/#website","url":"https:\/\/whatfix.com\/blog\/","name":"The Whatfix Blog | Drive Digital Adoption","description":"Get tips and advice on driving digital adoption through better employee training, product adoption, digital transformation, and more.","publisher":{"@id":"https:\/\/whatfix.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/whatfix.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/whatfix.com\/blog\/#organization","name":"Whatfix","url":"https:\/\/whatfix.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/whatfix.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2023\/02\/favicon-updated2.png","contentUrl":"https:\/\/whatfix.com\/blog\/wp-content\/uploads\/2023\/02\/favicon-updated2.png","width":150,"height":150,"caption":"Whatfix"},"image":{"@id":"https:\/\/whatfix.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/whatfix.com\/blog\/#\/schema\/person\/795eb085fee7451afcf700cc9bf50c0d","name":"Samantha Rohn","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/whatfix.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/61c9244c0fc63efe760317a213a381d1cd65f04491f333b76b43d34a778ea50a?s=96&d=blank&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/61c9244c0fc63efe760317a213a381d1cd65f04491f333b76b43d34a778ea50a?s=96&d=blank&r=g","caption":"Samantha Rohn"},"description":"Samantha is a Content Marketing Manager at Whatfix. Before joining, Sam spent 6+ years on the agency side at L2TMedia building its content and SEO operations. Sam closely monitors the CRM, CX, and service team space, analyzing emerging technologies, trends, and best practices. Sam also writer a bi-weekly LinkedIn column called the Digital Adoption Insider. Growing up in Chicago, Sam still calls the Second City her home. Before starting her career, she graduated from the University of Missouri's Journalism School. You can connect with Sam on LinkedIn or reach out via email at samantha.rohn@whatfix.com - her inbox is always open!","sameAs":["https:\/\/www.linkedin.com\/in\/samantha-rohn-56744468"],"url":"https:\/\/whatfix.com\/blog\/author\/sam\/"}]}},"_links":{"self":[{"href":"https:\/\/whatfix.com\/blog\/wp-json\/wp\/v2\/posts\/78882","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/whatfix.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/whatfix.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/whatfix.com\/blog\/wp-json\/wp\/v2\/users\/73"}],"replies":[{"embeddable":true,"href":"https:\/\/whatfix.com\/blog\/wp-json\/wp\/v2\/comments?post=78882"}],"version-history":[{"count":11,"href":"https:\/\/whatfix.com\/blog\/wp-json\/wp\/v2\/posts\/78882\/revisions"}],"predecessor-version":[{"id":91625,"href":"https:\/\/whatfix.com\/blog\/wp-json\/wp\/v2\/posts\/78882\/revisions\/91625"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/whatfix.com\/blog\/wp-json\/wp\/v2\/media\/78883"}],"wp:attachment":[{"href":"https:\/\/whatfix.com\/blog\/wp-json\/wp\/v2\/media?parent=78882"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/whatfix.com\/blog\/wp-json\/wp\/v2\/categories?post=78882"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/whatfix.com\/blog\/wp-json\/wp\/v2\/tags?post=78882"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}