Reliance Infocomm. Where is it headed?
July 1st, 2005 Leave a comment Visited 22 times, 2 so far today
Reliance Infocomm. Where is it headed?
Admittedly, it has come much under the scanner for all the wrong reasons. Call rerouting, CBI enquiries et al. Plus, the top brass has deserted the ship (not yet sinking). What Anil Ambani can possibly do to iron out the mess here? One thing that they could do is to iron out the chinks in the billing. Increased focus on the customer care would earn them a few brownie points.
I expect some kind of a roll out. Current media reports hint at fixed wireless phone as the likely candidate to be promoted. However, their fixed wire line phones go on un-noticed by a vast majority. I have not noticed any advertisements and it seems like that they are betting big on the same. Expect to hear more on that.
Plus, the BB rollout. At least we would have a clear idea and focus as to where it is headed for. There is a lot of publicity for the same; hope it is worth it. So far, no firm plans. I am sure Reliance is going to bet big on the same. Could we see more of screw-up with VSNL? Smarting under loss of customers and falling revenues in ISP business, VSNL is clearly a sinking ship. Staffed with mental retards, it still has the hangover of the monopolistic era when it ruled the roost. BSNL, its ugly sister, is betting big on International Long Distance telephony-its bread and butter and Reliance is snipping at its bandwidth business. Matter of time before VSNL changes its spots.
It is too early to say as to how Anil would steer the company out of present impasse. Splitting up the “empire†was stupidity- they could achieved far greater synergies together rather than alone. Perhaps much more power and clout than they have all alone.
Watch this space.
This post was submitted by Dr. Abhishek Puri on the Broadband Blog on Techwhack.
|
TechWhack on Facebook
|

This website uses IntenseDebate comments, but they are not currently loaded because either your browser doesn't support JavaScript, or they didn't load fast enough.