It Sounded Like the Board Chair Asking Finance to Wire the Gala Deposit. Here's the Callback Rule.

It is 4:52 p.m. on a Thursday in April, three days before the spring gala. The part-time bookkeeper at a $3.4 million human services nonprofit picks up a voicemail left on her direct line eleven minutes earlier. It is the board chair. Same hoarse voice, same habit of saying "listen" before every sentence, same road noise. The venue moved the deposit deadline up, the executive director is on a plane, please push the $18,400 wire tonight and she will sign the check request in the morning.

Everything about it is right except that the board chair never called.

Forty seconds of a board chair's voice is now enough

Here is the part that changed and the part owners keep underestimating. Cloning a voice used to take a studio session's worth of clean audio and someone who knew what they were doing. In 2026 it takes a short sample and costs almost nothing. Nonprofits are unusually exposed because they publish the sample themselves. The board chair's voice is in the annual meeting recording on YouTube. The executive director's voice is in the 90-second appeal video on the donation page, the podcast interview about the capital campaign, and the local news segment about the new shelter beds. The development director's voice is on the outgoing voicemail greeting anyone can reach by dialing the main number and pressing an extension.

You cannot take those down. The videos are how you raise money. So the control has to move.

Caller verification, in a nonprofit finance office, means this: no instruction that arrives by phone moves money, changes a bank record, or releases a gift — no matter whose voice it is in — until someone has called back on a number that was already in your records before that call came in. That single sentence, adopted as policy and actually followed, closes almost the entire hole.

The four phone-authorised actions a cloned voice would go after

Not every request is worth faking. Fraud follows the shortest path to cash. In this sector the short paths are specific and there are four of them.

• The urgent wire or same-day ACH. Gala deposits, emergency client assistance, a consultant who "needs to be paid before the site visit." Usually framed as time-pressured and usually routed around the executive director, who is conveniently unreachable.
• The banking change on a vendor or grantee record. A caller claiming to be from a grantee organisation or a longtime contractor asks the finance office to update the ACH details in Sage Intacct, QuickBooks or Bill.com before the next scheduled disbursement. On the foundation side, this is the one that hurts most: a $250,000 grant payment scheduled in Fluxx or Foundant goes out to a new account with the correct payee name on it.
• The gift or pledge instruction. A caller claiming to be a major donor asks for a refund of a recent credit card gift to a different card, asks that a pledge payment be redirected, or asks staff to re-issue an acknowledgment letter to a different name and address for tax purposes.
• The payroll or reimbursement change. A voice that sounds like a program director asks HR to update direct deposit before Friday. Small dollars per hit, but it works on organisations where one person handles payroll alone.

Notice what all four have in common. Every one of them is a request a legitimate person actually makes several times a year, which is exactly why staff say yes.

The Tuesday-morning version: what the call should hit before it hits a human

The workable answer is not "train staff to be suspicious." Suspicion decays under deadline pressure, and gala season and year-end are nothing but deadline pressure. The answer is a fixed sequence tied to a defined class of request, so the bookkeeper is never the one deciding whether a voice is real.

flowchart TD
  A["Call reaches finance line"] --> B["Ask: does this move money or change a payment record?"]
  B -->|No| C["Handle normally, log the call"]
  B -->|Yes| D["Open a hold ticket, take no action"]
  D --> E["Call back the number already on file in Sage Intacct or the CRM"]
  E --> F{"Did the person on the known number confirm?"}
  F -->|No| G["Freeze the record, notify Finance Director and Board Treasurer"]
  G --> D
  F -->|Yes| H["Second approver releases the payment, note filed in the ticket"]

Three details make this survive contact with a real week. First, the hold ticket exists before the callback, so an unresolved request is visible to someone else rather than sitting in one person's head. Second, the callback number comes from the record, never from the caller and never from caller ID — spoofed numbers are older and cheaper than cloned voices. Third, the second approver requirement applies to the change, not just the payment. Most nonprofits require two signatures over some threshold; almost none require two people to approve a bank detail edit, and that edit is the actual theft.

