Franklinmint.com: I got a human who gave me an e-mail address. S...
A Franklinmint.com customer review by GetHuman user GetHuman-400835 from November 24th, 2017
Background on GetHuman-400835's case
GetHuman: GetHuman-400835 - can you tell our other Franklinmint.com customers when your case took place?
GetHuman-400835: Yes I can. It was morning, on November 21st.
GetHuman: Did you reach out to Franklinmint.com, and if so, how?
GetHuman: And which of these common Franklinmint.com customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-400835 a list of common Franklinmint.com problems)
GetHuman-400835: "Complaint" was why I was trying to contact.
GetHuman-400835's review of Franklinmint.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Franklinmint.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-400835: I got a human who gave me an e-mail address. So much for "human" contact that is advertised with this number
GetHuman: Let's quantify your experience contacting Franklinmint.com. On a scale of 1 to 5, how easy is it go get help on a Franklinmint.com problem?
GetHuman-400835: 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-400835: I'd give them a four out of five on communication.
GetHuman: And what about Franklinmint.com's ability to quickly and effectively address your problem?
GetHuman-400835: For that I would say five out of five.
GetHuman: And finally- any advice for other Franklinmint.com customers?
GetHuman-400835: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Franklinmint.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-400835 taken from his Franklinmint.com customer service problem that occurred on November 21st, 2017.