SafeLink: So rude, refused service, asked more questions...
SafeLink Ulasan pelanggan oleh pengguna GetHuman GetHuman-230945 dari November 26, 2017
Background on GetHuman-230945's case
GetHuman: GetHuman-230945 - can you tell our other SafeLink customers when your case took place?
GetHuman-230945: Yes I can. It was evening, on November 22.
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-230945 a list of common SafeLink problems)
GetHuman-230945: "Complaint" was why I was trying to call.
GetHuman-230945'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-230945: So rude, refused service, asked more questions than necessary. Customer service thought she was "investigating" me. Asked me to verify an address and pin number from **** that weren't even mine. Argued with me about my own identity.
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-230945: 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-230945: I'd give them a three out of five on communication.
GetHuman: And what about SafeLink's ability to quickly and effectively address your problem?
GetHuman-230945: For that I would say four out of five.
GetHuman: And finally- any advice for other SafeLink customers?
GetHuman-230945: 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-230945 taken from his SafeLink customer service problem that occurred on November 22, 2017.