Google Pay: Wasn't there to help or communicate for a long...
A Google Pay customer review by GetHuman user GetHuman-245969 from November 21st, 2017
Background on GetHuman-245969's case
GetHuman: GetHuman-245969 - can you tell our other Google Pay customers when your case took place?
GetHuman-245969: Yes. It was morning, on November 16th.
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-245969 a list of common Google Pay problems)
GetHuman-245969: "Trouble Receiving a Payment" was why I was trying to call.
GetHuman-245969'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-245969: Wasn't there to help or communicate for a long long time, and when I got to talked to them, they were rude and not professional at all. I'm not comment about recommendation.
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-245969: 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-245969: I'd give them a two out of five on communication.
GetHuman: And what about Google Pay's ability to quickly and effectively address your problem?
GetHuman-245969: For that I would say one out of five.
GetHuman: And finally- any advice for other Google Pay customers?
GetHuman-245969: 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-245969 taken from his Google Pay customer service problem that occurred on November 16th, 2017.