LA Times: We did not receive our paper this morning. I c...
A LA Times customer review by GetHuman user ~Gary from November 25th, 2017
Background on ~Gary's case
GetHuman: ~Gary - can you tell our other LA Times customers when your case took place?
~Gary: Yup. It was afternoon, on November 18th.
GetHuman: Did you reach out to LA Times, and if so, how?
GetHuman: And which of these common LA Times customer issues best describes the reason you wanted to talk to them?
(Shows ~Gary a list of common LA Times problems)
~Gary: "Complaint" was why I was trying to call.
~Gary's review of LA Times customer service
GetHuman: So how would you sum up your experience for GetHuman's LA Times 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.
~Gary: We did not receive our paper this morning. I called and used the automated response. Paper should be here in ** minutes. * hours later, no paper. Called, waited ** minutes, cust. serv. will try to get one out but can't promise one. Too late for delivery. Told him I will cancel my subscription if not paper. It's now * hours later. NO paper.*Will call and cancel my sub in the morning.
GetHuman: Let's quantify your experience contacting LA Times. On a scale of 1 to 5, how easy is it go get help on a LA Times problem?
~Gary: I'd give them a five 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?
~Gary: I'd give them a four out of five on communication.
GetHuman: And what about LA Times's ability to quickly and effectively address your problem?
~Gary: For that I would say one out of five.
GetHuman: And finally- any advice for other LA Times customers?
~Gary: Call them early in the day or late. Don't forget any personal or account information you might need for LA Times to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Gary taken from his LA Times customer service problem that occurred on November 18th, 2017.