Shutterfly: Rachel helped me and she could not have been an...
A Shutterfly customer review by GetHuman user GetHuman-385109 from November 11th, 2017
Background on GetHuman-385109's case
GetHuman: GetHuman-385109 - can you tell our other Shutterfly customers when your case took place?
GetHuman-385109: Yes. It was evening, on November 5th.
GetHuman: Did you reach out to Shutterfly, and if so, how?
GetHuman: And which of these common Shutterfly customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-385109 a list of common Shutterfly problems)
GetHuman-385109: "Track an Order" was why I was trying to call.
GetHuman-385109's review of Shutterfly customer service
GetHuman: So how would you sum up your experience for GetHuman's Shutterfly 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-385109: Rachel helped me and she could not have been any more patient with me*she was clear and walked me thru it and really explained the whole problem I could not be more satisfied *it was a pleasure to talk to Rachel
GetHuman: Let's quantify your experience contacting Shutterfly. On a scale of 1 to 5, how easy is it go get help on a Shutterfly problem?
GetHuman-385109: 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-385109: I'd give them a three out of five on communication.
GetHuman: And what about Shutterfly's ability to quickly and effectively address your problem?
GetHuman-385109: For that I would say one out of five.
GetHuman: And finally- any advice for other Shutterfly customers?
GetHuman-385109: Call them early in the day or late. Don't forget any personal or account information you might need for Shutterfly to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-385109 taken from his Shutterfly customer service problem that occurred on November 5th, 2017.