OnTrac: He was helpful. Yesterday I had also called for...
A OnTrac customer review by GetHuman user GetHuman-164227 from November 25th, 2017
Background on GetHuman-164227's case
GetHuman: GetHuman-164227 - can you tell our other OnTrac customers when your case took place?
GetHuman-164227: Yeah. It was morning, on November 20th.
GetHuman: Did you reach out to OnTrac, and if so, how?
GetHuman: And which of these common OnTrac customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-164227 a list of common OnTrac problems)
GetHuman-164227: "Track item" was why I was trying to call.
GetHuman-164227's review of OnTrac customer service
GetHuman: So how would you sum up your experience for GetHuman's OnTrac 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-164227: He was helpful. Yesterday I had also called for a package pickup that was wrongfully delivered. I was informed that they would pick it up yesterday, but that did not happen. Today, Edward was really helpful, but that will depend on whether the package is picked up today. We will see.
GetHuman: Let's quantify your experience contacting OnTrac. On a scale of 1 to 5, how easy is it go get help on a OnTrac problem?
GetHuman-164227: 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-164227: I'd give them a three out of five on communication.
GetHuman: And what about OnTrac's ability to quickly and effectively address your problem?
GetHuman-164227: For that I would say one out of five.
GetHuman: And finally- any advice for other OnTrac customers?
GetHuman-164227: Call them early in the day or late. Don't forget any personal or account information you might need for OnTrac to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-164227 taken from his OnTrac customer service problem that occurred on November 20th, 2017.