Report a suspected phone scam to the organisation that can act on the harm: your bank for money or banking access, your mobile provider for SIM or service compromise, and SAPS for a suspected crime. SMS spam, unwanted content billing and unresolved service complaints have separate reporting routes.
Do not delay account protection while trying to prove who owns the displayed number. Caller ID can be masked, and a person named by a search result may not have made the call. Save what you actually observed and distinguish it from what the caller claimed.
Checked 1 November 2026. The links below lead to official provider, industry or regulator pages. No report is sent by reading this guide, and SIMcloud does not collect your complaint or identity documents here.
If you shared details, approved access or paid money
- End the suspicious interaction. Do not continue following instructions from the caller.
- If money, card details, banking credentials or approvals are involved, contact your bank through its official app, the number on your card or its independently obtained website.
- If there is an unexpected SIM swap, port notification or loss of service, contact your own mobile provider from another available channel.
- If software was installed or remote access granted, tell the bank and account provider. Use a separate trusted device or phone for those contacts where possible.
- Preserve messages, call timestamps, references and transaction records. Ask each organisation what evidence it needs and keep the case references.
Ask the bank or provider to assess protective actions for the affected account. A report does not guarantee that a payment can be reversed. Do not pay a second person claiming to recover the money for an upfront fee.
FNB's vishing guidance describes callers impersonating bank staff and requests for sensitive details or software installation. SABRIC also explains impersonation and masked telephone numbers. Use those warnings to act on the request itself, rather than trusting a familiar name or display number.
Where to report each kind of problem
| Situation | First route | Keep in mind |
|---|---|---|
| Money sent, card exposed, suspicious banking approval | Your bank's official fraud/account-security channel | A network complaint does not protect a bank account. |
| Unexpected SIM swap, port or loss of service | Your current mobile service provider | Report your own affected line and any notices, not just the caller's prefix. |
| Fraudulent call or message using a provider's name | The provider's published fraud or customer-care route | Record the impersonation claim without assuming the provider made the call. |
| Suspected crime, threats or financial fraud | SAPS reporting process | Use 10111 for a police emergency; ordinary reports go through a police station. |
| Unsolicited commercial SMS or SMS scam | WASPA's SMS reporting form | Its scope and action depend on the sender and membership information available. |
| Unwanted WASP/content charges | Your provider and WASPA unwanted-billing support | Use the unwanted-billing route, not just a spam report. |
| Unresolved communications service complaint | Provider first, then ICASA's complaints procedure where applicable | Follow the current escalation requirements and supply the provider reference. |
| Misuse of personal information or an unresolved privacy-rights request | The organisation's privacy contact, then Information Regulator where applicable | That process is separate from urgent bank protection and a criminal complaint. |
Network reporting routes
Contact your own service provider about compromise of your own line. If reporting the apparent origin of a call or SMS, describe that number as displayed or claimed: a prefix or lookup does not prove which party originated it. For a virtual operator, start with the provider on the service agreement rather than assuming a host network handles the retail account.
| Provider | Official starting point | Scope |
|---|---|---|
| Vodacom | Fraud, scams and hoaxes help; customer care 082 135 from the official contacts | Ask for the appropriate account-security or fraud process. Do not use an incoming caller's substitute helpdesk. |
| MTN | Report fraud help; customer care 135 on MTN or 083 135 from other networks | The current customer-support table also publishes 083 135 4357 for fraud. |
| Cell C | Scams and hoaxes guidance; 135 on Cell C or 084 135 via the support FAQ | Ask customer care to route the fraud or SIM-security report. |
| Telkom | Official scam alerts list fraud hotline 0800 124 000. | For an affected mobile account, also use your authenticated Telkom support route. The fraud hotline is not a promise to reverse a bank transaction. |
Call charges and access can depend on your provider and location. If a route changes or is unavailable, navigate from the provider's official site to its current support page. Never send a full ID document, OTP or bank statement to a contact merely because it appears in an unsolicited message.
What evidence to preserve
- The displayed number or sender label, including the country code if shown.
- Call or message date, time, channel and the number that received it.
- What the caller claimed and what they asked you to do.
- Original messages, voicemail and relevant screenshots already available to you.
- Any link received, recorded as evidence without opening it again.
- Payment details, bank references and account-security notifications, shared through the recipient's secure channel.
- Provider, bank and police references already obtained.
Keep originals where possible and make a separate short timeline. Do not edit the message and then present the edited copy as the original. When sharing screenshots, remove unrelated people's details from the copy while retaining the original privately for an authorised investigator if needed.
Do not include passwords or OTPs in an ordinary report. If an organisation needs identity or payment documents, ask it for the correct secure submission method. Do not publish the bundle of evidence in a social-media thread.
A concise incident summary you can use
On [date] at [time], I received a [call/SMS/message] displaying [number or sender]. The caller claimed to represent [organisation] and asked me to [request]. I [did/did not] share details, approve access or send money. The relevant transaction reference is [reference, shared privately]. I have preserved [evidence]. Please advise the appropriate protective action and provide a case reference. The caller's identity has not been independently verified.
Add only information you know. If a caller-ID app supplied a name, label it as an app result rather than a verified subscriber identity. Keep a copy of what you sent and note the route used.
Reporting a suspected crime to SAPS
SAPS's reporting guidance directs victims to the nearest police station for a crime report and identifies 10111 for emergencies. Its emergency call-centre guidance distinguishes emergency assistance from ordinary enquiries. Do not use an emergency line merely to identify a missed caller.
Bring the incident timeline and relevant evidence to the station. Keep the CAS reference supplied for a registered case and use it for follow-up. A bank complaint reference and a network ticket are separate records; keep each associated with the organisation that issued it.
A post on social media or a general website contact message is not a substitute for the appropriate police reporting process. SAPS's contact guidance explicitly distinguishes its general website channel from reporting a crime.
SMS spam, subscriptions and direct marketing
For unsolicited commercial SMS, use WASPA's reporting form with the sender, content and timestamp. The organisation explains that identifying a member can enable member-directed action; an unidentified sender report can instead contribute to monitoring. It is not a universal phone-scam police service.
Unexpected content charges need the provider's billing investigation and WASPA's unwanted-billing process where applicable. Blocking the sender does not establish that the paid service has been cancelled. Ask for the service name, provider, charges, cancellation confirmation and any dispute reference.
For a known legitimate marketer, use its verified opt-out route and keep evidence if contact continues. WASPA's linked Do Not Contact service applies within its stated membership rules; do not describe it as blocking every phone call or criminal message. For personal-information complaints, follow the organisation's privacy route and the Information Regulator's current instructions.
Block and follow up after preserving evidence
Use your phone or messaging app's block/report function once you have saved what you need. App-specific reports are separate from a network, bank or police report. Keep a simple log of references and promised next steps so you can follow up without retelling the entire incident.
If the provider does not resolve a communications service complaint, review ICASA's current escalation procedure. It also directs SMS spamming and content-service billing matters to WASPA. Select the correct channel rather than sending the same sensitive evidence to every address you find.
Scam-reporting questions
Do I need to find the owner's name before reporting?
No. Report the observed number, time, content and harm, and say that the identity is unverified. See the unknown-caller guide for why a name label is insufficient proof.
Can a network lookup show that the call was fraudulent?
No. It checks supported network information, not the caller's intentions or identity. Do not wait for a lookup when money or account access is at risk.
What if the caller says a SIM was registered using my ID?
Contact the claimed provider independently and request an investigation of your own record. Use the RICA-check guide; do not provide documents to the unsolicited caller.
Will reporting guarantee a refund or stop all future calls?
No. Protective action, investigation, payment recovery and device blocking are separate processes. Keep the references and ask each organisation what it can do in your case.