Asda: After a very diappointin g experince where teh...
A Asda customer review by GetHuman user ~Cardiff shopper from November 26th, 2017
Background on ~Cardiff shopper's case
GetHuman: ~Cardiff shopper - can you tell our other Asda customers when your case took place?
~Cardiff shopper: Yup. It was middle of the night, on November 20th.
GetHuman: Did you reach out to Asda, and if so, how?
GetHuman: And which of these common Asda customer issues best describes the reason you wanted to talk to them?
(Shows ~Cardiff shopper a list of common Asda problems)
~Cardiff shopper: "Change order" was why I was trying to call.
~Cardiff shopper's review of Asda customer service
GetHuman: So how would you sum up your experience for GetHuman's Asda 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.
~Cardiff shopper: After a very diappointin g experince where teh store refused to honour teh Try M Love me promise I caleed teh **** number. Once I pressed the right option, I was quickly connected to a very sympathetic and professional man who confirmed the store hadn't behaved properly.
GetHuman: Let's quantify your experience contacting Asda. On a scale of 1 to 5, how easy is it go get help on a Asda problem?
~Cardiff shopper: 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?
~Cardiff shopper: I'd give them a five out of five on communication.
GetHuman: And what about Asda's ability to quickly and effectively address your problem?
~Cardiff shopper: For that I would say three out of five.
GetHuman: And finally- any advice for other Asda customers?
~Cardiff shopper: Call them early in the day or late. Don't forget any personal or account information you might need for Asda to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Cardiff shopper taken from his Asda customer service problem that occurred on November 20th, 2017.