Oregon Scientific: Call center not in the states. Unable to unders...
A Oregon Scientific customer review by GetHuman user GetHuman-202833 from November 10th, 2017
Background on GetHuman-202833's case
GetHuman: GetHuman-202833 - can you tell our other Oregon Scientific customers when your case took place?
GetHuman-202833: Yup. It was afternoon, on November 6th.
GetHuman: Did you reach out to Oregon Scientific, and if so, how?
GetHuman: And which of these common Oregon Scientific customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-202833 a list of common Oregon Scientific problems)
GetHuman-202833: "Returns" was why I was trying to contact.
GetHuman-202833's review of Oregon Scientific customer service
GetHuman: So how would you sum up your experience for GetHuman's Oregon Scientific 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-202833: Call center not in the states. Unable to understand. Kept repeating and repeating and repeating. NOT acceptable.*.
GetHuman: Let's quantify your experience contacting Oregon Scientific. On a scale of 1 to 5, how easy is it go get help on a Oregon Scientific problem?
GetHuman-202833: 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?
GetHuman-202833: I'd give them a five out of five on communication.
GetHuman: And what about Oregon Scientific's ability to quickly and effectively address your problem?
GetHuman-202833: For that I would say three out of five.
GetHuman: And finally- any advice for other Oregon Scientific customers?
GetHuman-202833: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Oregon Scientific to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-202833 taken from his Oregon Scientific customer service problem that occurred on November 6th, 2017.