US Postal Service: Attempted to chat *-**-**** @ **:** AM and rece...
A US Postal Service customer review by GetHuman user ~Ron Hamilton from November 27th, 2017
Background on ~Ron Hamilton's case
GetHuman: ~Ron Hamilton - can you tell our other US Postal Service customers when your case took place?
~Ron Hamilton: Yes. It was evening, on November 22nd.
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 ~Ron Hamilton a list of common US Postal Service problems)
~Ron Hamilton: "Track a Package" was why I was trying to call.
~Ron Hamilton'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.
~Ron Hamilton: Attempted to chat *-**-**** @ **:** AM and received the following:*No agents are available now to chat. Please try again later. Thank you.
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?
~Ron Hamilton: I'd give them a one 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?
~Ron Hamilton: I'd give them a four out of five on communication.
GetHuman: And what about US Postal Service's ability to quickly and effectively address your problem?
~Ron Hamilton: For that I would say three out of five.
GetHuman: And finally- any advice for other US Postal Service customers?
~Ron Hamilton: 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 ~Ron Hamilton taken from his US Postal Service customer service problem that occurred on November 22nd, 2017.