Openserve Line Migration Maddness

After all my complaining and moaning my line is moved.
I am now with CISP..

ISP: Cool Ideas Service Provider (Pty) Ltd
Ping: 4ms
Download: 94.15Mbps
Upload: 49.27Mbps
Test your speed: http://speedtest.co.za

Network seems fine I am just worried about their customer support...
Guess we will see how it goes for now.
I still have this sour taste in my mouth from this whole experience.

Ok so some feedback. I have only had one issue so far when the line was completely dead for about 20min.
Speed also fluctuates but for the most part stays 90+Mbps.


ISP: Cool-ideas
Ping: 4ms
Download: 91.55Mbps
Upload: 48.32Mbps
Test your speed: http://speedtest.co.za
 
And just for the sake of another joke, I have one more line that also need to be migrated from WA to CISP. Knowing what I know and my newly found skills of dealing with the migration, please see how this ISP screws up plans:

---COPY OF TICKET XXXX RESPONSE WITH WA--
Please read through this ticket and confirm that you would be happy and that everything is in order, based on the timeline below:

1. On 2019 - 06 - 01 17:11 - > I execute the cancellation procedure on your portal for this service. Interestingly, you decide the line will not be cancelled at the end of June, but the end of July instead...2 month notice then, not one month - which I accept....

2. On 10/06/2019 09:50 - > I informed you that the line is cancelled and requested that the line be placed in the holding pool by 31 July. I also specifically indicated the issues that will be experienced and warned you that the line release request needs to be done on 1 July to take the OpenServe calendar month notice period into account.

3. 10/06/2019 12:06 - > you confirm receipt and indicate that there will be no hick ups.

4. 10/06/2019 12:33 - > I double check with you again to double and triple check you execute the release correctly.

5. 10/06/2019 14:04 - > You confirm all is in order, and the line will be released as requested on 1 July 2019. In fact, you could have placed the order on this day as OpenServe requires a 1 month calendar notice anyway.

6. 30/06/2019 19:52 - > I open ticket ##### (which you chose to close without response) in which I request, remind and check with you that the request for the line release will be made.

7. 02/07/2019 09:06 and 09:08 - > After no response from WebAfrica, I request clarification once again that the request to release with OpenServe has been made

8. 02/07/2019 14:53 - > You respond and claim the request with OpenServe was logged.

9. 02/07/2019 15:02 - > I request WHEN the request with OpenServe was logged, It should have been done on 1 July or before the time to honor the 1 calendar month notice with OpenServe and to release the line on 31 July 2019

10. 03/07/2019 08:53 - > You indicated that the request with OpenServe was not made in time, despite all my efforts to ensure the request at OpenServe is made in time.

11. 03/07/2019 09:13 - > Once again, I ask for confirmation that the original request and agreement was executed. Clearly this was not done.

12. 03/07/2019 11:38 - > You confirm that WebAfrica did not execute the request, and instead of the line being released on 31 July, it will now only be released on 31 August 2019!

What more could I have done??

Here is how this is going to play out now, and I can confirm this as I have been through this before:
a. the WebAfrica account will currently be cancelled on 31 July 2019, but on this date I can do nothing as the line is not released into the holding pool on 1 August as requested so many times
b. For the entire month of August, I will not have a service as the new ISP cannot take control of the line
c. on 1 September, the new ISP will be able to take control of the line and I will have a service again.

So now answer your question: "Please advise if this is in order?" - Would you find the above in order...

Going forward:
As explained, I cannot afford to have no service for a 1 month period, and the following will now need to be executed by WebAfrica:
i. The current account is set to expire on 31 July 2019. Clearly this cannot happen...
ii. Please ensure that the existing account is carried through and is only cancelled on 31 August 2019, instead of 31 July 2019.
iii. Please confirm in writing that the account is extended for cancellation by 31 August 2019

Lastly,
a. I would expect a manager within WebAfrica to pickup and review this ticket, the service executed in the ticket and provide some level of response.
b. That WebAfrica review their line cancellation and execution procedures.

------END OF MY LAST RESPONSE TO WA-----

So my take on this - I think the ISPs are in the wrong here. If they execute their cancellation procedures correctly, none of the consumers would have issues with migrating between ISPs....

O fun...here I go again!
 
And just for the sake of another joke, I have one more line that also need to be migrated from WA to CISP. Knowing what I know and my newly found skills of dealing with the migration, please see how this ISP screws up plans:

---COPY OF TICKET XXXX RESPONSE WITH WA--
Please read through this ticket and confirm that you would be happy and that everything is in order, based on the timeline below:

