Fitbit: I had a general question regarding some warrant...
A Fitbit customer review by GetHuman user GetHuman-48452 from November 27th, 2017
Background on GetHuman-48452's case
GetHuman: GetHuman-48452 - can you tell our other Fitbit customers when your case took place?
GetHuman-48452: Yeah. It was afternoon, on November 18th.
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-48452 a list of common Fitbit problems)
GetHuman-48452: "Warranty Claim" was why I was trying to call.
GetHuman-48452'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-48452: I had a general question regarding some warranty work, but the customer service rep would not help me without my giving the email address associated with the device. Since this is my husband's fitbit I wasn't sure which email he'd used, so she did not offer to help.
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-48452: I'd give them a five 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-48452: I'd give them a two out of five on communication.
GetHuman: And what about Fitbit's ability to quickly and effectively address your problem?
GetHuman-48452: For that I would say three out of five.
GetHuman: And finally- any advice for other Fitbit customers?
GetHuman-48452: Call them early in the day or late. Don't forget any personal or account information you might need for Fitbit to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-48452 taken from his Fitbit customer service problem that occurred on November 18th, 2017.