Telecheck: How do you answer the phone saying hello. She d...
A Telecheck customer review by GetHuman user ~anonymous from November 21st, 2017
Background on ~anonymous's case
GetHuman: ~anonymous - can you tell our other Telecheck customers when your case took place?
~anonymous: Yes. It was middle of the night, on November 13th.
GetHuman: Did you reach out to Telecheck, and if so, how?
GetHuman: And which of these common Telecheck customer issues best describes the reason you wanted to talk to them?
(Shows ~anonymous a list of common Telecheck problems)
~anonymous: "Dispute a Charge" was why I was trying to call.
~anonymous's review of Telecheck customer service
GetHuman: So how would you sum up your experience for GetHuman's Telecheck 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.
~anonymous: How do you answer the phone saying hello. She didn't say this is Telecheck or anything she just said hello. I said is this telecheck and she said yes can I help you. I said so you always answer the phone like your at home and then she got really smart. so I got back smart with her,
GetHuman: Let's quantify your experience contacting Telecheck. On a scale of 1 to 5, how easy is it go get help on a Telecheck problem?
~anonymous: 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?
~anonymous: I'd give them a three out of five on communication.
GetHuman: And what about Telecheck's ability to quickly and effectively address your problem?
~anonymous: For that I would say two out of five.
GetHuman: And finally- any advice for other Telecheck customers?
~anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Telecheck to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~anonymous taken from his Telecheck customer service problem that occurred on November 13th, 2017.