Wire Fraud Call-Back Protocol
A wire-verification procedure, plus what to do in the first hour if a wire goes wrong
Install it in one line — paste a single command into Claude, ChatGPT or Cursor and it writes the skill into your project.
Free, and about thirty seconds: a work email and a six-digit code.
Downloading shares your name, firm, role, and email with The Helvetica Group. That introduction is what keeps every skill here free.
What this skill does
Writes the procedure that stops wire fraud on fundings, payoffs, draws and investor payments: check every set of wire instructions by calling a number you found yourself, and never let one person both set up and release a wire. If a wire may already have gone to a scammer, it gives you the first-hour response plan.
What it does
- Maps every wire you send and receive, and how each one is usually attacked
- Writes a step-by-step call-back procedure your staff can follow every time
- Lists the warning signs that should stop a wire: changed instructions, urgency, lookalike email addresses
- Sets up two-person approval that works even for a very small team
- Gives a clear response plan for a suspected fraudulent wire: bank, FBI complaint, evidence, email security, insurer, counsel
- Drafts a one-page staff checklist, a call-back log and a plain-language warning notice for borrowers
When to use it
- You don't have a written wire procedure yet, or it has never been tested
- A title company, contractor or investor emails new bank details
- Before a funding, payoff, construction draw or investor distribution
- You think a wire may have gone to the wrong account
What to have ready
- Your role: lender, broker, servicer or fund
- The kinds of wires you send and receive
- Who on your team can set up and approve wires, by role
- Your bank's approval controls and your insurance details, if you know them
How to use it
- Download it with the button above. You'll sign in with a work email — that's how the creator knows who is using their skill.
- Copy the install prompt from the "Run it in Claude" box, and paste it into Claude along with the file. Claude installs the skill, fills in your firm's details where the file has
[BRACKETED]placeholders, and runs a quick test with you. - Then just ask in plain English. Claude picks the skill up on its own when a request matches it. Anything it still needs, it asks you for — it won't invent a number.
"Our contractor on [PROPERTY ADDRESS] just emailed new bank details for tomorrow's [AMOUNT] draw. Write our wire verification procedure and tell me what to do before this draw goes out."
What you get back
A draft wire-verification procedure, a red-flag list, two-person approval rules, a suspected-fraud response plan, a printable staff checklist, a call-back log template and a borrower warning notice.
Good to know
- Output quality tracks input quality. A missing figure is flagged as missing — it is never estimated to fill a gap.
- Every draft is a starting point for your own review, not a finished decision.
- Runs anywhere Claude does: the Claude app, Claude Desktop, or Claude Code.
- No bank account details ever appear in the drafts, and there is deliberately no way for a senior person to skip the call-back. Reporting duties are left to your counsel.
Legal disclaimer
This skill drafts; it does not decide. Its output is not legal, tax, accounting, appraisal, or investment advice, and using it creates no attorney-client, fiduciary, or advisory relationship. Nothing it produces is a commitment to lend or an offer to sell a security. Verify every number, date, citation, and conclusion against the source documents, and have a qualified professional licensed in the relevant jurisdiction review the work before you rely on it or send it to a borrower, investor, counterparty, or regulator. Laws, rates, and market data change. The final work product is yours.
Inside this skill
The actual file you get. Members can read it in full before saving it.
Wire Fraud Call-Back Protocol
Private lending moves large sums by wire to parties the lender rarely meets: title and escrow companies, payoff lenders, contractors on draws, borrowers, investors. Criminals know it. The common attack is simple — compromise or imitate one party's email, then send "updated" wire instructions at the moment money is about to move. Recovery after the fact is uncertain. Prevention comes down to one habit, applied without exception: verify every set of instructions by calling a number you found yourself, and let no single person both set up and release a wire.
It works for lenders, brokers, servicers and fund managers of any size, including a two-person shop.
The protocol, checklist and notice this skill writes are drafts for review by management, the firm's bank and its attorney. Reporting obligations and recovery options depend on the firm's regulatory status, its bank and the facts — confirm them with counsel.
If you believe a wire went to the wrong account right now, skip to Step 5.
Step 1 — Intake
| Input | Required? | Notes |
|---|---|---|
| Your role | ✅ | Lender, broker, servicer, fund manager — decides which flows exist |
| Money-out flows | ✅ | Loan funding to escrow, draw disbursements, investor distributions, refunds, vendor payments |
| Money-in flows | ✅ | Borrower payments, payoffs, investor capital calls, sale proceeds |
| Who can initiate and approve wires today | ✅ | Names by role only: [ROLE] — e.g. closer, controller, principal |
| Bank platform controls | Helpful | Dual approval, beneficiary templates, limits, alerts, any account-verification service the bank offers |
| Existing written procedure | Helpful | Improve it rather than replace it |
| Staff count | Helpful | Dual control has to work with the people you actually have |
| Cyber or crime insurance | Helpful | Notice requirements and any "verification" condition in the policy |
Minimum viable: your role and the kinds of wires you send and receive.
Step 2 — Map the flows and where each is attacked
Build a table of every flow. For each, name who supplies the instructions and how they are usually attacked:
| Flow | Instructions come from | Typical attack |
|---|---|---|
| Loan funding to escrow | Title / escrow company | Spoofed escrow email with "new" account days before closing |
Reading the full skill counts as a download. The contributor receives your name, company, and email.
Ratings & reviews
No written reviews yet. If you run this on a live file, say how it went. The next lender reading this page is deciding whether to trust it.
Examination record
Run it in Claude
- Copy the install command above
- Paste it into Claude, ChatGPT or Cursor
- It writes the skill in, fills in your firm’s details, and test-runs it with you
Prefer the file? The prompt above is for a package you already downloaded.
Details
More from The Helvetica Group
They publish here under a verified work email. Their other skills, and how to reach them, are on their contributor page.