Chex Systems: I called this number for the same reason as Bry...
A Chex Systems customer review by GetHuman user ~ANGIE from November 25th, 2017
Background on ~ANGIE's case
GetHuman: ~ANGIE - can you tell our other Chex Systems customers when your case took place?
~ANGIE: Yes I can. It was evening, on November 23rd.
GetHuman: Did you reach out to Chex Systems, and if so, how?
GetHuman: And which of these common Chex Systems customer issues best describes the reason you wanted to talk to them?
(Shows ~ANGIE a list of common Chex Systems problems)
~ANGIE: "None of those really matches why I wanted to call Chex Systems that day." was why I was trying to call.
~ANGIE's review of Chex Systems customer service
GetHuman: So how would you sum up your experience for GetHuman's Chex Systems 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.
~ANGIE: I called this number for the same reason as Bryan-to get someone in sales! They gave me another number- ***-***-**** for member solutions. This is a service of FIS. They are to call me back or send an email with sales information. LET'S SEE!!
GetHuman: Let's quantify your experience contacting Chex Systems. On a scale of 1 to 5, how easy is it go get help on a Chex Systems problem?
~ANGIE: 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?
~ANGIE: I'd give them a three out of five on communication.
GetHuman: And what about Chex Systems's ability to quickly and effectively address your problem?
~ANGIE: For that I would say five out of five.
GetHuman: And finally- any advice for other Chex Systems customers?
~ANGIE: Call them early in the day or late. Don't forget any personal or account information you might need for Chex Systems to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~ANGIE taken from his Chex Systems customer service problem that occurred on November 23rd, 2017.