US Postal Service: Call the **** number, and repeatedly say custom...
A US Postal Service customer review by GetHuman user ~dbbd1388 from November 28th, 2017
Background on ~dbbd1388's case
GetHuman: ~dbbd1388 - can you tell our other US Postal Service customers when your case took place?
~dbbd1388: Yeah. It was morning, on November 19th.
GetHuman: Did you reach out to US Postal Service, and if so, how?
GetHuman: And which of these common US Postal Service customer issues best describes the reason you wanted to talk to them?
(Shows ~dbbd1388 a list of common US Postal Service problems)
~dbbd1388: "Local services" was why I was trying to call.
~dbbd1388's review of US Postal Service customer service
GetHuman: So how would you sum up your experience for GetHuman's US Postal Service 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.
~dbbd1388: Call the **** number, and repeatedly say customer service from the main menu. After about **-** times the system will finally transfer you. It's annoying but you eventually get to talk to a person.
GetHuman: Let's quantify your experience contacting US Postal Service. On a scale of 1 to 5, how easy is it go get help on a US Postal Service problem?
~dbbd1388: 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?
~dbbd1388: I'd give them a three out of five on communication.
GetHuman: And what about US Postal Service's ability to quickly and effectively address your problem?
~dbbd1388: For that I would say two out of five.
GetHuman: And finally- any advice for other US Postal Service customers?
~dbbd1388: Call them early in the day or late. Don't forget any personal or account information you might need for US Postal Service to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~dbbd1388 taken from his US Postal Service customer service problem that occurred on November 19th, 2017.