Orange County Register: My questions were answered stating that deliver...
A Orange County Register customer review by GetHuman user ~gearguy61 from November 24th, 2017
Background on ~gearguy61's case
GetHuman: ~gearguy61 - can you tell our other Orange County Register customers when your case took place?
~gearguy61: Yeah. It was morning, on November 17th.
GetHuman: Did you reach out to Orange County Register, and if so, how?
GetHuman: And which of these common Orange County Register customer issues best describes the reason you wanted to talk to them?
(Shows ~gearguy61 a list of common Orange County Register problems)
~gearguy61: "Local services" was why I was trying to call.
~gearguy61's review of Orange County Register customer service
GetHuman: So how would you sum up your experience for GetHuman's Orange County Register 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.
~gearguy61: My questions were answered stating that delivery service was still a mess and I still can't get my paper
GetHuman: Let's quantify your experience contacting Orange County Register. On a scale of 1 to 5, how easy is it go get help on a Orange County Register problem?
~gearguy61: 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?
~gearguy61: I'd give them a two out of five on communication.
GetHuman: And what about Orange County Register's ability to quickly and effectively address your problem?
~gearguy61: For that I would say five out of five.
GetHuman: And finally- any advice for other Orange County Register customers?
~gearguy61: Call them early in the day or late. Don't forget any personal or account information you might need for Orange County Register to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~gearguy61 taken from his Orange County Register customer service problem that occurred on November 17th, 2017.