eSecuritel: I don't feel I received a solution to my proble...
A eSecuritel customer review by GetHuman user GetHuman-438753 from November 25th, 2017
Background on GetHuman-438753's case
GetHuman: GetHuman-438753 - can you tell our other eSecuritel customers when your case took place?
GetHuman-438753: Yup. It was morning, on November 19th.
GetHuman: Did you reach out to eSecuritel, and if so, how?
GetHuman: And which of these common eSecuritel customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-438753 a list of common eSecuritel problems)
GetHuman-438753: "Setup service" was why I was trying to call.
GetHuman-438753's review of eSecuritel customer service
GetHuman: So how would you sum up your experience for GetHuman's eSecuritel 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-438753: I don't feel I received a solution to my problem I should have ***.** on card and there is no way to check. I didn't want to look like a fool using it, I guess there is no way to check*that's great on your part
GetHuman: Let's quantify your experience contacting eSecuritel. On a scale of 1 to 5, how easy is it go get help on a eSecuritel problem?
GetHuman-438753: I'd give them a three 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-438753: I'd give them a four out of five on communication.
GetHuman: And what about eSecuritel's ability to quickly and effectively address your problem?
GetHuman-438753: For that I would say one out of five.
GetHuman: And finally- any advice for other eSecuritel customers?
GetHuman-438753: Call them early in the day or late. Don't forget any personal or account information you might need for eSecuritel to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-438753 taken from his eSecuritel customer service problem that occurred on November 19th, 2017.