Abbey (UK): I was stuck on the answer machine * times then...
A Abbey (UK) customer review by GetHuman user GetHuman-328548 from October 28th, 2017
Background on GetHuman-328548's case
GetHuman: GetHuman-328548 - can you tell our other Abbey (UK) customers when your case took place?
GetHuman-328548: Yup. It was middle of the night, on October 25th.
GetHuman: Did you reach out to Abbey (UK), and if so, how?
GetHuman: And which of these common Abbey (UK) customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-328548 a list of common Abbey (UK) problems)
GetHuman-328548: "Question" was why I was trying to call.
GetHuman-328548's review of Abbey (UK) customer service
GetHuman: So how would you sum up your experience for GetHuman's Abbey (UK) 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-328548: I was stuck on the answer machine * times then I tried this and after about * mins, I got through to someone. I couldn't really understand him but at least I didn't get stuck for nothing. Great tip, thanks!
GetHuman: Let's quantify your experience contacting Abbey (UK). On a scale of 1 to 5, how easy is it go get help on a Abbey (UK) problem?
GetHuman-328548: I'd give them a two 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-328548: I'd give them a three out of five on communication.
GetHuman: And what about Abbey (UK)'s ability to quickly and effectively address your problem?
GetHuman-328548: For that I would say five out of five.
GetHuman: And finally- any advice for other Abbey (UK) customers?
GetHuman-328548: Call them early in the day or late. Don't forget any personal or account information you might need for Abbey (UK) to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-328548 taken from his Abbey (UK) customer service problem that occurred on October 25th, 2017.