The $40,000 Wire She Can't Explain: Your FINRA Rule 2165 Playbook for Trusted Contacts and Temporary Holds

Your 78-year-old client calls on a Tuesday and asks you to wire $40,000 to an account you've never seen, for "a friend who's helping me with an investment." She's been your client for eleven years. She has never mentioned this friend. When you ask what the investment is, she gets vague, then irritated, then says the friend told her not to discuss it because "the opportunity is private." She wants the money out today.

Everything you can do in the next hour was actually decided years ago — by whether you captured a trusted contact when the account was opened, whether your staff was trained to recognize what they just heard, and whether your written procedures let you pause that wire while someone looks. That's the playbook this article builds, around the two FINRA rules that exist for exactly this Tuesday.

Two Rules, One Playbook

• FINRA Rule 4512 requires firms to make reasonable efforts to obtain a trusted contact person for each non-institutional account — a name and contact information for someone the firm may reach about the account. The client can decline; your obligation is generally the reasonable effort, and the account can still be opened without one. The trusted contact receives no authority over the account — no trading, no disbursements, no information rights beyond what the rule contemplates. They are, functionally, someone to call when something looks wrong.
• FINRA Rule 2165 provides a safe harbor allowing a firm to place a temporary hold on a disbursement of funds or securities — and on securities transactions — when it reasonably believes that a "specified adult" is being financially exploited. A specified adult is generally a client age 65 or older, or 18 or older with a mental or physical impairment that leaves them unable to protect their own interests. The initial hold generally runs up to 15 business days, can be extended roughly 10 more business days when the firm's internal review supports it, and can generally be extended further where a state regulator, agency, or court of competent jurisdiction becomes involved.

Note what 2165 is: permissive, not mandatory. It doesn't require you to hold anything — it protects you when you reasonably do. That protection is only usable if your firm's written supervisory procedures invoke it, your staff can recognize the trigger, and your documentation habits can support "reasonable belief" in a file a regulator may later read. Rules are the skeleton; the playbook is the five practices below.

Practice One: Capture the Trusted Contact — Every Account, Then Backfill

At account opening, the trusted-contact request is a form field. The reason firms end up with empty fields is that it gets presented like one. Present it instead as what it is — a professional safeguard, framed so accepting it feels like prudence rather than surrendering independence:

> "One more thing I do for every client: I'd like the name of one person you trust — often an adult child — that I'm allowed to call if I ever see something on the account that worries me. They get no access and no control; they can't see balances or move a dollar. It's one phone call's worth of permission. If something ever looked wrong and I couldn't reach you, who should I call?"

Then backfill the book. Rule 4512's reasonable-efforts duty applies to existing accounts as they're updated, and your older clients — the ones most likely to be targeted — are precisely the ones whose accounts predate the rule. Put the question into every annual review for clients over 60 until the gap is closed, and log each ask, including declines. A documented "asked and declined" is itself the reasonable effort.

Choose the moment well: the best trusted-contact conversations happen at 68, not at 83 — while the client is sharp, independent, and can hear the request as routine professional hygiene instead of a verdict on their capacity.

Practice Two: Train the Team on Red Flags

The exploitation call rarely comes to you first — it comes to whoever answers the phone. Every person who touches client requests should be able to recognize the pattern, and the pattern is remarkably consistent:

• A sudden new person in the client's financial life — a "friend," an online romantic interest never met in person, a new "advisor," a caregiver whose name starts appearing in conversations.
• Uncharacteristic requests — a first-ever wire, a large withdrawal from a client who has never taken more than the monthly distribution, urgency from someone who has never been urgent.
• Secrecy and scripts — the client can't or won't explain the purpose, uses borrowed language ("it's a private placement opportunity"), or says they were told not to discuss it.
• A third party doing the talking — someone else on the line "helping," prompting answers, or holding the phone.
• Signs of confusion — repeating questions, losing the thread of the request, not recalling a conversation from last week.

