eSecuritel: this company do fraud work I paid with my debit...
A eSecuritel customer review by GetHuman user ~neveragain from November 18th, 2017
Background on ~neveragain's case
GetHuman: ~neveragain - can you tell our other eSecuritel customers when your case took place?
~neveragain: Yeah. It was afternoon, on November 15th.
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 ~neveragain a list of common eSecuritel problems)
~neveragain: "Cancel service" was why I was trying to call.
~neveragain'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.
~neveragain: this company do fraud work I paid with my debit card for my son and they end up taking money out of my account for my son because they figured we should have known to send the phone back after we have filed a claim ***This company should be shut down by the BBB
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?
~neveragain: I'd give them a two 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?
~neveragain: I'd give them a one out of five on communication.
GetHuman: And what about eSecuritel's ability to quickly and effectively address your problem?
~neveragain: For that I would say two out of five.
GetHuman: And finally- any advice for other eSecuritel customers?
~neveragain: 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 ~neveragain taken from his eSecuritel customer service problem that occurred on November 15th, 2017.