Taco Bell: Never answered. Called * different times. Wai...
A Taco Bell customer review by GetHuman user ~Never again from November 28th, 2017
Background on ~Never again's case
GetHuman: ~Never again - can you tell our other Taco Bell customers when your case took place?
~Never again: Yup. It was afternoon, on November 24th.
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 ~Never again a list of common Taco Bell problems)
~Never again: "Store Feedback" was why I was trying to call.
~Never again'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.
~Never again: Never answered. Called * different times. Waited ** minutes, called back waited ** minutes, called back again, still waiting ** minutes. I guess this tell me all I need to know. Taco Bell does not care and should close their doors. I will never eat at Taco Bell again!
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?
~Never again: 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?
~Never again: 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?
~Never again: For that I would say four out of five.
GetHuman: And finally- any advice for other Taco Bell customers?
~Never again: 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 ~Never again taken from his Taco Bell customer service problem that occurred on November 24th, 2017.