In this article
Reporting, protecting an account and resolving a payment are different jobs. A useful record helps you explain what happened to each recipient without sending the same bundle of private information everywhere.
Start with a short timeline
Write the approximate time, the contact method, what was requested and what you did. Separate observation from inference: “I entered a card number” is a fact; “the carrier has been hacked” is a conclusion this evidence does not establish. Do not copy the card number into the timeline.
Record whether you opened a page, entered a credential, supplied a code, installed anything or authorized a payment. “I clicked it” is often too broad. A more precise account helps you choose the right support channel.
Choose the recipient by the job
- Unwanted text: use the carrier’s current spam-reporting instructions.
- Suspected account change: contact the carrier through an independently reached channel.
- Card exposure or a disputed payment: contact the payment provider through its official service.
- Broader scam report: use the FTC’s reporting guidance.
Metro identifies 7726 as the text-reporting destination. Forwarding for a report is not the same as replying to the sender. The FTC also links to ReportFraud.ftc.gov. Neither action is a promise that an individual case will receive a response or that funds will be recovered.
Keep originals private and share selectively
A screenshot may contain a phone number, notification preview, receipt reference or a token-bearing URL. Keep the original securely if needed for official help. When discussing the incident with someone else, summarize the relevant action instead of sending the whole screen. Follow the actual receiving service’s instructions if it requests evidence.
Do not send the incident record to this publication’s editorial inbox. We cannot file a fraud case, investigate an account or process a refund. Our contact route is appropriate for an incorrect article sentence or a broken public source link.
Use a next-step note, not a verdict
Fictional example: “The text is unverified. I have not opened its link. I will check the bill through the official account. No payment has been authorized from the message.” Another case might read: “Card details were entered. I contacted the card provider using its app. I am following its instructions.” These records are useful without declaring a message safe or fraudulent.
If the record shows exposure, continue with the response guide. If nothing was disclosed, use the inspection worksheet and keep the bill task separate.
Evidence and limits
Public sources checked November 4, 2026. The practical sequence and fictional examples are our editorial analysis. This is not a security scan, a fraud determination or an account investigation.
- Metro: Scam Shield FAQ: Report spam texts to 7726 rather than replying. Network filtering is not a guarantee that every delivered message is legitimate.
- FTC: Recognize and avoid phishing: Reach the company through a known independent channel, report phishing, and seek recovery guidance for exposed information.