Geo-Blocked Players File 3x More Support Tickets Than They Bet
Players who hit a geolocation wall on a regulated U.S. sportsbook or casino app open support tickets at roughly three times the rate of players who place a bet in the same session, according to ticket-volume data that operators and platform vendors rarely publish but quietly staff against. The pattern holds across states with legal markets and across product verticals — sportsbook, casino, and poker — which suggests the problem is not a single vendor's bug but a structural feature of how U.S. online gambling enforces its borders.
That ratio matters more than it first appears. Geolocation failures are usually discussed as a compliance cost: the operator risks a fine if it takes a wager from someone outside a legal jurisdiction, so it blocks first and asks questions later. What gets lost is the downstream cost. A blocked player is not a neutral event. It is a customer who has already deposited, already opened the app with intent, and now has to be handled by a human — often several times, because the first answer rarely resolves anything.
The Block Is Cheap. The Ticket Is Not.
On the operator's balance sheet, a geolocation block looks almost free. The software checks a device's location against a state boundary, finds a mismatch or an ambiguous signal, and declines the action. No wager is placed. No payout is owed. From a compliance standpoint, the system did exactly what it was built to do.
The support ticket is where the cost lands. A single contact to a live agent on a regulated U.S. operator routinely runs between $4 and $9 in fully loaded labor cost once you account for training, workforce management, and the tools agents use, according to figures circulated among customer-operations vendors. A geolocation-related contact is worse than average because it is rarely a one-touch resolution. The player wants to know why they were blocked, whether their account is in trouble, whether their money is safe, and how to fix it. That is a multi-message exchange at minimum, and a meaningful share of these cases escalate to a second or third contact.
Multiply that by the block rate. If a mid-sized operator with 200,000 monthly active users in a single state sees geolocation friction on 3% of sessions — a conservative figure for players near borders, on VPNs, or on flaky mobile connections — that is 6,000 affected sessions a month. If those sessions generate tickets at three times the baseline rate, and the baseline is, say, 1.5%, the operator is looking at 270 extra tickets a month from this one cause. At $7 apiece, that is nearly $23,000 a year in labor for a single state, before counting the revenue from the players who simply give up and leave.
The give-up number is the one nobody can see. A player who is blocked, files a ticket, waits 40 minutes, and gets a canned response about "regulatory requirements" may not file again. They just stop opening the app. That churn is invisible in the ticket data, which is precisely why operators underweight it.
Why the Three-to-One Ratio Shows Up
Three-to-one is not a law of nature. It is what you get when a friction event lands on a population that is, by definition, motivated. The player who gets geolocated out was trying to do something — place a bet, spin a slot, join a table. They had intent. Intent is what drives contact volume. A player browsing without intent generates far fewer tickets per session than a player whose action was just refused.
There is also a selection effect. Players who trigger geolocation blocks disproportionately include people on the edges of a state, people traveling, people on corporate or campus networks with shifted IP geolocation, and people using VPNs — a group that already skews toward higher engagement and higher support needs. They are not a random sample of the user base.
The Four Failure Modes Behind Most Geolocation Tickets
Support teams that categorize geolocation contacts tend to see the same handful of causes, and each has a different fix cost.
Border bleed. A player in Jersey City, New Jersey, sitting near the Hudson River, can register on a New York-facing cell tower or a Wi-Fi network whose IP resolves to Manhattan. The geolocation vendor sees New York, where the operator may not hold a license, and blocks. The player is physically in a legal state and cannot understand why they are being treated as a criminal. This is the single most common source of "I'm in [legal state], why can't I bet" tickets.
VPN and privacy tooling. A growing share of U.S. consumers run a VPN by default on mobile, often bundled with a security suite they installed and forgot about. When that VPN exits in a non-legal state, the operator blocks. The player may not even know the VPN is on. Untangling that requires an agent to walk someone through their phone settings, which is not a two-minute call.
Device permission drift. Geolocation on regulated apps depends on location permissions, and those permissions get revoked — by an OS update, by a privacy cleanup, by a user who tapped "don't allow" once and forgot. The app then cannot confirm location and blocks. The fix is simple in theory and maddening in practice, because the player has to find the right settings menu while an agent talks them through it.
Account and identity mismatches. A player who moved, changed phone numbers, or registered with an old address can trip identity checks that surface as geolocation errors. These tickets are the most expensive because they often require document review and can take days.
Each of these produces a ticket. None of them produces revenue.
The Compliance Trap
Operators cannot simply loosen the geolocation check to reduce tickets. State regulators require that a wager be placed from within the state's borders, and the penalties for getting that wrong are severe — license suspension, fines in the millions, and in extreme cases the loss of market access. The geolocation vendor's contract typically specifies a confidence threshold, and lowering it to reduce false positives is a decision that has to be justified to a compliance officer, not a support manager.
That asymmetry — huge downside for a false negative, modest downside for a false positive — is why the block rate stays high even when operators know it is generating tickets. The support cost is a rounding error next to the regulatory risk. So the tickets keep coming.
What the Numbers Look Like When You Actually Count
The three-to-one figure is a ratio, not an absolute, and it moves with how you define a session and a ticket. A few anchors help.
Ticket-per-session baselines for regulated U.S. operators generally sit somewhere between 0.8% and 2.5%, depending on product and state. Sportsbook skews lower because the interaction is fast and the outcome is binary; casino and poker skew higher because sessions are longer and players encounter more edge cases. If you take 1.5% as a middle estimate, a three-to-one geolocation ratio implies roughly 4.5% of blocked sessions generate a ticket. That is a contact rate you would expect from a serious outage, not from a routine location check.
The block rate itself varies enormously. Operators in compact, densely populated states with lots of cross-border commuting — New Jersey, Pennsylvania, Illinois, Michigan — report more geolocation friction than operators in large, geographically isolated states. A single-state operator in a state like Arizona or Colorado sees a lower block rate than one serving the Philadelphia or Chicago metros, where state lines cut through media markets and cell coverage.
Timing matters too. Ticket volume from geolocation spikes on weekends, on the first weekend of NFL season, and around major betting events, because that is when casual players — the ones least likely to have their location settings dialed in — show up. Support queues that are already stretched on a Sunday afternoon get stretched further by a wave of "why can't I bet" contacts that all require the same manual troubleshooting.
There is also a measurement problem. Most operators tag geolocation tickets with a reason code, but the tagging is inconsistent. A player who contacts support about a failed deposit after being blocked may be coded as a payments issue. A player who asks "is my account locked" may be coded as account security. The true geolocation ticket count is almost certainly higher than the reason-code report suggests, which means the three-to-one ratio may understate the problem.
The Vendor Layer
Operators do not build geolocation in-house. They buy it from a small set of vendors — GeoComply is the dominant player in the U.S. regulated market, with others like Xpoint and various identity vendors offering adjacent services. These vendors sell accuracy, and their contracts are built around confidence thresholds and false-positive rates.
The vendor's incentive and the operator's support team's incentive are not aligned. The vendor is measured on whether it correctly identifies out-of-state attempts. The support team is measured on ticket volume and resolution time. A vendor can hit its accuracy targets while generating a flood of false positives that the operator's agents have to absorb. That cost sits with the operator, not the vendor.
Some operators have pushed back, negotiating for better handling of ambiguous signals — for example, a "soft block" that prompts the player to re-confirm location rather than a hard refusal. Soft blocks tend to convert better and generate fewer tickets, because the player gets a path forward instead of a dead end. But soft blocks require product work and carry a small compliance risk if the re-confirmation is too permissive. Adoption has been uneven.
The Player Experience Nobody Designed
From the player's side, the geolocation block is close to the worst possible interaction. It arrives at the moment of highest intent, it uses language that sounds accusatory ("we cannot verify your location"), and it offers no obvious remedy. The player does not know whether they did something wrong, whether their account is flagged, or whether their deposit is at risk.
That ambiguity is what drives repeat contacts. A clear error — "your location settings are off, here's how to fix it" — resolves in one message. A vague error — "location verification failed" — generates a follow-up, then another, then a request to speak to a supervisor. Each step adds cost and erodes trust.
Operators that have invested in clearer error messaging report measurable drops in geolocation ticket volume, sometimes by a third or more, without changing the underlying block logic. The block still happens. The player just understands it and either fixes it themselves or accepts it. That is a product fix, not a compliance fix, and it is cheaper than adding support headcount.
The harder problem is the player who is genuinely blocked and cannot fix it — the one on a VPN they can't disable, or in a border zone where the signal is genuinely ambiguous. For that player, there is no good answer short of manual verification, which is expensive and slow. Some operators offer a one-time manual location confirmation; most do not, because it does not scale.
Where the Money Actually Goes
It is worth being precise about what the three-to-one ratio costs. Support labor is the visible line item, but it is not the largest. The largest is the suppressed revenue from players who are blocked, frustrated, and gone.
If a blocked session has, say, a 30% chance of converting to a wager absent the block, and the average wager generates a hold of some percentage, then every block has an expected revenue cost attached to it. For a player who would have bet $50 at a 5% hold, that is $2.50 in expected gross revenue — small per event, but multiplied across thousands of sessions a month, it adds up to real money. And the churn effect compounds it: a player who has a bad geolocation experience once is measurably less likely to return, which means the cost is not just the lost wager but the lost lifetime value.
Operators rarely model this. Geoloation is treated as a compliance function, and compliance functions are not usually asked to produce a return-on-investment analysis. The result is that the true cost of geolocation friction is dispersed across support, product, and revenue teams, and no single owner is accountable for reducing it.
The Question Operators Have Not Answered
The three-to-one ratio is a symptom, and the underlying condition is that U.S. online gambling has built a border-enforcement system optimized for regulatory defensibility rather than player experience. That was a reasonable choice when the market was new and the priority was proving to regulators that legal operators could keep out-of-state players out. It is a less reasonable choice now that the market is mature, the vendors are entrenched, and the players are sophisticated enough to notice when a routine location check feels like being accused of something.
The open question is whether any operator will treat geolocation friction as a product problem rather than a compliance cost — investing in soft blocks, clearer messaging, and self-service location fixes, and then measuring the ticket reduction and retention lift against the compliance risk. The vendors have little incentive to lead that charge, because their contracts reward accuracy, not player experience. The regulators have little incentive, because the current system works well enough from their side of the table. That leaves the operators, who bear the support cost and the churn, to decide whether the three-to-one ratio is a number worth moving — or just a cost of doing business in a market where the borders are real and the players keep testing them anyway.
For players, the practical takeaway is narrow but useful: if you are in a legal state and getting blocked, check your VPN and your location permissions before you open a ticket. For operators, the takeaway is less comfortable. The block is doing its job. The question is whether everything around it is doing theirs.