Direct Express: After spending over an hour trying to figure ou...
A Direct Express customer review by GetHuman user ~kevinmdavis1956 from November 25th, 2017
Background on ~kevinmdavis1956's case
GetHuman: ~kevinmdavis1956 - can you tell our other Direct Express customers when your case took place?
~kevinmdavis1956: Yes. It was afternoon, on November 23rd.
GetHuman: Did you reach out to Direct Express, and if so, how?
GetHuman: And which of these common Direct Express customer issues best describes the reason you wanted to talk to them?
(Shows ~kevinmdavis1956 a list of common Direct Express problems)
~kevinmdavis1956: "Complaint" was why I was trying to call.
~kevinmdavis1956's review of Direct Express customer service
GetHuman: So how would you sum up your experience for GetHuman's Direct Express 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.
~kevinmdavis1956: After spending over an hour trying to figure out how to get a human, I stumbled across this solution. This is the best way to get to a human quickly.
GetHuman: Let's quantify your experience contacting Direct Express. On a scale of 1 to 5, how easy is it go get help on a Direct Express problem?
~kevinmdavis1956: 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?
~kevinmdavis1956: I'd give them a four out of five on communication.
GetHuman: And what about Direct Express's ability to quickly and effectively address your problem?
~kevinmdavis1956: For that I would say three out of five.
GetHuman: And finally- any advice for other Direct Express customers?
~kevinmdavis1956: Call them early in the day or late. Don't forget any personal or account information you might need for Direct Express to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~kevinmdavis1956 taken from his Direct Express customer service problem that occurred on November 23rd, 2017.