I received a call at **:** PM ******* from ***-***-**** and went to my voice mail. It t...

GetHuman5883557's customer service issue with Verizon Wireless from March 2021

Help with my Verizon Wireless issue
First: share to improve GetHuman5883557's odds
Strength in numbers! Companies respond better when others are watching.
Before contacting them, items GetHuman5883557 may need:
PIN on Account, Name of Account Holder, Phone Number on Account, Email on Account, Billing Address on Account, and Last 4 of Social Security
The issue in GetHuman5883557's own words
I received a call at **:** PM ******* from ***-***-**** and went to my voice mail. It told me something about a dispute on ***-***-****. Then I hit the call back to ***-***-**** and got a recording that all Verizon operators were busy. So I went to my computer to look up the area codes and saw that both *** and *** had scams going. My question is since I did not speak to anyone is there still a way they could charge those *** calls to my number??

GetHuman5883557 did not yet indicate what Verizon Wireless should do to make this right.

How GetHuman5883557 fixed the problem

We are waiting for GetHuman5883557 to fix the problem and share the solution with the rest of us customers.

Do you have a customer issue as well?
We can help you get Verizon Wireless's attention and get better help faster. Tap below to get started.
Help from Real People?
If our free tools aren't enough, we partner with a US-based company with live tech support experts available 24/7. Take advantage of a $1 one-week trial membership and chat with an expert now.
Chat with a Live Expert
Having Verizon Wireless issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
This email address isn't valid

Verizon Wireless

Customer service issue
Reported by GetHuman5883557
Mar 24th, 2021 - 2 months ago
Not resolved
Seen by 4 customers so far
Similar issue to 7538 others
0 customers following this

Timeline

GetHuman5883557 started working on this issue
Mar 24th 6:47pm