Taco Bell: One of the emoyees sang crude songs about my fa...
A Taco Bell customer review by GetHuman user GetHuman-172051 from November 14th, 2017
Background on GetHuman-172051's case
GetHuman: GetHuman-172051 - can you tell our other Taco Bell customers when your case took place?
GetHuman-172051: Sure. It was morning, on November 11th.
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 GetHuman-172051 a list of common Taco Bell problems)
GetHuman-172051: "Refund" was why I was trying to call.
GetHuman-172051'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.
GetHuman-172051: One of the emoyees sang crude songs about my family as he made our ** pack of tacos. If i remember correctly the song went like "ohh why cant the customers wreck and die before theyre in the drive thruu" it had no rythm once so ever.
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?
GetHuman-172051: I'd give them a four 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-172051: 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?
GetHuman-172051: For that I would say two out of five.
GetHuman: And finally- any advice for other Taco Bell customers?
GetHuman-172051: 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 GetHuman-172051 taken from his Taco Bell customer service problem that occurred on November 11th, 2017.