Google Pay: Person went out of his way to help. However Go...
A Google Pay customer review by GetHuman user ~Jonathan Christopher from November 26th, 2017
Background on ~Jonathan Christopher's case
GetHuman: ~Jonathan Christopher - can you tell our other Google Pay customers when your case took place?
~Jonathan Christopher: Yeah. It was morning, on November 19th.
GetHuman: Did you reach out to Google Pay, and if so, how?
GetHuman: And which of these common Google Pay customer issues best describes the reason you wanted to talk to them?
(Shows ~Jonathan Christopher a list of common Google Pay problems)
~Jonathan Christopher: "Problem With a Payment" was why I was trying to call.
~Jonathan Christopher's review of Google Pay customer service
GetHuman: So how would you sum up your experience for GetHuman's Google Pay 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.
~Jonathan Christopher: Person went out of his way to help. However Google needs to improve their ransaction numbering to match the receiving bank last four digits.
GetHuman: Let's quantify your experience contacting Google Pay. On a scale of 1 to 5, how easy is it go get help on a Google Pay problem?
~Jonathan Christopher: I'd give them a three 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?
~Jonathan Christopher: I'd give them a four out of five on communication.
GetHuman: And what about Google Pay's ability to quickly and effectively address your problem?
~Jonathan Christopher: For that I would say five out of five.
GetHuman: And finally- any advice for other Google Pay customers?
~Jonathan Christopher: Call them early in the day or late. Don't forget any personal or account information you might need for Google Pay to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Jonathan Christopher taken from his Google Pay customer service problem that occurred on November 19th, 2017.