Question Unusual Account Activity (KYC/AML)

It helps you practice a branch conversation about unusual account activity, including how to explain why the account was reviewed, ask KYC/AML questions without sounding accusatory, and gather enough detail to decide the next compliant step. The focus is on the conversation, not on teaching policy from scratch. It is especially useful when the customer is irritated, suspicious, or reluctant to answer. The goal is to stay calm, keep the discussion factual, and preserve confidentiality.

This template is a fit for branch bankers, tellers with escalation responsibilities, relationship managers, and new hires who need realistic practice before handling sensitive customer conversations. It also works for supervisors coaching staff on how to ask one question at a time and avoid over-explaining. If your team handles account reviews, source-of-funds questions, or transaction follow-up, this scenario is relevant. It is not meant for general sales practice.

Use it during onboarding, refreshers, and anytime staff need practice with account review conversations. It is also useful after policy updates or when teams see repeated mistakes in live interactions. Because the scenario is short and focused, it can be run as a quick roleplay in a team meeting or as a one-on-one coaching attempt. Repeating it with different customer temperaments helps learners build confidence.

The scenario covers a customer who is upset that their account was temporarily restricted and wants to know why they are being questioned. It includes the tension that comes with large cash deposits, an international wire, and a customer who feels singled out. The learner has to keep the conversation respectful while still asking for the information needed to support review. It does not require the learner to diagnose suspicious activity, only to handle the conversation properly.

Yes, this is a compliance-oriented practice scenario tied to KYC/AML conversation skills. It supports training around customer due diligence, escalation, and careful information gathering without making legal claims or replacing your institution’s policy. Teams should still follow their own procedures for documentation, review thresholds, and escalation. The roleplay is meant to reinforce behavior, not serve as legal advice.

The most common mistakes are sounding accusatory, asking multiple sensitive questions at once, and jumping straight to policy language before acknowledging the customer’s frustration. Learners also tend to over-share internal details, promise outcomes they cannot control, or fail to collect enough context for the next step. This template is designed to surface those habits quickly. The rubric makes it clear whether the learner stayed calm, clear, and compliant.

Yes. You can change the account type, transaction pattern, branch setting, customer temperament, and the exact information your policy requires. You can also adjust the difficulty by making the customer more skeptical or more cooperative. Many teams customize the opening line and the required next step so the roleplay matches their internal process. That makes the attempt more realistic for local procedures.

Ad-hoc coaching often skips the pressure of a real conversation, and a script can make learners sound stiff or overly formal. This template gives them a realistic customer persona, a concrete situation, and a scored rubric so they can practice the actual interaction. Because the persona reacts to how the learner speaks, it creates immediate feedback that is closer to a live branch conversation. That makes it easier to spot gaps in tone, sequencing, and information gathering.