FragranceNet.com: No way to communicate with them, they don't ans...
A FragranceNet.com customer review by GetHuman user GetHuman-104744 from November 25th, 2017
Background on GetHuman-104744's case
GetHuman: GetHuman-104744 - can you tell our other FragranceNet.com customers when your case took place?
GetHuman-104744: Yes. It was afternoon, on November 16th.
GetHuman: Did you reach out to FragranceNet.com, and if so, how?
GetHuman: And which of these common FragranceNet.com customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-104744 a list of common FragranceNet.com problems)
GetHuman-104744: "Warranty claim" was why I was trying to call.
GetHuman-104744's review of FragranceNet.com customer service
GetHuman: So how would you sum up your experience for GetHuman's FragranceNet.com 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-104744: No way to communicate with them, they don't answer. The funny thing is that I used that site because American Express promoted it.
GetHuman: Let's quantify your experience contacting FragranceNet.com. On a scale of 1 to 5, how easy is it go get help on a FragranceNet.com problem?
GetHuman-104744: I'd give them a two 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-104744: I'd give them a one out of five on communication.
GetHuman: And what about FragranceNet.com's ability to quickly and effectively address your problem?
GetHuman-104744: For that I would say four out of five.
GetHuman: And finally- any advice for other FragranceNet.com customers?
GetHuman-104744: Call them early in the day or late. Don't forget any personal or account information you might need for FragranceNet.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-104744 taken from his FragranceNet.com customer service problem that occurred on November 16th, 2017.