When returning calls to Curascript, there shoul...
A CuraScript customer review by GetHuman user GetHuman-176393 from November 12th, 2017
Background on GetHuman-176393's case
GetHuman: GetHuman-176393 - can you tell our other CuraScript customers when your case took place?
GetHuman-176393: Yup. It was evening, on November 7th.
GetHuman: Did you reach out to CuraScript, and if so, how?
GetHuman: And which of these common CuraScript customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-176393 a list of common CuraScript problems)
GetHuman-176393: "Complaint" was why I was trying to call.
GetHuman-176393's review of CuraScript customer service
GetHuman: So how would you sum up your experience for GetHuman's CuraScript 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-176393: When returning calls to Curascript, there should be a way to get directly to a customer service rep. Repeating my identifying information more than once and to several individuals (for my security) is frustrating, esp. when at work.
GetHuman: Let's quantify your experience contacting CuraScript. On a scale of 1 to 5, how easy is it go get help on a CuraScript problem?
GetHuman-176393: I'd give them a one 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-176393: I'd give them a two out of five on communication.
GetHuman: And what about CuraScript's ability to quickly and effectively address your problem?
GetHuman-176393: For that I would say three out of five.
GetHuman: And finally- any advice for other CuraScript customers?
GetHuman-176393: Call them early in the day or late. Don't forget any personal or account information you might need for CuraScript to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-176393 taken from his CuraScript customer service problem that occurred on November 7th, 2017.