I am not sure if anyone else encountered this problem with Globe SuperDuo or Duo landline service. The landline number should be retained if you renew the registration in 30 days; however, my number got replaced even if I renewed my SuperDuo registration within 24 hours!
It usually takes me less than 5 minutes to do the re-registration with a prepaid sim but it wasn’t the case last night. I had difficulty renewing my SuperDuo service.
After sending SUPERDUO MM 599 to 8888, I received the usual text message that I have to reply with ‘YES’ to 8888 to complete registration. I promptly replied ‘YES’ to 8888 but the system rejected my registration:“Sorry, we cannot process your GLOBE SUPERDUO request at this time. Please try again later.”
That is exactly what I did.
I sent another re-registration to 8888 but I received the ‘error’ yet again.
I failed at least 3 times so I thought I should wait for a few hours to try the registration out once more.
After a few hours, I sent the re-registration — I replied ‘YES’ to the text prompt — alas! I got my SuperDuo service re-activated… but I got a NEW number! :( My old number got replaced.
I am not mad. I am just sad and disappointed because I am using this service faithfully for the last 6 months and it screwed up! I like my old number back so I hope @Talk2Globe would response to my tweets immediately. I really hope I can get my old number back.
For the third time in three months now, every time my Super Duo expires Globe seems to forget that there is a 30-day grace period. Again, a new number is issued to me even if I should have retained my previous number. I have complained several times about this and it seems that Globe doesn’t bother to address this issue with prepaid users. Sure, it is easy to just change sim card but the system is faulty and that’s why I am complaining. If you can do something about it, fix it. If you can’t let your customers know. Don’t ignore it!
I posted a new post about Globe Super Duo on February 2011 and When I renewed my Super Duo subscription on March 2011, the problems described here have been resolved already.