Text scam losses: $470 million reported in 2024, and what to do next

A parcel update arrives while you are making coffee. It says a delivery needs attention and offers a convenient link. The useful response is a small change of route: open the delivery company's app yourself and look up the parcel there. You can answer the real question about your delivery while keeping control of how the conversation continues.

That kind of everyday decision gives the text scam statistics a practical purpose. The FTC reported $470 million in losses to scams that began with text messages during 2024, in a spotlight published in April 2025. It describes reported harm over a defined period. Understanding the figure helps put the issue in perspective; a calm, repeatable response gives you something useful to do with that understanding.

Read the loss figure with its story attached

The FTC's text scam spotlight identifies patterns involving delivery problems, job offers, fraud alerts, toll notices and wrong-number conversations. The agency examined a random sample of 1,000 narrative reports to identify leading themes. Those categories help explain how a short message can become the beginning of a much longer interaction.

The word “began” matters. Imagine a text followed by a call, an account login and a payment. A person reporting the experience may describe the whole sequence, even though the initial contact occupied only a few lines on a phone. Thinking in terms of that sequence shifts attention toward the next action being requested: follow a link, share information, call someone or move money.

For a reader, this is more useful than trying to memorize the wording of every suspicious message. Ask what the request would cause you to do and how you could verify it through a familiar channel. The message's story may change from a parcel to a bank account, but your ability to choose an independent route stays the same.

What the 11 percent figure adds

The same spotlight says 11% of text scam reports in 2024 indicated that money was lost. The denominator is text scam reports. This characterizes the reports received; it is not a percentage of every text sent or everyone who received an unexpected message.

A small hypothetical example makes the arithmetic easy to follow. If a collection contains 100 reports and 11 mention a monetary loss, the share is 11%. The collection may also include reports about attempted fraud where the person stopped the interaction. People who submitted no report are outside that particular calculation. The example explains the measure, rather than estimating what happened among all recipients.

Keep that distinction when sharing the figure with someone else. “Eleven percent of the reports indicated a loss” is clear and informative. It lets the number do its proper job without making it stand for an individual's odds. The US texting statistics guide covers the related distinction between messages, people and network activity.

Dollar totals add a second dimension. In an imaginary dataset, several small losses and one large loss might produce the same combined amount as many medium-sized losses. A total describes their sum. Information about the distribution would explain the typical experience. This is why a loss figure and a report percentage can be useful together while answering different questions.

A simple route for a delivery or account message

The FTC's advice on unwanted texts recommends contacting the supposed organization through a website or number you already know is genuine. Turn that into an easy habit: begin the next step from your established app, saved account address or existing contact details. You are verifying the underlying issue through a route you selected.

For the parcel example, open the delivery app and look at the shipment associated with your order. If you need help, use its support options. A useful question is, “Does this delivery require any action from me?” This keeps the conversation focused on the parcel rather than on the instructions supplied by the unexpected sender.

For an account notification, the same pattern works with the service's usual app or website. Review the relevant account information there. If a support conversation is needed, describe the purported problem and ask whether it appears on the account. A deadline in the message becomes another detail to verify through that route, rather than a reason to hurry along the sender's preferred path.

This approach reduces the amount you have to decide from appearances. You can notice an unfamiliar link or odd wording, but you can also use the independent route when the message looks polished. The action stays simple: go to the place you already use for the relationship and ask the question there.

Keep the sequence clear if you have already responded

People often summarize an incident as “I clicked a scam,” even though several very different things may have happened. A clearer description is a sequence: I opened the message, visited a page, entered a particular kind of information, or made a payment. That sequence helps you and the organization assisting you choose the relevant next step.

Take a minute to write a short timeline while the details are fresh. Include the approximate time, the organization the message claimed to represent and what action you took. Record the account or payment service involved in a way that helps you identify it without copying secrets into the note. The aim is a useful summary you can refer to during a support conversation.

