Iffy, but let me rephrase then: it seems to be up to the customer to educate themselves in favour of Vodacom spending money on preventative measures...
On this username. And even I still don't understand the ins and outs of your products...
Which is great for those new contract subscribers. Prepaid customers don't get the luxury. Nor do old subscribers. I was a Vodacom subscriber for many years and never once in all of my data usage and OOB shocks did I ever get any notifications, letters or even advice from the call centre on the subject. Maybe things have changed, but then again I was using bundles purchased from USSD codes up until 2 months ago. At no point between sale, use and OOB did I receive anything in the way of information relating to OOB whatsoever, and the notifications for "you have 3MB left" were sometimes delayed by a good few hours. The Vodacom website wasn't much help either...
Having never seen one of these communications I can't really comment on this...
I agree. And that works both ways, especially when customers, current or ex, attempt to provide feedback based on their own experiences. You cannot just wash your hands of the situation because you sent out 3 letters. At the end of the day, if OOB shocks are still commonplace, then something is amiss and needs to be addressed on your end. In fact screw commonplace - if they are even still a possibility...
I'm not attacking Vodacom, let's just be clear. I've made a point of referencing all networks in my posts but in this case, Vodacom are the OP's network in question. I'm glad you've PMd her though - great stuff. I'd prefer to see something more proactive done on Vodacom's side.
See this standard vs advanced baloney has to go. Your costs are static (in terms of comparing the two). So one can only assume that the reason for there being two different playing fields and costings is a forecast one. Vodacom forecast OOB usage income. Which further highlights that you are trying to milk customers for going out of bundle. Unless you dont, in which case you would agree that doing all you can to prevent these is the only option. I believe this sort of penalty is ludicrous and predatory. Predatory in the sense that this income is made off non tech-savvy customers of yours who have no idea what all of this malarkey is about, but will have to pay when the day comes.
Then we have various methods of notification for OOB, which appear to be failing. Now you can either continue passing the blame on to your customers or you can accept some responsibility here to change things. See you use the 8ta one as an example, and I can see your argument being along the lines of wasting data having a download cancelled mid-way. This is easily resolved by having a notification pop up each time you open a new session, showing your balance and a warning to ensure that you have sufficient data for your browsing and downloading session. Simple solution to what you're trying to turn into a very complex problem. No need for 20 different types of notifications that sometimes work and are often delayed.
We then have contract data restrictions being set by default to ridiculously high amounts. Why? If you're aware of the problem, why are you not doing something about this? The few people who do use those large amounts of OOB data would surely prefer to be blocked and call Vodacom to be told their balance and how to better use data without being ripped a new one. The others who are okay with OOB bills of R10k+ are in the absolute minority. It really is a win-win for you to set your limit far lower and eliminate this shock-bill nonsense. Seems almost illogical to NOT do so, unless you're forecasting this revenue. In which case shame on you and your predatory tactics.
For the record, I am an equal basher for all consumer rights. It just appears that I fight Vodacom more often than not because you choose to engage with us, which is a great thing and thanks for that...












Reply With Quote
What is incomprehensible to me, and what I've never heard properly addressed, is why the convoluted process to avoid OOB is even necessary, why not completely eliminate the risk by introducing something as simple as Keeper's suggestion? 

Bookmarks