Starbucks: Your employees no longer clean the bathrooms. W...
A Starbucks customer review by GetHuman user ~toto28 from November 22nd, 2017
Background on ~toto28's case
GetHuman: ~toto28 - can you tell our other Starbucks customers when your case took place?
~toto28: Yeah. It was morning, on November 20th.
GetHuman: Did you reach out to Starbucks, and if so, how?
GetHuman: And which of these common Starbucks customer issues best describes the reason you wanted to talk to them?
(Shows ~toto28 a list of common Starbucks problems)
~toto28: "Delivery problem" was why I was trying to call.
~toto28's review of Starbucks customer service
GetHuman: So how would you sum up your experience for GetHuman's Starbucks 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.
~toto28: Your employees no longer clean the bathrooms. When a complaint is made they lock it up and say that it's out of order. This is happening all over N.Y.C.. also the people working in them, most stores, are "gangsta "! They wear their pants under their rear ends and their visors tilted. I don't know what happened to this place.
GetHuman: Let's quantify your experience contacting Starbucks. On a scale of 1 to 5, how easy is it go get help on a Starbucks problem?
~toto28: 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?
~toto28: I'd give them a two out of five on communication.
GetHuman: And what about Starbucks's ability to quickly and effectively address your problem?
~toto28: For that I would say one out of five.
GetHuman: And finally- any advice for other Starbucks customers?
~toto28: Call them early in the day or late. Don't forget any personal or account information you might need for Starbucks to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~toto28 taken from his Starbucks customer service problem that occurred on November 20th, 2017.