Please come and get your modem. I no longer have WOW. NAME: Pamela Sample ADD: **** E...

GetHuman-peechizb's problème de service client avec WOW! de mai 2022

14 vues | 695 similaire | 0 suivant
Aide sur mon problème WOW!
First: share to improve GetHuman-peechizb's odds
Strength in numbers! Companies respond better when others are watching.
GetHuman-peechizb's next move: try calling WOW! again.
The best way to get your problem resolved is to tap the button below to start calling WOW!. We will check on you later to see if it's fixed or needs to be escalated.
The issue in GetHuman-peechizb's own words
Please come and get your modem. I no longer have WOW. NAME: Pamela Sample ADD: **** E **th st** Chicago, IL *****. PH:***-***-****

GetHuman-peechizb did not yet indicate what WOW! should do to make this right.

How GetHuman-peechizb fixed the problem

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

Prefer a step by step guide?
We've taken the time to write instructions for how to solve some of the most common WOW! customer problems.
Comment puis-je obtenir un remboursement de Wow ?Comment récupérer mon nom d'utilisateur ou mon mot de passe avec Wow?
Do you have a customer issue as well?
We can help you get WOW!'s attention and get better help faster. Tap below to get started.
Vous avez également WOW! problèmes?
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
Follow this issue
See how GetHuman-peechizb fixes it.
This email address isn't valid

WOW!

Problème de service client
Reported by GetHuman-peechizb
mai 20, 2022 - il y a 5 mois
Not resolved
Vu par 14 clients jusqu'à présent
Problème similaire à 695 autres
0 clients suivant ce
Items needed
PIN sur le compte
Nom du titulaire du compte
Numéro de téléphone sur le compte
Courriel sur le compte
Adresse de facturation
4 derniers de la sécurité sociale

Timeline

GetHuman-peechizb a commencé à travailler sur ce problème
mai 20 4:30pm