Operations

Using AI to Check Suspicious Emails: A Second Reader for a Small Business Inbox

A suspicious email lands in a shared inbox and somebody has to decide, today, whether it is safe to act on. An AI assistant can read it slowly and list what the sender is really asking for. It cannot tell you the message is genuine. This guide builds the routine that keeps those two jobs separate.

Published 2026-11-02 · Last updated 2026-11-02

Can an AI assistant tell you whether an email is a scam?

Not definitively, and any tool that promises a definitive answer is overselling. What an assistant can do, quickly and usefully, is read a suspicious message the way a careful colleague would: slowly, looking for the specific things the sender is trying to get you to do. Phishing is attackers tricking owners or employees into clicking harmful links, opening fake emails, or downloading malicious attachments, and those actions can expose sensitive information or install malware. The scale is not trivial. Phishing topped the list of the five most reported cybercrimes in the FBI 2024 Internet Crime Report, with 193,407 complaints.

So the assistant earns a place in the routine, but a limited one. It is a second reader. The decision still comes from rules you set in advance, and the most important rule is simple: no chat window clears a request for money, bank details, or credentials. Ever.

What the assistant can and cannot see

Start with what changed. AI written phishing no longer gives itself away with clumsy grammar, so spelling and polish tell you almost nothing now. The warning signs that still work are about the sender, the request, and the pressure: an unexpected ask, urgent language, a link that does not belong, a greeting that could be addressed to anyone. CISA notes that a generic greeting such as Dear Valued Customer, paired with a signature block that carries no contact information, is an indicator of phishing, because a trusted organization will normally address you by name and provide its contact information. An assistant is genuinely good at listing those signs from the text in front of it.

Now the limits, because they shape the whole procedure. A pasted message is flat text. It does not carry the real destination of a link, only the words the link displays. It does not carry the authentication results your mail system checked on arrival. SPF lists which servers may send mail for a domain, DKIM adds a cryptographic signature to messages, and DMARC tells receiving servers what to do when those checks fail, and none of that machinery is visible in a copied paragraph. The sender address itself can deceive: a phishing address may imitate a legitimate business by altering or omitting a few characters, and even a real looking address can be spoofed. The assistant can flag a domain that looks wrong. It cannot authenticate the one that looks right.

One more limit matters in a business inbox. Phishing text can try to manipulate an AI that reads the mail, for example by hiding instructions inside the message. A sentence buried in a long fake invoice that tells the reader to ignore the warning signs is aimed at your checker, not at you. That is a practical reason to ask the assistant for observations, never for obedience, and to treat a glowing all clear with more suspicion than a list of concerns.

Prepare the message before you paste anything

  1. Pause, and touch nothing. Do not click links, open attachments, or reply. Replying confirms the address is live, and the check needs none of those actions.
  2. Copy the words, not the links. Copy the message text into a document first. The destination of a link stays behind, which is exactly where it should stay.
  3. Strip your own details. Remove names, account numbers, and any codes before pasting. Never paste a password or a one time code anywhere. The assistant needs the wording and the request, not your identifiers.
  4. Record the sender address exactly as shown. Character by character. The altered or omitted characters in an imitation address are evidence, and they vanish if you retype from memory.
  5. Check link destinations yourself, without clicking. Hover the mouse over each link to see where the URL leads. That reading is yours to make, not the assistant's, because pasted text cannot show it.
  6. Describe attachments, never forward them for opening. Note the file name and type in your own words. Do not ask the assistant to open a suspicious link or file to see what is there. Check the domain instead.

What success looks like: the assistant receives a clean block of text with no passwords, no codes, no account numbers, and no live links, plus your own note of the exact sender address and the real link destinations you read on hover.

Run the check: ask for warning signs, not a verdict

The prompt decides the quality of the answer. A yes or no question gets a confident guess. A warning sign question gets evidence you can weigh. Use a prompt in this shape: “Here is the text of an email I have not clicked or replied to, with personal details removed. Sender shown as: [address]. List every warning sign of a scam you can see, explain what the sender seems to want me to do, and say plainly where you cannot be sure. Do not tell me it is safe.”

Two follow ups are worth the extra minute. First, ask whether the sender domain matches the organization the message claims to be from, while remembering that even real looking addresses can be spoofed, so a match settles nothing. Second, ask the assistant to name the single action the message most wants: a payment, a password, a bank detail change, a download. Naming the prize clarifies the decision, because the decision rule below is keyed to the action, not to how the message feels.

Short version: the assistant sorts. You decide.

Decide by rule: the three outcomes

The decision rule for every checked message
What the message asks forOutcomeRule
Information you would happily give a stranger, no links neededProceed with careAnswer through your normal channel, not by replying to the checked message
A login, a file download, or access to an accountVerify out of band firstGo to the service through your own bookmark or app; never through the message
Money, a payment, a bank detail change, or credentialsHold, verify, then decideConfirm through a contact method you already hold, whatever the assistant said
Anything already clicked, opened, or answeredTreat as an incidentChange passwords, contact the bank if money is involved, and log it

The hold row carries the whole system. CISA's instruction for business staff is direct: verify a message that feels off not by replying, and not by using any phone number or link inside the message, but through a known contact method you already have, such as a number stored on your computer, or a number found through a search engine. For a supplier bank change, check previous statements for contact information rather than anything connected to the request. The assistant's opinion does not shorten that step. It only tells you how carefully to take it.

If someone already acted, the order matters. Change any password that might have been revealed, on every account where the same password was used. If financial accounts may be compromised, contact the financial institution immediately. Then report and delete the message itself: suspected phishing gets reported and deleted, every time, because the report protects the next inbox it lands in. Finally, log the outcome where the team can see it: date, sender, what was asked, what the check found, and what was decided. Staff cannot follow a reporting habit they have never been shown, so name the person suspicious mail goes to, and keep that name current. CISA makes the same point for small businesses generally: employees should know to whom and how to report suspicious emails.

General information for small business owners, not security advice for a specific incident. If money has already moved or an account is compromised, contact your bank and your IT provider first, then work through the checks here.

, Dex Carter, Tech Writer

Keep reading: Operations