I mistakenly recharged a vodafore number (**********) of a friend for RS. **, which is...

GetHuman7084361's Kundendienstproblem mit Vodafone von Februar 2022

5 Ansichten | 634 ähnlich | 0 folgt
Hilfe bei meinem Vodafone Problem
First: share to improve GetHuman7084361's odds
Strength in numbers! Companies respond better when others are watching.
GetHuman7084361's next move: call Vodafone.
The best way to get your problem resolved is to tap the button below to start calling Vodafone. We will check on you later to see if it's fixed or needs to be escalated.
Before contacting them, items GetHuman7084361 may need:
Name des Kontoinhabers, Kontonummer, Rechnungsadresse, Telefonnummer des Kontos und die letzten 4 Ziffern der Sozialversicherungsnummer
The issue in GetHuman7084361's own words
I mistakenly recharged a vodafore number (**********) of a friend for RS. **, which is currently not in use. When calling the number it said "this number is not available". I want the recharged plan to be changed to another existing Vodafone number of mine (**********). I want the Vodafone customer care team to change the recharged plan from the number (**********) and add it to the number(**********).

GetHuman7084361 did not yet indicate what Vodafone should do to make this right.

How GetHuman7084361 fixed the problem

We are waiting for GetHuman7084361 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 Vodafone's attention and get better help faster. Tap below to get started.
Haben Sie auch Vodafone Probleme?
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 GetHuman7084361 fixes it.
This email address isn't valid

Vodafone

Kundendienstproblem
Reported by GetHuman7084361
Feb. 2., 2022 - vor 5 Monaten
Not resolved
Bisher von 5 Kunden gesehen
Ähnliches Problem wie bei 634 anderen
0 Kunden folgen diesem

Timeline

GetHuman7084361 hat begonnen, an diesem Problem zu arbeiten
Feb. 2. 3:36pm