NE
Nadia E

1 reviews | Active since Jun 2013

09 Oct 2017, 11:40

Really Bad Service Never Any Feedback

We have been having ongoing issues with regards to our connection Always being told it is our fault, we get over 300ms ping when doing a speedtest and the support service is really bad with a couple technicians.

A while back we logged a call with our connection being horrible and a technician came out changing a component on the dish stating we would be charge should that fix the issue. It never did.. I called and emailed the technician only for them to tell me that they are working on the tower. I had 2 neighbors across the road that use your service have no internet during that same time the tower was being repaired.

I got billed over R3000 this month with NO feedback from anyone at wirulink, I am always having to ask what is going on and this is by far one of the worst services I have ever experienced in my life, how can you bill a client without following up with them and checking to see if everything was ok, first of all the issue was never on our side always on your side.

I couldn't follow up with the query as I had my wedding and was on honeymoon when I realized such a some was removed from my account.

As soon as I can I am moving away from wirulink, I have family with you and getting them to move away from you too.

Going to social media the hell out of how bad this company is.

0
Replies (6)
WIRUlink Pty Ltd
WIRUlink Pty Ltd's reply10 Oct 2017, 21:40
Official

Dear Naida

With reference to your discussion with the Client Relations Manager, be assured that all efforts will be made to resolve this matter and follow-up with you on a regular basis.

On behalf of WIRUlink Management we would like to thank you for your feedback to better our service.

We are committed to our clients and service excellence.

Yours faithfully

WIRUlink Management

NE
Nadia E's update31 Oct 2017, 10:05
Reviewer Update
Unfortunately I have once again had no 'regular basis' feedback, No one has come back to me with regards to what is happening here. Feel like I have been ******.
WIRUlink Pty Ltd
WIRUlink Pty Ltd's reply10 Nov 2017, 16:04
Official

Dear Nadia

Thank you for contacting us.

We only have 1 ticket regarding billing address change that has been resolved.
29/10/2017 - You asked for your billing address to be changed. Saturday 29th October 2017
30/10/2017 - WIRUlink Accounts made the change and informed you via email.
30/10/2017 - You responded thanking us for the address change.

Every time you log a call, you will get a unique reference number to follow up on the progress of your request.

Do not hesitate to contact Shannon van Blerk (Service & Helpdesk Manager) should there be anything else that you wish to take up with us. We are committed to offer the highest levels of service to all our customers and keep on improving wherever possible.

Thank you for your continued support.

Yours faithfully

NE
Nadia E's update10 Nov 2017, 21:33
Reviewer Update
I'm not sure why you posted that as the issue I had was money taken from us regarding issues we were having and Wirulink saying we were the problem and no feedback with regards to the issues. We will be contacting Shannon regarding the money that was wrongfully taken from us.
NE
Nadia E's update11 Nov 2017, 22:46
Reviewer Update
Can you explain why my ping always looks like the below: Pinging 8.8.8.8 with 32 bytes of data: Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Request timed out. Reply from 8.8.8.8: bytes=32 time=32ms TTL=52 Reply from 8.8.8.8: bytes=32 time=33ms TTL=52 Reply from 8.8.8.8: bytes=32 time=36ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=31ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=40ms TTL=52 Reply from 8.8.8.8: bytes=32 time=31ms TTL=52 Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=32ms TTL=52 Reply from 8.8.8.8: bytes=32 time=33ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=31ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=31ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Request timed out. Request timed out. Request timed out. Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Request timed out. Reply from 8.8.8.8: bytes=32 time=37ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=33ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=41ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=40ms TTL=52 Reply from 8.8.8.8: bytes=32 time=36ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Request timed out. Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=34ms TTL=52 Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=32ms TTL=52 Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=33ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Request timed out. Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=32ms TTL=52 Reply from 8.8.8.8: bytes=32 time=36ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Request timed out. Reply from 8.8.8.8: bytes=32 time=46ms TTL=52 Reply from 8.8.8.8: bytes=32 time=36ms TTL=52 Reply from 8.8.8.8: bytes=32 time=31ms TTL=52 Reply from 8.8.8.8: bytes=32 time=33ms TTL=52 Reply from 8.8.8.8: bytes=32 time=35ms TTL=52 Reply from 8.8.8.8: bytes=32 time=33ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=32ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=31ms TTL=52 Reply from 8.8.8.8: bytes=32 time=51ms TTL=52 Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=31ms TTL=52 Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=35ms TTL=52 Request timed out. Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=31ms TTL=52 Reply from 8.8.8.8: bytes=32 time=31ms TTL=52 Reply from 8.8.8.8: bytes=32 time=31ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=31ms TTL=52 Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=31ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=33ms TTL=52 Reply from 8.8.8.8: bytes=32 time=32ms TTL=52 Reply from 8.8.8.8: bytes=32 time=33ms TTL=52 Request timed out. Request timed out. Request timed out. Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=32ms TTL=52 Request timed out. Reply from 8.8.8.8: bytes=32 time=31ms TTL=52 Request timed out. Reply from 8.8.8.8: bytes=32 time=44ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Request timed out. Request timed out. Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=35ms TTL=52 Request timed out. Reply from 8.8.8.8: bytes=32 time=79ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=34ms TTL=52 Reply from 8.8.8.8: bytes=32 time=50ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=31ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=33ms TTL=52 Request timed out. Reply from 8.8.8.8: bytes=32 time=29ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=34ms TTL=52 Reply from 8.8.8.8: bytes=32 time=34ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52 Reply from 8.8.8.8: bytes=32 time=30ms TTL=52
WIRUlink Pty Ltd
WIRUlink Pty Ltd's reply13 Nov 2017, 08:26
Official

Dear Nadia

Sierra Tech

It is normal for the latency/ping to be 25-40ms on a wireless connection and a stable ping shows a good quality connection.

Our team will contact you to find out if there are any other specific problems you're experiencing.

Yours faithfully

WIRUlink Management