Excess charged from Consumer Cellular phone on July ******.*Amount $**.** and multiple...

GetHuman3218632's customer service issue with Wells Fargo from July 2019

Help with my Wells Fargo issue
First: share to improve GetHuman3218632's odds
Strength in numbers! Companies respond better when others are watching.
Before contacting them, items GetHuman3218632 may need:
Name on the account, Billing address, Account holders birthday, Last 4 of SSN, and Full card number
The issue in GetHuman3218632's own words
Excess charged from Consumer Cellular phone on July ******.*Amount $**.** and multiple times (** times). The consumer Cellular phone agent said they only charged only one times and the ** others are mistaken by their system, they will make a cancelation. So, right now my account posted and all the amount $**.** have been charged. Please help me to resolve the case as above. Thanks.*My account* xxxx****

GetHuman3218632 did not yet indicate what Wells Fargo should do to make this right.

How GetHuman3218632 fixed the problem

We are waiting for GetHuman3218632 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 Wells Fargo's attention and get better help faster. Tap below to get started.
Having Wells Fargo 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

Wells Fargo

Customer service issue
Reported by GetHuman3218632
Jul 9th, 2019 - a year ago
Not resolved
Seen by 11 customers so far
Similar issue to 3789 others
0 customers following this

Timeline

GetHuman3218632 started working on this issue
Jul 9th, 2019 2:17pm
GetHuman3218632 indicated the issue is not fixed yet.
Jul 9th, 2019 7:33pm
GetHuman3218632 confirmed the issue is fixed. Hooray!
Jul 10th, 2019 7:59pm
GetHuman3218632 indicated the issue is not fixed yet.
Jul 10th, 2019 8:02pm
GetHuman3218632 confirmed the issue is fixed. Hooray!
Jul 11th, 2019 11:43am
GetHuman3218632 indicated the issue is not fixed yet.
Jul 11th, 2019 11:47am