BillMeLater.com: Customer service representative sounded as if h...
A BillMeLater.com customer review by GetHuman user ~580 from November 19th, 2017
Background on ~580's case
GetHuman: ~580 - can you tell our other BillMeLater.com customers when your case took place?
~580: Yes. It was middle of the night, on November 16th.
GetHuman: Did you reach out to BillMeLater.com, and if so, how?
GetHuman: And which of these common BillMeLater.com customer issues best describes the reason you wanted to talk to them?
(Shows ~580 a list of common BillMeLater.com problems)
~580: "None of those really matches why I wanted to call BillMeLater.com that day." was why I was trying to call.
~580's review of BillMeLater.com customer service
GetHuman: So how would you sum up your experience for GetHuman's BillMeLater.com 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.
~580: Customer service representative sounded as if he was just reading a script and it was not very personable. No inflection, no sincerity. ("I am so sorry. I will be happy to help you, blah, blah, blah.")
GetHuman: Let's quantify your experience contacting BillMeLater.com. On a scale of 1 to 5, how easy is it go get help on a BillMeLater.com problem?
~580: 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?
~580: I'd give them a one out of five on communication.
GetHuman: And what about BillMeLater.com's ability to quickly and effectively address your problem?
~580: For that I would say four out of five.
GetHuman: And finally- any advice for other BillMeLater.com customers?
~580: Call them early in the day or late. Don't forget any personal or account information you might need for BillMeLater.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~580 taken from his BillMeLater.com customer service problem that occurred on November 16th, 2017.