The moment an FAQ stops being enough
A player opens an operator's FAQ because something is stuck: a deposit has not appeared, a withdrawal is pending, a bonus did not trigger, or a document was rejected. The FAQ is the first place they look, and for a certain class of question it is the right place. For another class, it is the wrong place, and knowing the difference is what saves a player from acting on an answer that was never about their account.
An operator FAQ is a collection of general answers. It explains how the cashier normally works, which documents are usually requested, what a wagering requirement means as a concept, and which routes exist for getting help. It does not know the reader's balance, their verification status, their payment method, or the state of their last withdrawal. Those facts live in the account, and no FAQ can see into an account.
The practical rule is simple: a question about how the system works can be answered by an FAQ. A question about what is happening to me right now cannot. The first kind of question has one answer for everyone. The second kind has an answer that changes from player to player and from day to day, and the FAQ can only point toward the channel that carries it.
What an FAQ can settle: process, routes, document lists
The strongest part of any operator FAQ is the part that describes mechanics. A reader can expect to find, and can reasonably rely on, answers of this kind:
| Question type | What the FAQ can tell you | Where the binding detail lives |
|---|---|---|
| Deposit routes | Which payment methods the cashier generally offers, and the broad steps for using each | The cashier itself, which shows only the methods available to the reader's account and region |
| Withdrawal process | The sequence: request, verification, release, arrival; and what can hold a withdrawal at each stage | The reader's withdrawal history and any message attached to the specific request |
| Verification documents | The categories of documents usually requested: identity, address, payment method | The document request sent to the reader, which names the exact items and formats |
| Bonus mechanics | What wagering means, how it attaches to a deposit, and why a bonus balance is separate from a cash balance | The promotion's own terms page, which carries the multiple and the game weightings |
| Account tools | Where limits, self-exclusion and history are located in the account interface | The account settings themselves, which reflect the current state of the reader's choices |
| Support routes | Which channels exist: live chat, email, ticket, and their general availability | The contact page or support panel, which shows the channels currently open to the reader |
What these have in common is that they describe a system. A deposit route either exists in the cashier or it does not. A verification step either happens before a withdrawal or it does not. The FAQ can state these things because they do not depend on who is reading.
But even here, the FAQ is a summary. It may say that verification is required before a first withdrawal, but it will not say which of the reader's documents failed. It may say that a bonus has wagering, but it will not say how much of the reader's wagering remains. The FAQ gives the shape of the process; the account gives the state of the process.
What an FAQ cannot settle: anything account-specific
The moment a question contains the word "my", the FAQ is no longer the binding source. "My withdrawal is pending" is not the same question as "how do withdrawals work". The first is about a particular request with a particular history. The second is about the machinery. An FAQ answers the second and can only gesture at the first.
Several categories of question fall into this gap, and a reader should recognise them before trusting an FAQ answer:
| Question | Why the FAQ cannot answer it | Where the answer is |
|---|---|---|
| Why is my withdrawal still pending? | The reason is attached to the specific request: a document missing, a method mismatch, a review flag | The withdrawal record in the account, and any message from the payments team |
| Why was my deposit not credited? | The cause depends on the payment provider, the amount, and the reader's account state | The transaction history and the payment provider's own record |
| Why was my document rejected? | The rejection names a specific defect in a specific file | The rejection notice, which states what was wrong and what to resend |
| How much wagering do I have left? | The remaining amount is a running balance attached to the reader's bonus | The bonus progress display in the account |
| Why is a game not loading for me? | The cause may be the reader's device, region, connection, or account state | The game's error message and the support channel |
| Why was my account restricted? | The restriction is a decision about the reader's account, not a general rule | The notice sent to the reader, and the support channel for explanation |
The pattern is consistent. An FAQ describes the rule. The account applies the rule to a particular person. When a reader needs the application, not the description, the FAQ has done its job by telling them where to look next.
Where the binding answer lives instead
For every question an FAQ cannot settle, there is a document or channel that can. The reader's task is to move from the general page to the specific one, and the FAQ is useful precisely because it maps that route.
The hierarchy is worth stating plainly. The most binding source is the account itself: the balance, the transaction history, the bonus progress bar, the verification status. Nothing else overrides what the account shows, because the account is the operator's own record of what is happening to the reader. Next come the documents that govern a transaction: the promotion terms for a bonus, the withdrawal policy for a payout, the AML page for a large transfer. These set the rules the account applies. The FAQ sits above all of them as a map: it tells the reader which document governs which question, but it does not replace any of them.
When an FAQ answer and an account display disagree, the account display wins. When an FAQ answer and a promotion terms page disagree, the terms page wins. The FAQ is a summary, and a summary is only as good as its last update. The terms page and the account are live.
This is not a defect of the FAQ. It is what an FAQ is for. A page that tried to answer account-specific questions would have to be connected to the account system, and then it would not be an FAQ; it would be the account itself. The separation is the design.
How to read an FAQ without being misled
The most common misreading is to take a general answer as a personal one. A player reads that withdrawals are processed in order, and concludes that their withdrawal is therefore being processed in order. That conclusion does not follow. The FAQ describes the normal sequence; it says nothing about the reader's place in it.
A second misreading is to take an example as a promise. An FAQ may illustrate a wagering requirement with a hypothetical: suppose a bonus carries a multiple, then a player must wager that multiple of the bonus before withdrawing. The reader then assumes their bonus carries that same multiple. It may or may not. The example teaches the mechanic; the promotion terms carry the number.
A third misreading is to treat the FAQ as complete. No FAQ lists every edge case, every payment method failure mode, every document format that will be rejected. The FAQ covers the common path. When the reader is on an uncommon path, the FAQ's silence is not an answer; it is a sign to open the support channel.
The discipline is to ask, of every FAQ answer: is this about the system, or about me? If it is about the system, it is probably reliable. If it is about me, it is probably a pointer, not an answer.
What changes, and why an FAQ can lag
An FAQ is a static page, or close to it. The things it describes are not static. Payment methods are added and removed. Verification requirements are tightened. Bonus terms are rewritten. Withdrawal policies are amended. Each of those changes can make an FAQ sentence wrong overnight.
This is why the FAQ is never the final word on a figure. A withdrawal timeframe stated in an FAQ is a description of the operator's general practice at the time the page was last edited. The timeframe that applies to the reader's withdrawal is the one in force when the request was made, and it is stated in the withdrawal policy and in the withdrawal record. Across operators, processing commonly takes anywhere from a few hours to several business days, but the reader's own figure is not in the FAQ; it is in the account.
The same applies to document lists, bonus mechanics, and support hours. The FAQ gives the shape. The live page gives the current content. A reader who relies on an FAQ figure without checking the live page is reading a snapshot and calling it a policy.
FAQ
Can I trust the answers in an operator FAQ?
For questions about how the system works, an FAQ is usually reliable: it describes the cashier, the verification flow, and the bonus mechanic. For questions about your own account, it is not reliable, because it cannot see your account. Treat it as a map, not as a record.
Where do I find the answer to a question about my own withdrawal?
In your withdrawal history and in any message attached to the specific request. The FAQ can tell you the general stages a withdrawal passes through, but the reason yours is at a particular stage is a fact about your request, not a general rule.
Why does the FAQ not state the wagering requirement for a bonus?
Because the requirement is set by the promotion's own terms, and it can differ from one promotion to the next. The FAQ may explain what wagering means; the promotion terms page carries the multiple that applies to a specific bonus.
What should I do when the FAQ and the account disagree?
Follow the account. The account is the operator's live record of your balance, status and transactions. The FAQ is a summary that may lag behind a policy change. When they conflict, the live source governs.
This page is an independent summary of what an operator FAQ covers and where it stops; it is not published by leroijohnny.com, and it states no figure or status for that operator. The operator's own FAQ and account pages are the only binding source for what the operator answers and what applies to a specific player.
Play responsibly
Gambling should be treated as paid entertainment, never as a way to earn income or recover losses. 1-800-MY-RESET (1-800-697-3738)
18+ or 21+ depending on where you are; follow the minimum age that applies to you.
This article is general information about how these mechanics work. It is not legal advice and not a recommendation to gamble or to use any particular operator. Availability and legality differ by jurisdiction — check the rules that apply where you are.
