Verify Identity and Recover a Locked-Out Banking Customer
Practice verifying a locked-out banking customer’s identity, explaining MFA recovery, and guiding them to a safe next step when bills are due today.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Banks · Credit Unions · Financial Services · Contact Centers
Overview
This AI roleplay practice scenario trains banking support staff to handle a customer who is locked out of online banking after losing the phone that held their MFA app. The learner has to verify identity, acknowledge the customer’s urgency, explain why security steps are required, and guide the customer to a safe recovery path without overpromising access.
Use this template when the real skill gap is not product knowledge, but the conversation itself: staying calm, asking focused verification questions, and keeping the customer engaged while protecting the account. It is especially useful for weekday support calls where bills are due, the customer is anxious, and the pressure to “just unlock it” is high.
Do not use this template as a generic banking service script or for situations where the customer already passed verification and only needs a simple password reset. It is also not the right fit for fraud disputes, card replacement, or technical app troubleshooting unless those issues are layered into the lockout scenario. The value of the template is in the specific tension between urgency and security, which is where many agents lose confidence or make risky promises.
How to use this template
- Read the situation so you understand the customer’s urgency, the lost MFA phone, and the need to protect account access.
- Start the roleplay and let Jordan open with a realistic, frustrated request for immediate help.
- Talk to the persona using a calm opening line, then move into focused identity verification and recovery questions.
- Complete the attempt against the scored rubric, checking whether you acknowledged urgency, explained the process, and offered a safe next step.
- Review the feedback, note where you overpromised or rushed, and retry the scenario until your explanation is clear and policy-aligned.
Best practices
- Acknowledge the customer’s urgency before asking verification questions so the conversation does not feel dismissive.
- Use short, plain-language explanations for each security step instead of reading policy language verbatim.
- Ask only the verification questions needed for the recovery path you can actually offer.
- State what you can do next, not what might happen later, so the customer leaves with a concrete plan.
- Keep your tone steady and reassuring even if the customer repeats the same concern about late fees or missed payments.
- Do not imply that account access will be restored immediately unless the recovery path is already confirmed.
- If the customer becomes more frustrated, restate the reason for the process and the safest available option rather than arguing.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this banking roleplay template help learners practice?
It helps learners practice the exact call flow for a customer who lost their MFA phone, cannot access online banking, and needs help without weakening security. The scenario focuses on identity verification, clear explanation of the recovery process, and setting a safe next step the customer can accept. It is useful for support, branch, and contact center teams that handle access issues. The goal is to balance urgency with fraud prevention.
Who should run this scenario?
A team lead, QA coach, onboarding trainer, or operations manager can run it. It works well as a live coaching exercise, a self-serve practice attempt, or part of a certification check for banking support staff. The facilitator should listen for whether the learner acknowledges urgency before moving into verification. They should also score whether the learner stays within policy instead of improvising access.
How often should support teams practice this template?
Use it during onboarding, when policies change, and as a refresher for teams that handle login or account-access calls. It is also a good monthly or quarterly drill for agents who rarely see lockout cases but still need to handle them correctly. Repeating the scenario helps learners build the habit of explaining security steps calmly under pressure. That aligns with deliberate practice: realistic reps with immediate feedback.
Does this template fit regulated banking workflows?
Yes, because it centers on identity verification, account access, and safe recovery steps. The roleplay helps reinforce that convenience cannot override authentication requirements. It is especially useful for teams that must follow internal security policy, fraud controls, and customer authentication standards. The learner should never promise access before verification is complete.
What are the most common mistakes this scenario surfaces?
Learners often jump straight into policy language without acknowledging the customer’s stress. Another common miss is asking too many broad questions instead of a focused verification sequence. Some learners overpromise that access will be restored immediately, which creates risk and frustration if the recovery path is not available. The scenario also reveals whether the learner can explain next steps in plain language.
Can I customize the recovery path or verification steps?
Yes. You can adapt the scenario to match your bank’s actual identity checks, fallback channels, branch handoff rules, or fraud review process. You can also change the customer’s temperament, the urgency level, or whether the customer has partial access through another device. Keep the learner objective the same so the practice still tests calm verification and safe resolution.
How does this compare with an ad-hoc coaching call?
An ad-hoc call may cover the issue once, but this template gives every learner the same situation, persona behavior, and scoring rubric. That makes feedback more consistent and easier to compare across attempts. It also lets the learner retry the same scenario until they can handle the urgency and security balance cleanly. The result is better skill transfer than a one-off conversation.
Can this template be used with other systems or training tools?
Yes. The scenario can be paired with QA scorecards, LMS assignments, call-center coaching workflows, or internal knowledge base links. You can also connect it to roleplay practice programs that support scored attempts and feedback review. If your team uses a specific authentication workflow, add those steps to the scenario so the practice matches real operations. The key is keeping the roleplay grounded in the actual customer journey.
Related templates
Ready to use this template?
Get started with MangoApps and use Verify Identity and Recover a Locked-Out Banking Customer with your team — pricing built for small business.
