What you will prepare
Result: A list of warning signs, limits of the text-only check and an independent route for verifying a request.
- Level
- Beginner practice
- Time
- About 10 minutes for the fictional-message exercise
- Device
- Phone, tablet or computer for reading and notes
- Tools
- The fictional message in this guide; an AI text chat is optional. No real account message, upload, detector subscription or payment is needed.
Before you begin: A warning or lack of warning cannot authenticate a sender. Keep the independent verification step.
Times are planning estimates, not measured reader results. About this October 20, 2026 presentation update.
AI can help flag a suspicious message or suggest questions to ask. It cannot guarantee that a caller, website, image, or payment request is genuine. Treat a scam detector as one source of information, then verify the request through a separate, trusted channel.
This distinction matters when an alert sounds confident—or when no warning appears at all. A useful tool supports your judgment; it does not make the decision to send money or share information for you.
Understand what an alert actually tells you
- A warning is a reason to investigate. A legitimate message can be flagged by mistake.
- No warning is not a guarantee. A fraudulent message can slip through a filter.
- A score needs context. A tool’s “risk score” should not be treated as the measured probability that your particular message is fraudulent unless the provider explains and substantiates that interpretation.
Ask what the tool examines: the text, a link’s reputation, the sender, an audio file, or something else. A text-only review cannot establish who actually sent a message. An image detector cannot establish whether an investment described in that image is legitimate.
Look beyond spelling and polished presentation
The FBI’s guidance on AI-enabled fraud explains how criminals use generated text, images, audio, and video. Clear writing and a convincing voice are insufficient evidence of authenticity.
Instead, examine the request. Is someone asking for a password, verification code, unusual payment, or urgent change to established instructions? Does the message discourage you from checking with anyone else? Those questions remain useful even when the presentation looks professional.
Use a fictional example to test the tool
Try this invented message rather than uploading a real bank statement or private conversation:
“Your account will close in 20 minutes. Use this link to confirm your password and pay a verification fee.”
Ask the AI: “Identify the warning signs in this fictional message. Explain what you cannot determine from the text alone, and suggest an independent way to verify the request.”
A useful response should recognize urgency and requests for credentials or payment, while acknowledging that text analysis cannot authenticate the sender. Be cautious if it declares a message unquestionably safe or invents evidence that it checked the sender.
Check the service before sharing real examples
Read the provider’s description of what it analyzes, what information it stores, and how to delete an upload. Consider whether the task can be done without uploading anything. Redacting a name does not necessarily remove account numbers, conversation details, or other identifying information.
For workplace messages, use your organization’s approved reporting process. Avoid forwarding client material to a personal AI account just to get a second opinion.
Verify before acting
Open the organization’s app yourself or contact it using a number from an existing statement or another independently verified source. Use a separate route from the message being checked. If you have already paid a suspected scammer, the FTC recommends contacting the payment provider promptly to report the fraud and ask about recovery options.
For a practical family response routine, read our guide to protecting yourself and your family from AI scams.
Reviewed October 2, 2026.
AI disclosure: This article was drafted and revised using AI. Read our full disclaimer.
