LA Times: This was the only phone number that I could fin...
A LA Times customer review by GetHuman user GetHuman-133482 from November 25th, 2017
Background on GetHuman-133482's case
GetHuman: GetHuman-133482 - can you tell our other LA Times customers when your case took place?
GetHuman-133482: Yeah. It was evening, on November 23rd.
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 GetHuman-133482 a list of common LA Times problems)
GetHuman-133482: "Cancel subscription" was why I was trying to call.
GetHuman-133482'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.
GetHuman-133482: This was the only phone number that I could find. When I called *** they couldn't understand my words. No accent, just plain English. With my husband making noise behind me they were lost at ***. Your number worked for me and I thank you!
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?
GetHuman-133482: I'd give them a four 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?
GetHuman-133482: I'd give them a three out of five on communication.
GetHuman: And what about LA Times's ability to quickly and effectively address your problem?
GetHuman-133482: For that I would say four out of five.
GetHuman: And finally- any advice for other LA Times customers?
GetHuman-133482: 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 GetHuman-133482 taken from his LA Times customer service problem that occurred on November 23rd, 2017.