annabell sam is one of worst managers Taco Bell...
A Taco Bell customer review by GetHuman user ~Teagirl74 from November 28th, 2017
Background on ~Teagirl74's case
GetHuman: ~Teagirl74 - can you tell our other Taco Bell customers when your case took place?
~Teagirl74: Yeah. It was middle of the night, on November 25th.
GetHuman: Did you reach out to Taco Bell, and if so, how?
GetHuman: And which of these common Taco Bell customer issues best describes the reason you wanted to talk to them?
(Shows ~Teagirl74 a list of common Taco Bell problems)
~Teagirl74: "Refund" was why I was trying to call.
~Teagirl74's review of Taco Bell customer service
GetHuman: So how would you sum up your experience for GetHuman's Taco Bell 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.
~Teagirl74: annabell sam is one of worst managers Taco Bell can have working for them she berates the employees just because there Christian faith and hollers at employees in front of customers she is not a good manager and I will not eat at this store until she is no longer a manager the store * is ******
GetHuman: Let's quantify your experience contacting Taco Bell. On a scale of 1 to 5, how easy is it go get help on a Taco Bell problem?
~Teagirl74: 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?
~Teagirl74: I'd give them a one out of five on communication.
GetHuman: And what about Taco Bell's ability to quickly and effectively address your problem?
~Teagirl74: For that I would say one out of five.
GetHuman: And finally- any advice for other Taco Bell customers?
~Teagirl74: Call them early in the day or late. Don't forget any personal or account information you might need for Taco Bell to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Teagirl74 taken from his Taco Bell customer service problem that occurred on November 25th, 2017.