Add one thing that costs nothing: a spoken code phrase shared between the executive director, the board treasurer and the finance director, rotated once a year at the board retreat, never written in email. If the voice cannot produce it, the voice does not get a wire.

Running the numbers on a control nobody wants to pay for

Boards approve controls when someone shows them expected cost, not scare stories. Here is the arithmetic for an organisation with a $4 million budget, one finance director, one part-time bookkeeper, and roughly 40 payment-detail changes a year (new grantees, new vendors, moved bank accounts).

Those percentages are illustrative, but the shape holds under any reasonable substitution. You spend roughly five hours a year to remove about four thousand dollars of expected annual loss — and more importantly the tail event: the $180,000 grant disbursement that goes to the wrong account and has to be disclosed to the funder, the auditor and the board.

There is a second cost organisations discover late. Read your crime policy. Many carriers treat a transfer staff made voluntarily, even under deception, as excluded unless you carry a social engineering endorsement, and several now ask on renewal whether you have a documented callback procedure. Having one written down can affect what you pay and whether you are covered at all.

Where the voice on the line is genuinely hard to judge

Three honest limits. First, none of this helps with the request that is real but wrong — the founder-era executive director who genuinely does call the bookkeeper directly and genuinely does want the wire out tonight, and who takes it personally when someone applies the policy to her. That is a governance problem, and the board treasurer has to solve it in a board meeting, not the bookkeeper at 4:52 p.m.

Second, do not put the burden on staff to detect a fake by ear. As of July 2026, a good clone is not reliably detectable by a human on a phone call, and telling a receptionist to "listen for something off" produces false confidence and, eventually, an accusation aimed at a real donor whose voice is thin over a bad landline.

What stays human: the judgement call on a donor who is confused or being pressured by a relative, the conversation with a board member who does not like the new rule, and the decision about when a suspected attempt becomes a report to the bank and to law enforcement.

What to do on Monday

Write one page. Title it "Payment and record changes requested by phone." List the four actions above. State that each one requires a hold ticket, a callback to the number on file, and a second approver. Name who the second approver is when the executive director is travelling. Get the board treasurer to sign it at the next finance committee meeting and put it in the fiscal policy manual, which your auditor will ask for anyway. Then turn on dual control for outbound wires at the bank — most business accounts offer it and most nonprofits never switch it on.

Frequently asked questions

Our development director takes gift instructions by phone from donors all day. Does this slow that down?

No, because most of what she does is not on the list. Taking a pledge, updating a mailing address, discussing a designation — none of that moves money. The rule triggers on refunds, card changes, bank detail edits and any instruction to send money out: a handful of calls a month, not a hundred.

We are a small family foundation with two staff. Is a second approver realistic?

Yes, and it is usually a trustee. Many private foundations already require a trustee signature over a threshold for grant payments. Extend it to grantee banking changes and you have covered the largest single exposure a foundation has — the payment file that goes out right after a grant is approved, when everyone is expecting money to move.

Should we tell our donors and grantees we are doing this?

Tell your grantees, in writing, at the point of award: we will never change payment details on a phone call or an email alone, and we will always call you back on the number in your grant file. That makes the fraudulent version look wrong when it arrives. Donors do not need a memo; they just get one extra confirming call.

Does an AI receptionist make this worse or better?

Better, if it is set up to hand off rather than to act. A phone agent that never has authority to change a record, that logs every call with a transcript, and that routes anything touching money to a named human with a ticket attached, removes the improvised yes. The danger is giving any automated system the ability to complete a financial action on voice instruction alone. Do not do that.

A note on the phone line itself: CallSphere builds AI voice and chat agents that answer nonprofit main lines and web chat around the clock, take donor and program calls, book appointments, and capture who called and why. It does not authorise wires and it should not — but it does give you a complete, timestamped record of every call that came in, which is exactly what you want in front of you the morning after a request like this one.