Starbucks: My visit was great. The cashier, NIVEDITA, was...
A Starbucks customer review by GetHuman user GetHuman-183443 from October 31st, 2017
Background on GetHuman-183443's case
GetHuman: GetHuman-183443 - can you tell our other Starbucks customers when your case took place?
GetHuman-183443: Yup. It was afternoon, on October 24th.
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 GetHuman-183443 a list of common Starbucks problems)
GetHuman-183443: "Update Account Info" was why I was trying to call.
GetHuman-183443'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.
GetHuman-183443: My visit was great. The cashier, NIVEDITA, was extremely pleasant. She made it a great experience. She is very outgoing. The coffee also was excellent. I really enjoyed sitting on the outside store bench driking that coffee.
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?
GetHuman-183443: 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-183443: 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?
GetHuman-183443: For that I would say three out of five.
GetHuman: And finally- any advice for other Starbucks customers?
GetHuman-183443: 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 GetHuman-183443 taken from his Starbucks customer service problem that occurred on October 24th, 2017.