Google Pay: CSR needs additional training to clarify Google...
A Google Pay customer review by GetHuman user GetHuman-378613 from November 28th, 2017
Background on GetHuman-378613's case
GetHuman: GetHuman-378613 - can you tell our other Google Pay customers when your case took place?
GetHuman-378613: Yup. It was afternoon, on November 26th.
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 GetHuman-378613 a list of common Google Pay problems)
GetHuman-378613: "Refund a Charge" was why I was trying to call.
GetHuman-378613'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.
GetHuman-378613: CSR needs additional training to clarify Google Wallet processes and procedures for money transfers , refunds and transfer expiration. He was kind but could only offer some of the information I was asking for.
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?
GetHuman-378613: I'd give them a five 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?
GetHuman-378613: 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?
GetHuman-378613: For that I would say three out of five.
GetHuman: And finally- any advice for other Google Pay customers?
GetHuman-378613: 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 GetHuman-378613 taken from his Google Pay customer service problem that occurred on November 26th, 2017.