SafeLink: Ive been calling every number safe link has and...
Una recensione del cliente SafeLink da parte dell'utente GetHuman ~nyla da novembre 24º, 2017
Background on ~nyla's case
GetHuman: ~nyla - can you tell our other SafeLink customers when your case took place?
~nyla: Sure. It was evening, on novembre 21º.
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 ~nyla a list of common SafeLink problems)
~nyla: "Setup service" was why I was trying to call.
~nyla'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.
~nyla: Ive been calling every number safe link has and yes of course tech support. finally went on line to here and waited got a human that i could not understand well in the end he reffered me back to the same number i had called several times among others and pressed numbers after i lost patience randomly , nothing worked. im still hanging!!
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?
~nyla: I'd give them a one 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?
~nyla: 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?
~nyla: For that I would say three out of five.
GetHuman: And finally- any advice for other SafeLink customers?
~nyla: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per SafeLink sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from ~nyla taken from his SafeLink customer service problem that occurred on novembre 21º, 2017.