Explain the callback.

Cirlet · October 22, 2026. Original editable templates. Replace every bracketed field and confirm your actual process before use.

Help clients understand how your agency handles an unexpected request to change sensitive details. These words describe a process you must establish; they do not create one.

Download editable messages · TXT

A short client email

Subject: How to check an unexpected request
If you receive an unexpected request that appears to come from [agency name] to change payment instructions or disclose sensitive information, pause. Contact us using [the phone number on your existing agency documents / another approved, previously known route]. Do not rely on a new number or link supplied in the unexpected message.
Our agreed process for confirming sensitive changes is [describe the process your agency actually follows]. If something does not match, ask [approved agency role] to verify it before acting. Please do not reply with passwords, recovery codes or confidential records.

Website wording

Unexpected request? Verify it first.
Before acting on an unexpected change to payment instructions or sharing sensitive information, use our contact details from your existing agency records to check with [approved role]. A familiar name, logo or voice alone does not verify a request. Our process is [insert the agency’s approved process].

A provider handoff

“Please help us confirm the approved callback route, the agency role responsible for sensitive changes and where clients can find existing contact details. Check that website and email wording match our actual process. Record the owner, evidence and review date before publication.”

Before publishing

Have an accountable agency owner approve the process and wording.
Replace every bracket. Confirm the contact route is current and independently available.
Check the wording against actual carrier, provider and agency procedures. Do not promise to verify every message unless that is established.
Use a fictional request to rehearse the process with staff. Do not send a test scam to clients.
Set a review owner and date. Keep sensitive internal contacts and incident details out of public text.

Run the team rehearsal · See how to record an unknown

For agency web providers

You may adapt this original text for an agency’s approved process under the kit reuse terms. Attribute Cirlet in your resource documentation; client-facing credit is optional for these message templates. Publishers may qualify links. Do not imply endorsement, a security review, coverage or regulatory compliance. No client list or credentials need to be shared with Cirlet.

Verification principle: FBI IC3, May 15, 2025. These templates are preparation resources, not emergency response or a guarantee against fraud.