Google Pay: call answered on first ring. i am having an iss...
A Google Pay customer review by GetHuman user ~pbk from November 17th, 2017
Background on ~pbk's case
GetHuman: ~pbk - can you tell our other Google Pay customers when your case took place?
~pbk: Yes. It was afternoon, on November 8th.
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 ~pbk a list of common Google Pay problems)
~pbk: "Trouble Receiving a Payment" was why I was trying to call.
~pbk'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.
~pbk: call answered on first ring. i am having an issue with a merchant that has not delivered my order which was paid through google wallet. the representative said she is sending me the form which i must complete and return for further action which they request ** hours to contact the merchant. follow up is required. that was the right response.
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?
~pbk: I'd give them a four 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?
~pbk: I'd give them a three out of five on communication.
GetHuman: And what about Google Pay's ability to quickly and effectively address your problem?
~pbk: For that I would say five out of five.
GetHuman: And finally- any advice for other Google Pay customers?
~pbk: 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 ~pbk taken from his Google Pay customer service problem that occurred on November 8th, 2017.