SafeLink: he intentado cominicarme con ustedes por aqui y...
SafeLink Ulasan pelanggan oleh pengguna GetHuman GetHuman-407822 dari November 27, 2017
Background on GetHuman-407822's case
GetHuman: GetHuman-407822 - can you tell our other SafeLink customers when your case took place?
GetHuman-407822: Yeah. It was evening, on November 24.
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-407822 a list of common SafeLink problems)
GetHuman-407822: "Lost or Broken Phone" was why I was trying to call.
GetHuman-407822'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-407822: he intentado cominicarme con ustedes por aqui y por telefono y nada. Mi telefono se da****o me lo iban a cambiar y no ha llegado he intentado comunicarme y nada tendre que llamar a los comunicacion federal para poder hacer algo
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-407822: 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-407822: I'd give them a four out of five on communication.
GetHuman: And what about SafeLink's ability to quickly and effectively address your problem?
GetHuman-407822: For that I would say five out of five.
GetHuman: And finally- any advice for other SafeLink customers?
GetHuman-407822: 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-407822 taken from his SafeLink customer service problem that occurred on November 24, 2017.