Verify Identity and Recover a Locked-Out Banking Customer

It covers a support call with a banking customer who lost their MFA phone, cannot log in, and needs help regaining access without bypassing security. The learner practices acknowledging urgency, verifying identity, explaining recovery steps, and setting a realistic next action. It is designed for account-access recovery, not for general banking product support. The template focuses on what the agent says and does during the call.

This template fits frontline banking support, contact center onboarding, and fraud-aware service teams. It is especially useful for new agents who need practice balancing empathy with strict verification. Team leads can also use it for coaching and calibration. It works well for both live practice and self-paced rehearsal.

Use it during onboarding, then revisit it whenever identity-verification policy changes or agents struggle with account recovery calls. It is also useful as a refresher before peak support periods, such as bill-payment cycles or after a security incident. Repeating the scenario helps agents build consistent language and better pacing. The goal is to make the verification flow feel natural without sounding scripted.

An ad-hoc conversation usually covers only one example and depends on the coach's memory. This template gives the learner a repeatable situation, a defined persona, and scored rubric criteria so performance can be compared across attempts. That makes it easier to spot whether the agent is actually improving. It also reduces drift in how different coaches teach the same recovery call.

Yes. You can swap in your own identity-verification steps, escalation paths, callback rules, and MFA reset process. You can also adjust the persona's temperament to match your customer base or call volume. Keep the scenario specific, but align the recovery details with your internal policy. The best customizations preserve the tension between urgency and security.

It often reveals agents who jump straight to solutions before acknowledging the customer's frustration. It also surfaces vague explanations of verification steps, overexposure of sensitive information, and weak next-step guidance. Another common issue is promising immediate access when the process actually requires a secure follow-up. The rubric is built to catch those behaviors.

The scenario reinforces secure identity verification, least-privilege handling of account details, and careful communication around recovery steps. It helps agents practice not disclosing sensitive information before verification is complete. That supports internal controls and common financial-services expectations around customer authentication. The roleplay is about safe service, not shortcutting the process.

Pair it with your identity-verification SOP, fraud escalation guide, and any knowledge base article for MFA reset or device replacement. It also works well alongside call-quality scorecards and coaching notes. If your team uses CRM or contact-center tools, the scenario can be tied to the exact workflow agents must follow after the call. That makes the practice more transferable to real work.