Xerox: i called for service but was told that there wa...
Una Xerox reseña del cliente por el usuario de GetHuman ~elisea de noviembre 6º, 2017
Background on ~elisea's case
GetHuman: ~elisea - can you tell our other Xerox customers when your case took place?
~elisea: Sure. It was middle of the night, on octubre 29º.
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 ~elisea a list of common Xerox problems)
~elisea: "Complaint" was why I was trying to call.
~elisea'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.
~elisea: i called for service but was told that there was a hold on our account and that i needed to call a number to speak to a rep who can let us know why there is a hold on the account. i called that number, it went to v*m so i left a detailed message with a callback* * days ago. i never heard back from anyone and we cannot use our machine.
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?
~elisea: 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?
~elisea: 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?
~elisea: For that I would say four out of five.
GetHuman: And finally- any advice for other Xerox customers?
~elisea: Llámalos temprano en el día o tarde. No olvide ninguna información personal o de cuenta que pueda necesitar para Xerox para saber quién es usted.
GetHuman: Well there you have it. Some useful feedback and words from ~elisea taken from his Xerox customer service problem that occurred on octubre 29º, 2017.