JC Penney Catalog: Ugoeze was excellent in helping me to place *my...
A JC Penney Catalog customer review by GetHuman user ~margaret from November 13th, 2017
Background on ~margaret's case
GetHuman: ~margaret - can you tell our other JC Penney Catalog customers when your case took place?
~margaret: Yeah. It was middle of the night, on November 12th.
GetHuman: Did you reach out to JC Penney Catalog, and if so, how?
GetHuman: And which of these common JC Penney Catalog customer issues best describes the reason you wanted to talk to them?
(Shows ~margaret a list of common JC Penney Catalog problems)
~margaret: "Track order" was why I was trying to call.
~margaret's review of JC Penney Catalog customer service
GetHuman: So how would you sum up your experience for GetHuman's JC Penney Catalog 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.
~margaret: Ugoeze was excellent in helping me to place *my order.this order was very important to me.she took her time with me.i didn't feel*like being rush.EXCELLENT!!!!!!!*THANK YOU,UGOEZE
GetHuman: Let's quantify your experience contacting JC Penney Catalog. On a scale of 1 to 5, how easy is it go get help on a JC Penney Catalog problem?
~margaret: I'd give them a three 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?
~margaret: I'd give them a two out of five on communication.
GetHuman: And what about JC Penney Catalog's ability to quickly and effectively address your problem?
~margaret: For that I would say five out of five.
GetHuman: And finally- any advice for other JC Penney Catalog customers?
~margaret: Call them early in the day or late. Don't forget any personal or account information you might need for JC Penney Catalog to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~margaret taken from his JC Penney Catalog customer service problem that occurred on November 12th, 2017.