Scam call with a fake charity angle; definitely not trustworthy.
Fidelity telemarketing call: red flags to know - +1 603-402-5051 ((603) 402-5051)
Resumen — +16034025051
Opinión del experto
Picture your phone lighting up with an unfamiliar number that claims to be Fidelity. When a call references a financial institution, treat it as a potential data‑privacy risk and pause before sharing any personal or account details. Verify the caller by hanging up and dialing the official 800‑number listed on the institution’s website, or log into your online account to check for messages. Keep a record of the number and consider adding it to your carrier’s block list. Report suspicious activity to the FTC and your bank’s fraud department. Maintaining privacy and verification steps helps you dodge scams and unwanted telemarketing.
Categorías del llamante
Nombres de llamantes
Detalles
Calificar este número — +16034025051
Reportes recientes para (603) 402-5051
I can confirm that this is a legitimate call from Fidelity, as the caller, John Conroy, provided a genuine callback number, 800-544-5372, which I verified through Google.
Yet anouther call from fideltiy with no messgae, how annoyning.
I'm fairly shure it's fidelity, Fixed income is calling me back because I got confused when I called them friday afternoon, thats my asumption
I didnt answer the call, and since it was supposably from Fidelity, I would have expected a message to be left, but none was, Fidelity doesnt operate in such a manner, it was clearly a scam call, and I wont be responding to such calls in the futer
Similarly to a previous experience, the caller claimed to represent Fidelity, leaving a message that seemed legitimate, although the number was unknown and therefore not answered.
This number didnt leave a message and was blocked by Verizon as spam
It is perplexing that Fidelity in NH would contact a CT resident via phone when all transactions are conducted online, and they have accessible 800 numbers.
This caller claims to represent fidelity, yet the communication has been persistently harassing
I'm unsure if this call was an error on the part of Fidelity or another caller.