Known-Channel Callback: The Simplest Scam Filter
How to hang up, ignore the provided contact path, and verify through a number, app, or person you already trust.

An unexpected caller says your account is at risk, a relative needs help, or a payment must go to a new destination. You do not have to decide on the spot whether the person sounds convincing. End the contact and check the specific request through a route you established independently before the message arrived.
The human pattern underneath
A familiar name, a convincing voice, a real-looking email thread, or a call that arrives exactly when a text predicted it might make a request feel authentic. None proves who is asking. Caller ID can be faked, and a genuine account can be compromised. Urgency alone does not prove a request is false, either: a real problem may need attention through a safer route.
A known-channel callback moves the decision away from the contact path supplied by the unexpected caller or message. It is a useful check, not a guarantee. Start a new call or session yourself: do not call back the number in the incoming call log, reply to the message, or accept a transfer from the caller. The route must still reach the right person, and that person must confirm the particular action you are being asked to take.
Quick facts
| Question | Practical answer |
|---|---|
| Level | Beginner |
| Time | About 9 minutes; reaching the right person may take longer. |
| First move | Pause before paying, sharing a code, granting access, or following a new instruction. End the unexpected contact. |
| Stronger check | Start a new conversation using an independently established number, app, portal, or in-person contact. Confirm the specific request. |
| If you cannot confirm | Leave the request unresolved and hold off on the requested action. Seek help promptly if there is an immediate safety or account risk. |
Plain definitions
| Term | Plain meaning |
|---|---|
| Caller ID | The name or number displayed on a call. It can be spoofed and is not identity proof. |
| Known channel | A contact path established independently of the suspicious request, such as a number on your bank card or a family number you already use. |
| Callback | Ending the incoming contact and starting a new conversation through a known channel. It can also mean using an official app or speaking in person. |
| Out-of-band check | Verification through a separate route from the request; a separate route is useful only if you know it reaches the right person. |
The practical workflow
| Step | What to do |
|---|---|
| Name the request | Note who supposedly contacted you, what they want, and any claimed deadline. Do not provide personal details, one-time codes, payment, or remote access to an unexpected caller. |
| End the contact | Hang up or stop replying. Do not use a number, link, QR code, or transfer offered in the message, even if the caller says it is the fraud department. Do not approve an unexpected sign-in prompt while you check. |
| Choose a route | Use a number on your card or a recent statement, an official app or bookmarked site, a previously established family contact, or an independently confirmed workplace or school directory. Avoid relying on a top search result or advertisement for a support number. |
| Ask about the exact request | Ask the person to describe what they see in their own records before supplying the details from the message. For a payment, compare the recipient, amount, and complete destination or account details with an authorized person using an appropriate secure process. Follow your organization’s approval process too. |
| Decide and note | Continue through the verified route only when the specific request is confirmed. If it is denied, stop and report as appropriate. If the person cannot check, ask which department can and reach it through the established route. If you still cannot confirm, hold the action and try another independently verified contact. Privately note the time, route, person or department, and answer. |
For an unexpected bank call, the FTC recommends hanging up and contacting the bank yourself through its official app, a recent statement, or the number on your card. Do not read a one-time code to an unexpected caller or grant remote access to fix a supposed account problem.
Choose the route before you need it
- Bank or service: Use the card, a recent statement, the official app, or a site you bookmarked independently. Once connected, ask the relevant department whether the stated issue and requested action are real.
- Family or friend: Call a number you already know. If they do not answer, try another trusted relative or friend; silence does not prove either the emergency or the scam. Agree on a family safe-word routine in advance, but do not rely on a safe word alone.
- Workplace, school, or vendor: Use an established directory or contact from your records, and reach someone authorized to confirm the request. For changed payment instructions, verify the actual destination, not just that an invoice exists. The email thread hijack guide explains why a familiar conversation can still contain a false instruction.
A saved number or account is not automatically safe forever: numbers change, accounts can be taken over, and contact records can be altered. If the known route seems compromised or no longer reaches the expected person, use another independently confirmed route or an in-person check. Do not treat a newly supplied number as verified simply because the sender says the old one changed.
If you have no previously established contact, find the organization independently: for example, use the support section of its official app or navigate to its official website from a source you already trust. Cross-check the address against existing records rather than relying on a sponsored search result. For a person, ask someone you already know how to reach them. A second message from the same account, or a number repeated in the original message, is not an independent check. See the search ad and lookalike domain guide if you need to find an organization’s site.
What to ask on the callback
Begin with an open question: “I received a request about my account. What do your records show?” Then compare the answer with the request: who initiated it, what action is needed, and by when. The representative may need to identify you before discussing an account, but keep your password and login verification codes private. If they cannot find a record, give enough context for them to check the specific issue; a lack of an immediate answer is not proof either way. If the person only confirms that you have an account or that an invoice exists, the requested action is still unconfirmed. Ask for the department or person authorized to check it; do not let the original caller connect you.
For a changed payment destination, ask an authorized contact, “What payment instructions do you have on file for this invoice?” Compare the recipient, amount, and full destination details through the organization’s secure verification process, not just the recipient name or last few digits. Avoid putting full account numbers in an ordinary email or your notes. A matching answer is useful evidence, but it cannot rule out a compromised account or an insider error. If the answer conflicts with the message, or the authorized contact cannot verify it, pause the payment and resolve the discrepancy through another established contact. Follow any required independent approval before paying. The real estate wire guide applies this check to closing funds.
A grounded example
A text says your bank account is locked and a representative will call in two minutes. The call arrives on schedule, and the caller knows your name. Hang up, then open your bank’s app or dial the number on your card yourself. Ask whether the account is locked and whether the bank requested the particular action described. If the bank cannot confirm it, do not follow the caller’s instructions; ask the bank how to check further. A familiar name and the timing of the call do not settle the question.
If you already acted or cannot wait
If you sent money, contact your bank, card issuer, payment app, or transfer provider immediately through a known route. Explain what happened and ask whether the payment can be stopped or reversed; recovery is not guaranteed. See what to do after sending money .
If you shared a password or login code, use the provider’s official recovery process, change the affected password, and review account access. Change it on other accounts too if you reused it. If you granted remote access, end the session and contact the provider or a trusted technician through an independently chosen route for help securing the device and accounts. Use a trusted device to seek help if you suspect yours is compromised. The account access guide has further steps. For immediate physical danger, contact local emergency services; do not let an unverified payment demand delay getting help.
Keep the decision reversible
Save the original message where possible and make a private note of the request, times, contact details, and any transaction reference. Avoid opening suspicious attachments or sending more documents while you check. Share records only with the people or providers who need them. The verification notes guide offers a simple record.
If the request remains unconfirmed, it is fine to say, “I will check and get back to you.” Do not publicly accuse someone on incomplete evidence. Block or report the suspicious contact when appropriate; the reporting map covers starting points.
Common mistakes
- Calling a number in the message or the incoming call log instead of starting a new contact through an established route.
- Letting the caller stay on the line, transfer you, or direct your search for a support number.
- Asking only whether a person or invoice exists, without confirming the specific payment or account change.
- Treating a familiar voice, caller ID, or a correct personal detail as proof.
- Giving the contact the answer first, then treating their agreement as confirmation.
- Assuming an unanswered callback means there is no emergency, or that a saved account cannot be compromised.
Try this next
- Save independently verified contacts for your bank, family, school, and workplace before an urgent request arrives.
- Agree on a family safe-word routine and a second person to contact if someone cannot be reached.
- Use the Reality Check Quickstart for a broader first pass, or the small business vendor guide for payment changes.
Official references
- FTC: How to handle unexpected calls that claim your money is at risk — independent bank contact and account-code precautions.
- FTC: Phone scams — caller ID spoofing and U.S. reporting options.
- FTC: Scammers use AI to enhance their family emergency schemes — checking a familiar-sounding voice through a known number or another person.
- FBI: Business email compromise — independent verification of payment requests and changed instructions; includes U.S. reporting information.
- FTC: What to do if you were scammed — payment and account recovery steps, with U.S. reporting options.
Written By
JJ Ben-Joseph
Founder and CEO · TensorSpace
Founder and CEO of TensorSpace and the editor of Fondsites: an engineer working across software, AI, cybersecurity, and biosecurity who builds the site's games and tools.