Fitbit: no wait time they answered, i already had a cas...
A Fitbit customer review by GetHuman user ~lnoga from November 27th, 2017
Background on ~lnoga's case
GetHuman: ~lnoga - can you tell our other Fitbit customers when your case took place?
~lnoga: Sure. It was evening, on November 20th.
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 ~lnoga a list of common Fitbit problems)
~lnoga: "Complaint" was why I was trying to call.
~lnoga'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.
~lnoga: no wait time they answered, i already had a case * from emails that were no progressing. they accessed the case * and then i held for less than * minute for him to talk to sales. my fitbit was not charging, i did all thereir steps thru email ist. they are sending me replacement. use their email process *st to get your case * do the steps, respond by email, if no resonse call this phone number.
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?
~lnoga: 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?
~lnoga: I'd give them a three out of five on communication.
GetHuman: And what about Fitbit's ability to quickly and effectively address your problem?
~lnoga: For that I would say two out of five.
GetHuman: And finally- any advice for other Fitbit customers?
~lnoga: 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 ~lnoga taken from his Fitbit customer service problem that occurred on November 20th, 2017.