This number was helpful. But for the Xerox org...
A Xerox customer review by GetHuman user GetHuman-335960 from November 19th, 2017
Background on GetHuman-335960's case
GetHuman: GetHuman-335960 - can you tell our other Xerox customers when your case took place?
GetHuman-335960: Yes I can. It was afternoon, on November 11th.
GetHuman: Did you reach out to Xerox, and if so, how?
GetHuman: And which of these common Xerox customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-335960 a list of common Xerox problems)
GetHuman-335960: "Warranty claim" was why I was trying to call.
GetHuman-335960's review of Xerox customer service
GetHuman: So how would you sum up your experience for GetHuman's Xerox 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-335960: This number was helpful. But for the Xerox organization overall, it is very frustrating trying to get someone to help. It's a company fail when the customer feels like they have to chase down the company to buy their product. This number gave me a local number to contact.
GetHuman: Let's quantify your experience contacting Xerox. On a scale of 1 to 5, how easy is it go get help on a Xerox problem?
GetHuman-335960: 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-335960: I'd give them a five out of five on communication.
GetHuman: And what about Xerox's ability to quickly and effectively address your problem?
GetHuman-335960: For that I would say four out of five.
GetHuman: And finally- any advice for other Xerox customers?
GetHuman-335960: Call them early in the day or late. Don't forget any personal or account information you might need for Xerox to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-335960 taken from his Xerox customer service problem that occurred on November 11th, 2017.