Fitbit: I spoke with Carlos and he was amazing he helpe...
A Fitbit customer review by GetHuman user GetHuman-48354 from November 27th, 2017
Background on GetHuman-48354's case
GetHuman: GetHuman-48354 - can you tell our other Fitbit customers when your case took place?
GetHuman-48354: Yes. It was afternoon, on November 22nd.
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-48354 a list of common Fitbit problems)
GetHuman-48354: "Problem With the App" was why I was trying to call.
GetHuman-48354'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-48354: I spoke with Carlos and he was amazing he helped me so fast and effectivly that while calling on my ** minute break from work i was able to place the call and end the call all solving the issue before it was time to be back at my desk Carlos is amazing and needs a raise!!!
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-48354: I'd give them a three 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-48354: 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-48354: For that I would say three out of five.
GetHuman: And finally- any advice for other Fitbit customers?
GetHuman-48354: 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-48354 taken from his Fitbit customer service problem that occurred on November 22nd, 2017.