ROBLOX: We have payed for robux and still it has been a...
A ROBLOX customer review by GetHuman user GetHuman-razcool from December 8th, 2017
Background on GetHuman-razcool's case
GetHuman: GetHuman-razcool - can you tell our other ROBLOX customers when your case took place?
GetHuman-razcool: Yes I can. It was morning, on December 6th.
GetHuman: Did you reach out to ROBLOX, and if so, how?
GetHuman: And which of these common ROBLOX customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-razcool a list of common ROBLOX problems)
GetHuman-razcool: "Update account information" was why I was trying to call.
GetHuman-razcool's review of ROBLOX customer service
GetHuman: So how would you sum up your experience for GetHuman's ROBLOX 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-razcool: We have payed for robux and still it has been a day and still non have showen.
GetHuman: Can you tell the rest of us a bit more from what happened on 12/06/17?
GetHuman-razcool: We have payed $*.** for *** robux and tall none have showen
GetHuman: Let's quantify your experience contacting ROBLOX. On a scale of 1 to 5, how easy is it go get help on a ROBLOX problem?
GetHuman-razcool: 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?
GetHuman-razcool: I'd give them a five out of five on communication.
GetHuman: And what about ROBLOX's ability to quickly and effectively address your problem?
GetHuman-razcool: For that I would say four out of five.
GetHuman: And finally- any advice for other ROBLOX customers?
GetHuman-razcool: Call them early in the day or late. Don't forget any personal or account information you might need for ROBLOX to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-razcool taken from his ROBLOX customer service problem that occurred on December 6th, 2017.