After roughly 19 hours of marathon__ methodically attaching the same 21K KYC complaint to every BC Game promotional post in sight, the multi-award-winning platform's Community Ops representative Kelsey has finally surfaced. The response, posted at 4:57 AM UTC on a Saturday, is a masterclass in the art of showing up while simultaneously demonstrating that you have read absolutely nothing.

"heyhey, could you send me back your uid to us via dm first? we'll arrange relevant team to check your case🧐"

That is the message in its entirety. Let us count the things happening here. First, the double "hey." Not one hey, which would be casual. Two heys, fused together without a space, suggesting either the enthusiasm of someone who has just mainlined their third coffee or the nerves of someone who knows they are stepping into a very hot thread. Possibly both. The magnifying-glass emoji at the end does a lot of heavy lifting, gesturing vaguely at investigation without committing to anything that might be mistaken for a timeline.

The real centerpiece, though, is the request itself. Kelsey is asking marathon__ to provide a UID via DM. This is the same marathon__ who has been posting about this issue across multiple threads since Friday, whose account details are presumably embedded in every support ticket, every complaint message, and every reply that the BC.GAME social team has been scrolling past for days. The request for a UID at this stage is not information-gathering. It is the customer service equivalent of asking someone who has been standing in your lobby holding a sign for 19 hours to please write down their name on a piece of paper.

The Kelsey Method

This is, by now, a recognizable pattern. Last week, when fariborz, the Platinum 5 VIP with $15 million in turnover, was permanently banned without explanation, Kelsey surfaced at 3:56 AM with a three-point explanation that boiled down to: we helped you before, the ban was for your own protection, and we cannot discuss the details. That response was delivered with a bandaged-head emoji and the phrase "we are disappointed to see that our previous efforts are not reflected in your description of this case." The corporate hurt feelings approach did not go over well, and fariborz has since escalated to tagging his complaint onto BC.GAME's replies to NFL insider Ari Meirov, where 909,000 followers can see it.

With marathon__, Kelsey appears to have swapped the wounded bullet points for a more streamlined opening: the double hey and the UID redirect. It is faster, friendlier, and just as empty. Both approaches share the same underlying philosophy: acknowledge the complaint exists, ask for something the player has already provided, and hope that the act of responding, regardless of content, de-escalates the thread. It is community management as placebo.

The Thread That Would Not Die

To understand why Kelsey's response reads as theater rather than troubleshooting, it helps to review what marathon__ has actually been saying. The player's complaint, detailed here on Friday, is specific: BC.GAME blocked a withdrawal after a wagering win, deleted the account history, reduced the balance, rejected the KYC documents, and then approved those exact same documents instantly on a new account and processed a $21,000 withdrawal. "I have proof," marathon__ wrote. Twice.

The complaint first appeared as a reply to BC.GAME's sports betting promo post, the glossy kind of content the platform's 394,000 followers are meant to consume between the accumulating complaint replies. Then it appeared again beneath the "Today's top creations" community showcase, where four users had been awarded up to $20 in bonuses for sharing Coco creations and lifestyle shots. The juxtaposition of cheery community content and a reply accusing the platform of a KYC shell game could power a small city.

By the time Kelsey arrived, the thread had already attracted a sympathetic reply from @Yadartseth, who chimed in with "Same bro i was 39 VIP," adding yet another data point to the growing collection of BC.GAME users who recognize their own experience in someone else's complaint. The platform's content calendar, meanwhile, rolled on undisturbed: a Gamrot vs Salkilld fight prediction, a weekly bonus announcement, the usual rhythm of an account that has apparently decided the replies section is a problem for someone else's job description.

Progress, Technically

Is Kelsey's response progress? In the narrowest possible sense, yes. Someone from BC.GAME has acknowledged that marathon__ exists and that a case might, at some future point, be checked by a relevant team. This is more than fariborz got for several days. It is more than many of BC.GAME's complaining users ever receive.

But the substance of the response is a request for information that Kelsey, or anyone on the Community Ops team with access to the internal support system, should already have. marathon__'s UID is not classified material. It is the single most basic piece of identifying information in any casino dispute, and it has almost certainly been attached to every ticket, DM, and public post the player has made. Asking for it again, 19 hours into a public meltdown, is either a stalling tactic or evidence that the internal systems at BC.GAME are organized in a way that makes finding a specific player's case roughly as difficult as finding a specific grain of sand on a beach.

Kelsey's bio describes the role as "Surviving the BCGAME inbox one DM at a time" and "chasing updates & helping players." The coffee-powered emoji is in there too. Fair enough. The inbox is clearly a war zone. But survival is not the same as resolution, and asking a player who has been shouting into the void for two days to please re-submit the most basic piece of information about their case is not help. It is the illusion of help, delivered with a magnifying glass and a double hey.

marathon__ has not yet replied to Kelsey's message. The UID, wherever it is, presumably remains exactly where it has been all weekend.