Optus - Faults: they refuse to let you contact a person outside...
A Optus - Faults customer review by GetHuman user GetHuman-18001 from November 24th, 2017
Background on GetHuman-18001's case
GetHuman: GetHuman-18001 - can you tell our other Optus - Faults customers when your case took place?
GetHuman-18001: Sure. It was late at night, on November 17th.
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 GetHuman-18001 a list of common Optus - Faults problems)
GetHuman-18001: "Cancel service" was why I was trying to call.
GetHuman-18001'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.
GetHuman-18001: they refuse to let you contact a person outside of *-* Monday to Friday business hours. after wrongfully disconnecting my phone they also refuse to reconnect it
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?
GetHuman-18001: I'd give them a two 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?
GetHuman-18001: 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?
GetHuman-18001: For that I would say four out of five.
GetHuman: And finally- any advice for other Optus - Faults customers?
GetHuman-18001: Call them early in the day or late. Don't forget any personal or account information you might need for Optus - Faults to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-18001 taken from his Optus - Faults customer service problem that occurred on November 17th, 2017.