![]() ![]() ![]() |
|
NZLion:
2Degrees hasn't asked anyone to come to my apartment, and the callcentre agents have no idea why chorus require physical access
An excuse to delay your job? Chorus have lots on. Anything they can push off onto someone else is job temporarily off their list?
Mike
Definitely ping @ChorusNZ, I can't imagine that they wouldn't have a better insight into the situation - I know in my case, the information I got from 2Degrees versus the information I got from UFF was completely different, and I'd generally trust the LFC and Service Companies over the RSPs.
Anything I say is the ramblings of an ill informed, opinionated so-and-so, and not representative of any of my past, present or future employers, and is also probably best disregarded.
toejam316: I must admit, I was considering posting the details of my churn with 2Degrees on here - suffice to say, someone needs to look into their communication processes in getting info from the customer to the LFC. Through my employment, I have access to things like the UFF Helpdesk and NOC, which meant that over the course of near daily calls I managed to (through getting UFF to lodge information requests with explicit instructions) go from 2Degrees lodging a whole new install, to lodging a second port activation. It was like pulling teeth. It might be a rare occurrence, but it shouldn't be one at all. Once they get the service in, it's fantastic, but it isn't as difficult as they make out. Definitely ping @ChorusNZ, I can't imagine that they wouldn't have a better insight into the situation - I know in my case, the information I got from 2Degrees versus the information I got from UFF was completely different, and I'd generally trust the LFC and Service Companies over the RSPs.
Work for another RSP, looked at initial post and cringed, looks like a simple comms issue right? I've managed to get Chorus/UFF records on track provided I was convincing and had ONT serial numbers pretty easily. A month for an ONT activation is pretty bad.
Hi all,
NZLion has provided his details to us and we've taken a look at the situation. This particular case was a records issue on Chorus's side, which it took them a while to remedy. They had no record of that ONT in use on their network, nor services installed to that particular apartment, and as such needed to re-scope the address to confirm everything is there and correct, and get that loaded in to their system. This necessitated a new order to be run to pick up the updated details, which was done yesterday as requested by Chorus, and scheduling is now confirmed for tomorrow.
Had the records been correct from the get go, we would have had this connected quite a while ago.
Thanks
Ralph ^JOB
A text this morning from 2degrees telling me that I should be sorted sometime tomorrow. We shall see
That text was accurate
I phoned from work this afternoon and was told it was working. When I got home from work I had to alter a couple of settings at my end, after which I am now up and running.
Welcome to the Club.
What would one do without geekzone eh? You'd still be waiting!
2degreesCare:
Hi all,
NZLion has provided his details to us and we've taken a look at the situation. This particular case was a records issue on Chorus's side, which it took them a while to remedy. They had no record of that ONT in use on their network, nor services installed to that particular apartment, and as such needed to re-scope the address to confirm everything is there and correct, and get that loaded in to their system. This necessitated a new order to be run to pick up the updated details, which was done yesterday as requested by Chorus, and scheduling is now confirmed for tomorrow.
Had the records been correct from the get go, we would have had this connected quite a while ago.
Thanks
Ralph ^JOB
RemoteID mismatch?
joker97:
What would one do without geekzone eh? You'd still be waiting!
Correct.
The key is to process a request when the planets are aligned. Then take away the last number you though of.
|
![]() ![]() ![]() |