SafeLink: I have been on hold - no one will answer! I tri...
SafeLink Ulasan pelanggan oleh pengguna GetHuman ~annonymous dari November 28, 2017
Background on ~annonymous's case
GetHuman: ~annonymous - can you tell our other SafeLink customers when your case took place?
~annonymous: Yup. It was middle of the night, on November 20.
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 ~annonymous a list of common SafeLink problems)
~annonymous: "Lost or Broken Phone" was why I was trying to call.
~annonymous'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.
~annonymous: I have been on hold - no one will answer! I tried the option for them to call back and I got a guy from India. Yesterday I got a guy from Hundurus. They were of absolutely no help! Safelink has such terrible customer service!!!!! I don't know how they stay in business!
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?
~annonymous: 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?
~annonymous: I'd give them a five out of five on communication.
GetHuman: And what about SafeLink's ability to quickly and effectively address your problem?
~annonymous: For that I would say two out of five.
GetHuman: And finally- any advice for other SafeLink customers?
~annonymous: 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 ~annonymous taken from his SafeLink customer service problem that occurred on November 20, 2017.