SafeLink: No one there is competent and they are very arg...
SafeLink Ulasan pelanggan oleh pengguna GetHuman GetHuman-431773 dari November 24, 2017
Background on GetHuman-431773's case
GetHuman: GetHuman-431773 - can you tell our other SafeLink customers when your case took place?
GetHuman-431773: Yup. It was middle of the night, on November 19.
GetHuman: Did you reach out to SafeLink, and if so, how?
GetHuman: And which of these common SafeLink customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-431773 a list of common SafeLink problems)
GetHuman-431773: "Service problem" was why I was trying to call.
GetHuman-431773's review of SafeLink customer service
GetHuman: So how would you sum up your experience for GetHuman's SafeLink 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-431773: No one there is competent and they are very argumentative. I was transferred ** times!!!!!!!!!!! I am still on hold for transfer number ten!!! *A cup and string work better than Safelink phones!!!!!!!!!!!!!!!!!!!!!!!!!!!!
GetHuman: Let's quantify your experience contacting SafeLink. On a scale of 1 to 5, how easy is it go get help on a SafeLink problem?
GetHuman-431773: 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?
GetHuman-431773: I'd give them a one out of five on communication.
GetHuman: And what about SafeLink's ability to quickly and effectively address your problem?
GetHuman-431773: For that I would say four out of five.
GetHuman: And finally- any advice for other SafeLink customers?
GetHuman-431773: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk SafeLink mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-431773 taken from his SafeLink customer service problem that occurred on November 19, 2017.