Optus - Faults: Constantly having drop outs, the phone rep kept...
Optus - Faults Ulasan pelanggan oleh pengguna GetHuman ~Ada dari November 13, 2017
Background on ~Ada's case
GetHuman: ~Ada - can you tell our other Optus - Faults customers when your case took place?
~Ada: Yeah. It was morning, on November 6.
GetHuman: Did you reach out to Optus - Faults, and if so, how?
GetHuman: And which of these common Optus - Faults customer issues best describes the reason you wanted to talk to them?
(Shows ~Ada a list of common Optus - Faults problems)
~Ada: "Account access" was why I was trying to call.
~Ada's review of Optus - Faults customer service
GetHuman: So how would you sum up your experience for GetHuman's Optus - Faults customer community? We'll censor any IDs, numbers, or codes and any inappropriate words here out of respect to the millions of other customers using this resource.
~Ada: Constantly having drop outs, the phone rep kept putting me on hold to "talk to a supervisor" had me clearing cookies... ridiculous, * weeks later the problem is still there despite a Tech coming out and stating the problem was on the pole outside, well no suprises it's STILL a problem.
GetHuman: Let's quantify your experience contacting Optus - Faults. On a scale of 1 to 5, how easy is it go get help on a Optus - Faults problem?
~Ada: I'd give them a four out of five for ease of finding your way to help.
GetHuman: What about quality of communication. How would you rate that on a 1 to 5 scale?
~Ada: I'd give them a five out of five on communication.
GetHuman: And what about Optus - Faults's ability to quickly and effectively address your problem?
~Ada: For that I would say two out of five.
GetHuman: And finally- any advice for other Optus - Faults customers?
~Ada: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk Optus - Faults mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from ~Ada taken from his Optus - Faults customer service problem that occurred on November 6, 2017.