Royal Mail: waited for person as directed by not pressing b...
A Royal Mail customer review by GetHuman user GetHuman-334046 from November 19th, 2017
Background on GetHuman-334046's case
GetHuman: GetHuman-334046 - can you tell our other Royal Mail customers when your case took place?
GetHuman-334046: Sure. It was middle of the night, on November 9th.
GetHuman: Did you reach out to Royal Mail, and if so, how?
GetHuman: And which of these common Royal Mail customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-334046 a list of common Royal Mail problems)
GetHuman-334046: "Complaint" was why I was trying to call.
GetHuman-334046's review of Royal Mail customer service
GetHuman: So how would you sum up your experience for GetHuman's Royal Mail 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-334046: waited for person as directed by not pressing buttons but passed buck to local sorting office - the number which never answers and which I can not call from work (in my break) because **** - not good PO
GetHuman: Let's quantify your experience contacting Royal Mail. On a scale of 1 to 5, how easy is it go get help on a Royal Mail problem?
GetHuman-334046: 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-334046: I'd give them a three out of five on communication.
GetHuman: And what about Royal Mail's ability to quickly and effectively address your problem?
GetHuman-334046: For that I would say five out of five.
GetHuman: And finally- any advice for other Royal Mail customers?
GetHuman-334046: Call them early in the day or late. Don't forget any personal or account information you might need for Royal Mail to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-334046 taken from his Royal Mail customer service problem that occurred on November 9th, 2017.