I just wanted to know why My fitbit does not wo...
Una recensione del cliente Fitbit da parte dell'utente GetHuman ~firstname.lastname@example.org da novembre 27º, 2017
Background on ~email@example.com's case
GetHuman: ~firstname.lastname@example.org - can you tell our other Fitbit customers when your case took place?
~email@example.com: Yeah. It was afternoon, on novembre 20º.
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 ~firstname.lastname@example.org a list of common Fitbit problems)
~email@example.com: "Technical support" was why I was trying to call.
~firstname.lastname@example.org'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.
~email@example.com: I just wanted to know why My fitbit does not work on an elevated treadmill. Mo email,no info. SOOOOOO SORRY.
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?
~firstname.lastname@example.org: 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?
~email@example.com: 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?
~firstname.lastname@example.org: For that I would say two out of five.
GetHuman: And finally- any advice for other Fitbit customers?
~email@example.com: 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 ~firstname.lastname@example.org taken from his Fitbit customer service problem that occurred on novembre 20º, 2017.