1. On 2019 - 06 - 01 17:11 - > I execute the cancellation procedure on your portal for this service. Interestingly, you decide the line will not be cancelled at the end of June, but the end of July instead...2 month notice then, not one month - which I accept....

2. On 10/06/2019 09:50 - > I informed you that the line is cancelled and requested that the line be placed in the holding pool by 31 July. I also specifically indicated the issues that will be experienced and warned you that the line release request needs to be done on 1 July to take the OpenServe calendar month notice period into account.

3. 10/06/2019 12:06 - > you confirm receipt and indicate that there will be no hick ups.

4. 10/06/2019 12:33 - > I double check with you again to double and triple check you execute the release correctly.

5. 10/06/2019 14:04 - > You confirm all is in order, and the line will be released as requested on 1 July 2019. In fact, you could have placed the order on this day as OpenServe requires a 1 month calendar notice anyway.

6. 30/06/2019 19:52 - > I open ticket ##### (which you chose to close without response) in which I request, remind and check with you that the request for the line release will be made.

7. 02/07/2019 09:06 and 09:08 - > After no response from WebAfrica, I request clarification once again that the request to release with OpenServe has been made

8. 02/07/2019 14:53 - > You respond and claim the request with OpenServe was logged.

9. 02/07/2019 15:02 - > I request WHEN the request with OpenServe was logged, It should have been done on 1 July or before the time to honor the 1 calendar month notice with OpenServe and to release the line on 31 July 2019

10. 03/07/2019 08:53 - > You indicated that the request with OpenServe was not made in time, despite all my efforts to ensure the request at OpenServe is made in time.

11. 03/07/2019 09:13 - > Once again, I ask for confirmation that the original request and agreement was executed. Clearly this was not done.

12. 03/07/2019 11:38 - > You confirm that WebAfrica did not execute the request, and instead of the line being released on 31 July, it will now only be released on 31 August 2019!

What more could I have done??

Here is how this is going to play out now, and I can confirm this as I have been through this before:
a. the WebAfrica account will currently be cancelled on 31 July 2019, but on this date I can do nothing as the line is not released into the holding pool on 1 August as requested so many times
b. For the entire month of August, I will not have a service as the new ISP cannot take control of the line
c. on 1 September, the new ISP will be able to take control of the line and I will have a service again.

So now answer your question: "Please advise if this is in order?" - Would you find the above in order...

Going forward:
As explained, I cannot afford to have no service for a 1 month period, and the following will now need to be executed by WebAfrica:
i. The current account is set to expire on 31 July 2019. Clearly this cannot happen...
ii. Please ensure that the existing account is carried through and is only cancelled on 31 August 2019, instead of 31 July 2019.
iii. Please confirm in writing that the account is extended for cancellation by 31 August 2019

Lastly,
a. I would expect a manager within WebAfrica to pickup and review this ticket, the service executed in the ticket and provide some level of response.
b. That WebAfrica review their line cancellation and execution procedures.

------END OF MY LAST RESPONSE TO WA-----

So my take on this - I think the ISPs are in the wrong here. If they execute their cancellation procedures correctly, none of the consumers would have issues with migrating between ISPs....

O fun...here I go again!

I'm moving from Supersonic to Macrolan 25 July.... This is going to be fun. :rolleyes: I continually ask them for the cancellation order number so I can give it to Macrolan but they said no only when I pay the last invoice will the line be moved to the holding pool not before.
 
I'm actually also very keen in Bitco... Can I contact you for some help also?




CI is going to hate me for this.

In the last 2 months I've helped 7 people sign up with Bitco that originally signed up with CI, all because CI somehow keeps dropping the ball.

Example:
This happened in march-
Person, lets call them A, paid Vumatel their installation fees, 2 years before, when vuma were laying cables in their area. Vuma installed it all back then.
A never used the fibre. Then their work changed and they needed more data. So they decided to finally get fibre.
They decided on CI. Signed up. Waited, waited, waited.... A also kept calling CI.
March my phone rings. You can hear the near hopelessness in gent's voice. A had applied with CI 3 months before.
I helped A sign up for Bitco Home Fibre.
There were things Vuma had to do on their side as the line was unused for more than 6 months, so that caused a delay, but Bitco and I made sure A had working fibre asap, and 5 working days later A had working fibre. It was only 5 because we had to wait for Vumatel.

There are many other threads, recently, about CI dropping the ball.

Bitco Home Fibre does resell Openserve fibre, so if you want I can help you getting going with Bitco. They offer uncapped, unshaped and unthrottled internet and they also do VOIP services.
 
Top
Sign up to the MyBroadband newsletter
X