The FTC's recovery guidance advises promptly contacting the bank, card issuer or payment service involved and asking whether a payment can be reversed. For exposed account credentials, it recommends changing the affected password and enabling additional authentication. The available response depends on the circumstances, so the provider's official process is the right place to pursue the specific case.

Keep the response organized as it progresses. Put the support reference, the date of contact and the agreed next step together. If you speak to someone else later, that small record helps you explain where the case stands. It also makes it easier to follow the provider's instructions without repeatedly reconstructing the original events from memory.

Make account protection part of ordinary maintenance

The FTC's phishing guide describes attempts to obtain passwords and financial information through impersonated messages. Its protective measures include software updates and multifactor authentication. These fit naturally into normal account maintenance: keep the phone's software current and use the additional sign-in protection offered by important services.

Set aside a calm moment to review the accounts you rely on most, such as your main email and payment services. Find their security settings from within the genuine app or site. Understand the recovery options associated with those accounts as well as the normal sign-in method. Familiarity with the usual route makes it easier to return to it when an unexpected message arrives.

This preparation complements the message-by-message habit. Account protection helps govern access to a service, while independent verification helps you decide whether a particular request belongs to that service. Both are practical parts of looking after your accounts. Neither requires becoming an expert in every variation of a scam story.

Choose reporting and blocking deliberately

In the United States, the FTC describes reporting unwanted texts through the messaging app or forwarding them to 7726. You can also submit a fraud report through the FTC's reporting service. Use the route appropriate to the information you want to share. Reporting is a purposeful action that can give a service details about an unwanted contact.

Google's spam reporting documentation explains what its reporting action sends, including recent incoming messages and related details. It also describes blocking separately from reporting. Reading the prompt gives you a clear choice about the action you want to take and the information involved.

If you are helping a family member, keep them involved in that choice. Show them the reporting screen and explain the difference between retaining the conversation, blocking further contact and submitting information to a service. This makes the help understandable and repeatable. The next time an unfamiliar text arrives, they have a process they recognize rather than a set of mysterious actions someone else performed.

Keep a useful record without spreading it everywhere

A short record can make follow-up easier. The message wording, the approximate timeline and any support reference may be useful when speaking with the organization involved. Choose a place where you can find those details again and keep the audience appropriate to their purpose. A private reference record serves a different role from a public post asking strangers to investigate.

For SMS history you choose to retain, HashKeep provides an archive. Its role is preservation, not sender authentication or scam prevention. That is the relevant product boundary here. You can keep a readable record of an exchange while using the service's official support process to establish what happened and what action is available.

Forwarding introduces a new audience. Email, Telegram or Discord destinations can be useful for a deliberate workflow, and their providers or recipients can read delivered copies. The SMS forwarding privacy guide explains that choice. For a sensitive exchange, send the details needed by the person helping you rather than distributing the entire conversation broadly.

A calm routine is easier to reuse

The sequence is short enough to remember: identify the request, choose an independent route, and keep a clear account of any action already taken. Reporting and blocking are additional choices you can make deliberately. When somebody asks for help, walking through that sequence together gives them a practical skill instead of another alarming statistic to carry around.

The FTC's 2024 reported-loss figure provides context for why this deserves attention. Your response can remain ordinary and manageable. Open the account or delivery app you know, ask a specific question, and use official support when needed. The useful outcome is a decision made from information you verified, with a concise record available if you need to return to it later.

Sources

1. FTC Top text scams of 2024

   April 2025; 2024 reported loss and report denominator; sample of 1000 narratives. Checked 2026-10-13.

2. How to Recognize and Report Spam Text Messages

   Independent verification and US reporting routes. Checked 2026-10-13.

3. How To Recognize and Avoid Phishing Scams

   Credential/payment phishing and account protection. Checked 2026-10-13.

4. What To Do if You Were Scammed

   Official response guidance; prompt provider contact, credential recovery, no guaranteed refund. Checked 2026-10-13.

5. Report spam in Google Messages

   Reporting disclosure, last ten incoming messages, blocking separately. Checked 2026-10-13.