StarHub: I 've called and waited for nearly ** to ** min...
A StarHub customer review by GetHuman user GetHuman-414223 from November 7th, 2017
Background on GetHuman-414223's case
GetHuman: GetHuman-414223 - can you tell our other StarHub customers when your case took place?
GetHuman-414223: Yup. It was middle of the night, on November 1st.
GetHuman: Did you reach out to StarHub, and if so, how?
GetHuman: And which of these common StarHub customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-414223 a list of common StarHub problems)
GetHuman-414223: "Update account information" was why I was trying to call.
GetHuman-414223's review of StarHub customer service
GetHuman: So how would you sum up your experience for GetHuman's StarHub 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-414223: I 've called and waited for nearly ** to ** mins but was not connected to a customer consultant. Next to get them to call back and leave my number but waited for whole day, noone calls back. What type of service is this?????
GetHuman: Let's quantify your experience contacting StarHub. On a scale of 1 to 5, how easy is it go get help on a StarHub problem?
GetHuman-414223: I'd give them a three 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-414223: I'd give them a two out of five on communication.
GetHuman: And what about StarHub's ability to quickly and effectively address your problem?
GetHuman-414223: For that I would say one out of five.
GetHuman: And finally- any advice for other StarHub customers?
GetHuman-414223: Call them early in the day or late. Don't forget any personal or account information you might need for StarHub to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-414223 taken from his StarHub customer service problem that occurred on November 1st, 2017.