When you suspect a phone scam, stop the requested action and verify the claim through a contact route you already trust. If you have sent money or shared account access, contact the relevant bank or service provider promptly. You do not need to finish researching the phone number before seeking help.
Phone scam prevention starts with the request: what does the caller want you to send, reveal, install or authorize? A familiar name, polished explanation or public phone listing should not override that question. A reverse lookup can add context, but it cannot approve a payment or authenticate an incoming call.
This guide covers phone scam warning signs, hypothetical examples, recovery preparation and official reporting routes checked in September 2026. Start with the situation that matches your call or message.
First, identify what the caller wants you to do
Separate the caller’s story from the action. A complicated explanation may end in a very simple request: move money, disclose a code, download software or follow a link. Write that action down in plain language before considering the rest of the story.
Australia’s ACMA phone and SMS scam guidance identifies pressure, unusual payment requests, impersonation and requests for sensitive information as warning signs. It advises against giving an unverified caller money, passwords, authentication codes or remote access.
For your own check, ask:
- What am I being asked to do immediately?
- Did I initiate the transaction or support request?
- What independent evidence supports the claimed problem?
- Can I check it through an existing account or official contact?
- Is the caller discouraging me from speaking to someone else?
A warning sign is a reason to pause and verify. You do not have to prove a criminal case before ending a call you do not trust.
Common suspicious-call scenarios and how to check them
The examples below are hypothetical illustrations. They describe requests worth checking, not reports about any specific phone number, business or individual.
A supposed account emergency
Hypothetical example: a caller says your account is under attack and insists you move funds while staying on the line. Focus on the proposed transfer. Open your account through your own app or contact the provider using details you already hold.
A useful question for the verified provider is: “Is there a genuine issue on my account, and what should I do through your normal process?” Do not let the original caller remain your only source of instructions while you investigate the claim.
A fee for a prize, refund or unexpected benefit
Hypothetical example: you are told that money is waiting for you, but you first need to pay an administrative charge. Put the promised reward aside and examine the immediate request: you would be sending money to obtain something you did not independently arrange.
Ask whether you can verify the underlying program, transaction or organization without using the caller’s link. If you cannot establish why the benefit exists, a confident voice should not fill the gap. You can decline the offer and keep your payment details private.
A delivery or order problem
Hypothetical example: a text says a parcel cannot be delivered until you confirm payment details. Check the original order through the merchant or delivery service you used. Compare the claim with the status shown there.
The FTC’s spam-text guidance describes fake delivery, invoice and account messages that lead people toward links or requests for information. It recommends checking through a known contact route rather than the unexpected message.
A caller offering urgent technical help
Hypothetical example: someone says they need access to your computer to fix a problem you did not report. Before installing anything or changing a security setting, contact the device maker or service provider yourself.
If you were already seeking help, match the conversation to the request you actually opened. A claim to be “following up” is not enough on its own. Keep ticket numbers and account information private while you check the support channel.
A family emergency or familiar-sounding voice
Hypothetical example: a caller appears to be someone close to you and asks for urgent financial help while insisting you keep it secret. Try an established contact route for that person or another trusted person who can help check the situation.
The FTC’s analysis of AI-enabled voice cloning explains that voice imitation creates fraud risks and that no single detection approach solves the problem. Do not make a sensitive decision depend solely on whether the audio sounds familiar.
Where caller ID and reverse phone lookup fit
A number search is useful when it leads to information you can assess: a sourced public business association, a reviewed report or an explanation of a number’s context. It is less useful when you treat a label as permission to follow the caller’s instructions.
You can look up a visible number while keeping the requested action on hold. Read the source and report descriptions, then decide whether a separate verification step is needed. RevealNames does not publish private saved-contact labels as verified identities, trace hidden callers or verify a current subscriber’s account.
If you need to understand an unexpected call rather than respond to an active request, use the who-called-me guide. For a screen without usable digits, use the private and unknown caller guide.
No reports does not mean a call is safe
A blank or limited record tells you that the search did not provide useful public evidence. It does not validate a caller’s instructions. Keep the same verification standard for a newly encountered number as for one with a long history of online discussion.
Similarly, a report category does not establish a caller’s legal identity. Read what the contributor actually experienced. Our spam database guide explains the difference between written reports, quick votes and search activity.
If you have already sent money
Contact the organization used for the payment immediately and explain that you believe it involved a scam. Ask whether a reversal, recall or other response is possible. The FTC’s recovery guide, updated June 2026, provides steps for cards, bank transfers, payment apps, gift cards, cryptocurrency and cash. Recovery is not guaranteed.
Have the transaction details ready for the provider’s secure process. Preserve receipts, reference numbers and the messages that led to the payment. Do not post these documents in a public phone-number report.
Prepare a clear description for your provider
You do not need a polished account before contacting support. Begin with the payment, when it happened and why you now suspect a problem. Distinguish a payment you were persuaded to make from a transaction you did not authorize; let the provider assess the circumstances.
Questions you can ask include:
- Which transaction details do you need through your secure channel?
- Is there an action you can take immediately?
- Should I take any additional steps to protect this account?
- What reference should I keep for follow-up?
- When and how should I check for an update?
Keep a private note of the answer and the case reference. A reverse directory cannot reverse the transaction or predict the provider’s decision.
If you shared a password, code or personal information
If you shared a password, follow the account provider’s official recovery instructions and change reused passwords on other accounts. Enable available additional authentication. If you cannot sign in, use the provider’s recovery route. The FTC recovery guidance also points US readers to IdentityTheft.gov for exposed identity information.
Explain precisely what you shared. A password, a one-time code, an identity document and a card number are different exposures. Telling the relevant provider which one was involved helps it give applicable instructions instead of generic advice.
If you installed software or allowed remote access
Follow trusted technical support, rather than accepting more instructions from the original caller. The FTC recommends updating security software, scanning for problems and securing accounts after unwanted device access. Use the same recovery guide for its current steps.
In your private notes, record what you installed, which device was involved and what you remember authorizing. Do not assume deleting a message or blocking the number has resolved account or device access. Ask the appropriate provider how to assess the remaining issue.
Preserve evidence without spreading private information
Build a short timeline: when contact began, what the caller claimed, what they asked you to do and which actions you took. Keep the displayed number separate from any callback number, payment destination or message link.
Use the provider or authority’s secure reporting process for receipts, screenshots and account details. For a public community report, remove private information and describe the behavior. You can explain that a caller claimed to represent an organization without asserting that the organization made the call.
This distinction helps other readers compare their experience while avoiding an unsupported allegation about the number’s subscriber. If a RevealNames record is misleading, send a correction request rather than publishing private information to prove your point.
Where to report scam calls and texts
The right destination depends on your country and what happened. These are official reporting routes, separate from a community contribution to RevealNames. A directory report is not automatically sent to police, regulators or your phone provider.
United States
Report fraud at ReportFraud.ftc.gov. For unwanted calls without a financial loss, the FTC’s phone-scam guidance points to DoNotCall.gov. Suspicious texts can also be forwarded to 7726 or reported through your messaging app, as explained in the FTC’s text-message guidance above.
The FCC complaint page covers unwanted calls/texts and situations where your own number is spoofed or mislabeled. The FCC does not resolve individual unwanted-call complaints. Contact your bank or account provider separately when money or access is involved.
Canada
The Canadian Anti-Fraud Centre directs fraud and cybercrime reports to reportcyberandfraud.canada.ca and accepts reports at 1-888-495-8501. Victims should also contact local police. The CAFC collects information to support investigations; local police investigate incidents.
For unwanted telemarketing, consult the CRTC’s telemarketing and unwanted-call resources to select the appropriate complaint route.
United Kingdom
Current Ofcom reporting guidance points readers in England, Wales and Northern Ireland to Report Fraud or 0300 123 2040. In Scotland, contact Police Scotland on 101. Report Fraud is the current service name; older material may say Action Fraud.
Suspicious mobile calls and texts can be reported to 7726, which alerts the mobile provider. Contact your bank promptly if a payment or account information was involved.
Australia
ACMA directs people to report scams to Scamwatch. Its phone and SMS guidance advises promptly contacting your bank and phone company when money or personal information has been stolen. Use the reporting and support links appropriate to the specific incident.
Other countries
Use your national consumer-protection, cybercrime or police reporting service. Contact the relevant payment or account provider as well. Do not assume another country’s short reporting code or complaint process works on your line.
Make the next unexpected call easier to handle
Create a small set of trusted contact routes before you need them: your provider’s app, the number printed on your bank card and important personal contacts. Keep a place for private incident notes so an unexpected call does not force you to organize everything under pressure.
Review your device’s screening and spam settings using the unknown-caller guide. Decide how you will check legitimate calls that are filtered. Agree with a trusted person that either of you can pause an urgent request and verify it through another channel.
The aim is a repeatable process: pause, identify the requested action, verify the claim and use the appropriate support route. A complicated story should not require an improvised decision every time.
Frequently asked questions about phone scams
How can I check whether a number is a scam?
Search for available public records and read report details, then assess the actual request. A number alone does not establish fraud or safety. If the caller claims to represent an organization, verify that claim independently before acting.
What should I do if I only answered the call?
End the conversation if it feels suspicious. Consider whether you shared information, made a payment or changed anything on a device. Those details determine the next step; answering alone does not establish that an account has been compromised.
Can a free phone lookup recover money or secure my account?
No. A free lookup can provide public context about a visible number. Payment recovery, account protection and device support require the relevant provider. Do not delay contacting it while trying to identify the caller.
Should I warn other people about the call?
You can share a factual description through the appropriate reporting route. Keep private account details out and distinguish the caller’s claimed identity from anything you verified. A clear account is more useful than an accusation based only on a display name.
Why does the guide include several countries?
Readers can receive unfamiliar calls wherever they live, but reporting services have jurisdiction-specific roles. Choose the route for your circumstances. Using a US, Canadian, British or Australian phone number does not by itself establish where the caller is physically located.