Give the team one standing instruction that removes all judgment pressure: you never have to accuse anyone — you only have to escalate. A junior associate who says "let me have our principal review this wire today" has done the job perfectly. Route every flag to the designated principal, in writing, same day.

Practice Three: The Hold — the Clock and the File

When the flags stack up, the designated supervisor makes the 2165 decision, and two things determine whether the safe harbor actually protects the firm: the reasonable belief and the file.

Document, same day, in the client's record:

• What was requested — amount, destination, stated purpose, and how it departs from the client's history
• What was observed — the specific red flags, in concrete language ("client could not name the recipient's surname"), not conclusions ("client seemed exploited")
• Who reviewed and decided, and when the clock started
• Every step of the internal review while the hold runs

The timeline discipline matters because the hold is short by design: generally 15 business days, an extension of about 10 more on the strength of your internal review, and further extension generally available once a regulator, agency, or court is engaged. Fifteen days is not "problem solved" — it is a window purchased for the phone calls in Practice Four. A hold placed without an investigation behind it is just a delayed wire.

Know your edges, too: 2165 reaches disbursements and transactions from the account; it is not a general freeze of the client's life, and state rules — many modeled on the NASAA act — may add requirements or protections on top. Your written procedures should name the designated principals, the documentation standard, and the escalation path, because the safe harbor generally presumes you built one.

Practice Four: Notify and Escalate

The hold buys time; the calls use it.

• Notify the trusted contact — generally within two business days of placing the hold, along with parties authorized on the account, unless you reasonably believe that person is involved in the exploitation (in which case notify someone else with standing, and document the exception). This call is the entire return on the 4512 investment: *"I'm seeing a request on your mother's account that doesn't look like her. I've paused it. Can you visit her this week?"*
• Report to Adult Protective Services where exploitation is suspected — and in a number of states, reporting by financial professionals is generally mandatory, so know your state's rule before the incident, not during it. APS can do what you can't: assess the client at home, involve family, and coordinate with law enforcement.
• Use the legal protections built for reporting. The federal Senior Safe Act generally provides immunity for trained financial-services personnel who report suspected elder financial exploitation in good faith to covered agencies. Training is the predicate — one more reason Practice Two is written into procedures rather than delivered as a hallway chat.

What you should *not* do is play detective solo or confront the suspected exploiter. Your instruments are the pause, the file, the trusted contact, and the referral.

Practice Five: Have the Conversation in Spanish

If you serve Spanish-speaking families, this practice is not optional garnish — it's load-bearing. The scams arrive in Spanish: the grandchild-emergency call (*"Abuela, soy yo, tuve un accidente, no le digas a mis papás"*), the lottery that needs fees released, the romance that needs a wire, the fake *notario* handling immigration papers for a fee that keeps growing. The scripts are professionally engineered for a Spanish-dominant elder — they invoke family loyalty, urgency, and discretion in her own language.

Your defenses should speak that language too:

• Run the trusted-contact conversation in Spanish with Spanish-dominant clients, and confirm the elder actually understood what she agreed to — a form signed politely is not a safeguard understood.
• Make the trusted contact for a monolingual elder a bilingual family member wherever possible; they'll spot a scripted story faster than anyone at your firm.
• Train any bilingual staff on red flags in both languages, because the tell is often in the Spanish — the borrowed phrase, the "no le digas a nadie."
• Brief the whole family, at a review, on the common scripts. In multi-generational households, the adult children are your early-warning system; give them the red-flag list in the language each generation reads.

Monday Morning

Run one report: clients 65 and older with no trusted contact on file. That list is your exposure, ranked. Put the trusted-contact ask — in the client's language — into every review on that list until the field is full or the decline is documented. Then spend thirty minutes with your team on the red-flag list and one instruction: *escalate, never accuse.* Confirm your written procedures name who decides a 2165 hold and what goes in the file.

The Tuesday call is coming for someone in your book. The firms that handle it well aren't faster on the day — they finished the playbook years before the phone rang.