SO
Steffen O

1 reviews | Active since Sept 2016

22 Sept 2016, 11:46

Stil waiting.... 22 days and counting

<p>I received a call from someone at Vodacom on 2016-08-18 suggesting to change my package from a Smart S to a uChoose Smart S.</p> <p><br />I was very hesitant to change as I was happy with my contract, mainly because I got an extra 800mb data (promotional). During this call I asked several times if I would still get this promotional extra data. He repeatedly assured me that I would still get the same. This turned out to be incorrect and I did not get the promotional data anymore.<br />Now I get only 200mb instead of 1Gb....for R20 p/m more! Please note that the amount of data I get is the only important thing for me.</p> <p><br />I feel as if Vodacom ******* me.</p> <p><br />I then phoned Vodacom customer care on 1 September and they could not assist me. Only got a service request number. NO one called me back.<br />A week later I phoned again and got new service request no. but still no one called me back.</p> <p><br />Today 22 September I called customer care again.... That's 22 days now... and all I got was 'wait for someone to call me'</p> <p><br />Basically all I want is my contract to be changed to what I had (incl. Promotional data)<br />Is that too much to ask?</p> <p> </p> <p> </p>

0
Replies (4)
Vodacom
Vodacom's reply22 Sept 2016, 12:33
Official

Dear Customer,

Thank you for making us aware of your complaint.

Kindly be advised that a consultant will make contact with you in due course to assist with your query.

***Please note*** Beware of phishing ****s.

Vodacom will not contact you via Whatsapp to request your personal details

Regards,
Vodacom Consumer Website Team

Vodacom
Vodacom's reply28 Sept 2016, 09:25
Official

As per our telephonic discussion, this query has been resolved.

Regards,

R. Maart

SO
Steffen O's update28 Sept 2016, 09:37
Reviewer Update

Thank you Vodacom for resolving this issue for me beyond what I expected.

SO
Steffen O's update17 Jan 2017, 10:39
Reviewer Update

This issue seems to have been 'Un-Resolved'. Back to square one.....