ProFlowers: Suluma was excellent I was angry because for th...
A ProFlowers customer review by GetHuman user GetHuman-257889 from November 16th, 2017
Background on GetHuman-257889's case
GetHuman: GetHuman-257889 - can you tell our other ProFlowers customers when your case took place?
GetHuman-257889: Yes. It was evening, on November 6th.
GetHuman: Did you reach out to ProFlowers, and if so, how?
GetHuman: And which of these common ProFlowers customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-257889 a list of common ProFlowers problems)
GetHuman-257889: "Returns" was why I was trying to call.
GetHuman-257889's review of ProFlowers customer service
GetHuman: So how would you sum up your experience for GetHuman's ProFlowers 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-257889: Suluma was excellent I was angry because for the second time flowers were not delivered to Bay Shore NY. Everyone else on my list got their flowers. I have used ProFlowers for years but I will not be using them again.
GetHuman: Let's quantify your experience contacting ProFlowers. On a scale of 1 to 5, how easy is it go get help on a ProFlowers problem?
GetHuman-257889: 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?
GetHuman-257889: I'd give them a five out of five on communication.
GetHuman: And what about ProFlowers's ability to quickly and effectively address your problem?
GetHuman-257889: For that I would say five out of five.
GetHuman: And finally- any advice for other ProFlowers customers?
GetHuman-257889: Call them early in the day or late. Don't forget any personal or account information you might need for ProFlowers to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-257889 taken from his ProFlowers customer service problem that occurred on November 6th, 2017.