My FitBit quit working and all I had to do was...
Una recensione del cliente Fitbit da parte dell'utente GetHuman GetHuman-23993 da novembre 27º, 2017
Background on GetHuman-23993's case
GetHuman: GetHuman-23993 - can you tell our other Fitbit customers when your case took place?
GetHuman-23993: Yup. It was afternoon, on novembre 25º.
GetHuman: Did you reach out to Fitbit, and if so, how?
GetHuman: And which of these common Fitbit customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-23993 a list of common Fitbit problems)
GetHuman-23993: "Warranty claim" was why I was trying to call.
GetHuman-23993's review of Fitbit customer service
GetHuman: So how would you sum up your experience for GetHuman's Fitbit 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-23993: My FitBit quit working and all I had to do was call customer service and they are mailing me a new one. Very pleased with the customer support. The lady was a little hard to understand, but hey, they are backing their product so I can deal with that :)
GetHuman: Let's quantify your experience contacting Fitbit. On a scale of 1 to 5, how easy is it go get help on a Fitbit problem?
GetHuman-23993: 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-23993: I'd give them a five out of five on communication.
GetHuman: And what about Fitbit's ability to quickly and effectively address your problem?
GetHuman-23993: For that I would say five out of five.
GetHuman: And finally- any advice for other Fitbit customers?
GetHuman-23993: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per Fitbit sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-23993 taken from his Fitbit customer service problem that occurred on novembre 25º, 2017.