Respond to a Suspected Wire Transfer Scam

A customer who walks into your branch worried about a wire transfer is not looking for a fraud investigation. They are scared, they may still be getting text messages from whoever talked them into the transfer, and they need you to slow the moment down without making promises you cannot keep. This is one of the hardest desk conversations in banking because the right answer is almost never the one the customer wants to hear right away.

Why This Conversation Goes Wrong

Most branch bankers want to help immediately, and that instinct is what causes trouble. A customer describes a call from someone posing as her title company, and the natural response is to reassure her that the money can probably be pulled back or that the sender was obviously a scammer. Neither statement is something you can know at the desk. Wire recalls depend on the receiving bank, timing, and whether funds have already moved again. Promising an outcome you do not control turns a stressful moment into a bigger problem later when the outcome does not match what you said. The conversation also goes wrong when a banker starts investigating the transaction personally, pulling up account details and forming a theory about fraud instead of routing the customer to the team built for that review.

How to Prepare Before You Sit Down

Know your bank's escalation path before a customer is in front of you, not while they are sitting there. You should know who to call or which system to open, what information that team needs first, and how long a customer typically waits for a first update. Write down the two or three facts you actually need, generally when the wire was sent, what new instructions the customer received, and how those instructions arrived. You do not need the customer's full story of the last three days. Practice saying out loud that you cannot confirm recovery of funds or confirm fraud, because those sentences feel awkward the first time you say them under pressure. Also decide in advance what you will never ask for. You do not request a password or a one time code, and you do not need information that the official fraud process collects later through a secure channel.

What to Say at the Desk

Start by acknowledging what the customer did right. Sofia comes in and says a man called claiming to be from her title company and told her to resend her wire to a new account because the first one had an error. You tell her, "You did the right thing coming in today instead of waiting to see what happens." That single sentence does more to calm her than any explanation of process.

Next, get the facts you need without diagnosing the situation. You ask, "Can you tell me when you sent the original wire and what number the caller used to reach you?" Sofia says the wire went out yesterday afternoon and the caller used a number that matched the one on the title company's paperwork, though she never called it back to confirm. You tell her, "Do not call that number again. I want you to call your contact at the title company using the number from your closing documents or their listed office line, not any number this caller gave you." That instruction matters because a scammer who has already impersonated one party can just as easily answer a callback on a spoofed number.

Then be plain about what happens next and who owns it. You say, "I am going to connect you with our fraud and wire team right now. They review the transaction and reach out to the receiving bank if that is appropriate. I cannot tell you whether the funds can be recovered, and I do not want to guess, because that team has information I do not have access to at this desk." Sofia asks if the money is gone. You do not answer that question with a yes or a no. You say, "I understand why you want that answer today. What I can tell you is that your concern is now recorded and moving through the right process, and the team handling wire recalls will update you with facts, not guesses."

Close the conversation by confirming what she should do and expect. You ask her to repeat back the safe number for her title company and remind her that no one from the bank will ever call her asking for a password or a one time code to fix this. You tell her how she will hear back, whether that is a call, a letter, or a note in her online banking messages, and roughly when.

Mistakes That Make a Bad Day Worse

The most common mistake is offering comfort that sounds like a guarantee. Saying "we will get your money back" or "that number is definitely a scam" feels kind in the moment and becomes a real problem if either turns out to be false. A second mistake is skipping the independent verification step. If you only tell Sofia to stop trusting the caller's number without giving her a safe way to reach the real title company, she is left with no path forward and may call the scammer back out of habit. A third mistake is asking for information the fraud process does not need at the branch desk, particularly a password or a single use code, since that request trains customers to hand over exactly the kind of information a future scammer might ask for by mimicking a legitimate process. A fourth mistake is rushing the customer out before she can repeat the safe contact information back to you. If she leaves confused about which number to call, the conversation did not accomplish its purpose even if every other part of it went well.

Practice and Score the Conversation

This is a conversation worth rehearsing before it happens with a real customer, because the habits that feel natural, like reassuring someone that everything will be fine, are exactly the ones you need to unlearn. A manager can run this scenario in a short role play, playing a frightened customer and listening for three things. Did the banker make any promise about recovery or about fraud that the bank cannot back up. Did the banker give a specific, safe way to verify the request outside the bank. Did the banker clearly hand the customer to the right team instead of trying to resolve it personally. Score each of those as pass or fail rather than a vague impression, and replay any moment where the banker slipped into a guarantee.

DealSpeak's Banking practice conversations let a branch banker run this exact scenario against an AI customer who reacts the way a scared, pressured person actually reacts, then get scored on the specific language used. If you want to build the same discipline for a different high stakes banking conversation, look at how to Start a Banking Conversation About an Acquisition or how to Prepare a Commercial Annual Review Conversationsince both share the same core skill of separating what you know from what you hope is true.

Close

A customer in this situation does not need you to solve the fraud. She needs you to slow things down, point her toward a safe way to verify what is happening, and hand her off to the team that actually reviews the transaction. Get those three things right and you have done your job well, regardless of how the wire itself turns out.