The situation a reader is in when they open an FAQ
A player who opens Mojogo's FAQ page is usually mid-task. A deposit has not arrived, a withdrawal is pending, a document was rejected, or a bonus did not appear after a qualifying deposit. The FAQ is the fastest route to an answer, and that is precisely what makes it useful and also what makes it dangerous. Useful, because a well-built FAQ answers the mechanical question in seconds. Dangerous, because a reader can mistake a general process answer for a ruling on their own account.
An FAQ page is a collection of answers to questions the operator expects to be asked often. It is written once, published for everyone, and updated on the operator's own schedule. It is not a conversation with support, not a review of any individual account, and not a substitute for the terms and conditions. The reader's job is to know which of those three things they are looking at.
What an operator FAQ can answer bindingly
An FAQ can state process. Process answers are things that are true for every account in the same situation, and they do not depend on the reader's balance, history, or verification state. A question like "which documents are accepted for identity verification" is a process question. A question like "how do I find my transaction history" is a process question. A question like "what happens if I close my account while a withdrawal is pending" is a process question, because the rule applies to everyone.
These answers are binding in the sense that the operator has published them as its own explanation of how it works. If the FAQ says a document must be a colour scan and not a photograph, that is the operator's stated requirement. If the FAQ says a withdrawal is processed only to the method used for deposit, that is the operator's stated route. A reader can reasonably rely on these statements as the operator's position, and can quote them back to support if a dispute arises.
But even a process answer has a shelf life. An FAQ page is edited. A payment route that was listed last month may be removed this month. A document list may be expanded. The reader should treat the FAQ as the operator's current published position, not as a permanent contract. The permanent contract is the terms page, and where the two conflict, the terms page is the document the operator will point to.
Where an FAQ stops being able to help
An FAQ cannot answer anything that depends on the reader's account. It cannot say why this specific withdrawal is still pending, because that depends on the amount, the method, the verification state, and the operator's internal review queue. It cannot say whether this specific document will be accepted, because that depends on the file and on the agent who reviews it. It cannot say when this specific deposit will clear, because that depends on the payment provider and on the operator's processing schedule.
An FAQ also cannot bind the operator on figures. If the FAQ mentions a minimum deposit, a maximum withdrawal, a wagering multiple, or a processing window, that figure is a snapshot. It may be correct today and wrong tomorrow. The operator's own terms page is the only document that states the figure the operator will enforce, and even the terms page can be changed with notice. The FAQ is a convenience; the terms are the contract.
This is the line a reader must hold. When the question is "how does this process work in general", the FAQ is the right document. When the question is "what will happen to my money in this specific case", the FAQ is the wrong document, and the reader should be talking to support or reading the terms. A reader who asks the FAQ to settle an account-specific question is asking a document to do a job it was never designed to do.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted verification documents | Operators revise document lists as regulations or internal policy change | FAQ verification section, or the account verification page |
| Withdrawal routes and method restrictions | Payment providers change their own rules, and operators renegotiate agreements | FAQ payments section, or the cashier page |
| Bonus eligibility and wagering requirements | Promotions are seasonal and terms are rewritten for each offer | FAQ promotions section, or the promotions terms page |
| Processing windows for deposits and withdrawals | Volumes, payment provider delays, and operator policy all shift | FAQ payments section, or the withdrawal policy page |
| Account closure and self-exclusion procedure | Responsible gambling tools are updated as regulation evolves | FAQ responsible gambling section, or the responsible gambling page |
| What happens to a pending withdrawal on account closure | The rule depends on the reason for closure and the operator's current policy | FAQ account section, or the terms and conditions page |
How to read an FAQ page without being misled
The first move is to check the date. Many FAQ pages carry a "last updated" note, and if they do not, the reader should assume the page may be stale. A process answer from two years ago is not a process answer; it is a historical document. The second move is to check the scope. An FAQ answer that says "typically" or "usually" or "in most cases" is not a rule. It is a description of what the operator expects to happen, and the operator is not bound by it when the exception arrives.
The third move is to check the source. If the FAQ answer contains a figure, the reader should find the same figure on the terms page or the payment page. If it is not there, the FAQ figure is either outdated or a summary, and the reader should not rely on it. If the FAQ answer contains a process, the reader should test it against the actual screen. The cashier page shows the methods available; the verification page shows the documents requested; the promotions page shows the terms attached to the current offer.
The fourth move is to use the FAQ as a map, not as a destination. The best FAQ answers point to the page where the binding answer lives. A good FAQ answer on withdrawals will name the withdrawal policy page. A good FAQ answer on verification will name the verification page. A good FAQ answer on bonuses will name the promotions terms page. The reader who follows those pointers is reading the right document. The reader who stops at the FAQ is reading a summary and hoping it is accurate.
When the FAQ does not state an item
An FAQ page that does not state a figure is not incomplete. It is simply not the document that carries figures. The reader should not conclude that the operator has no minimum deposit because the FAQ does not mention one. The reader should conclude that the minimum deposit is stated elsewhere, and the place to look is the cashier page or the terms page. The absence of a figure from an FAQ is not evidence of anything except that the FAQ is not the binding source.
The same applies to process answers. If the FAQ does not say what happens when a withdrawal is rejected, that does not mean the operator has no policy. It means the policy is in the withdrawal terms or the terms and conditions. If the FAQ does not list accepted documents, the verification page will. If the FAQ does not explain how to close an account, the responsible gambling page or the account settings will. The FAQ is a convenience layer over the operator's documents, and a thin one at that.
There is one case where absence is itself the answer. If the FAQ page has no section at all on a topic the reader expects to find there, that is a signal about the operator's priorities, not about the operator's rules. A reader who cannot find a responsible gambling section in the FAQ should look for the responsible gambling page directly. A reader who cannot find a payments section should look at the cashier. The FAQ is not the operator's whole site; it is a curated subset, and the curation itself tells the reader where the operator wants attention to go.
The FAQ and the support channel
An FAQ page and a support conversation are different instruments. The FAQ is public, general, and static. A support conversation is private, specific, and dynamic. A reader who asks support a question that the FAQ already answers will usually be pointed back to the FAQ. A reader who asks the FAQ a question that only support can answer will get a general process description and no ruling on their account.
The practical rule is this: if the question begins with "how do I", the FAQ is the right place to start. If the question begins with "why is my", the FAQ is the wrong place to start, and the reader should open a support ticket. The FAQ cannot see the account, cannot see the transaction, and cannot see the document that was rejected. Support can see all three. The FAQ is a library; support is a conversation. A reader who confuses the two will waste time and may act on an answer that was never about their case.
There is also a third instrument: the terms and conditions. The terms are the operator's contract with the reader. They state the figures, the conditions, and the consequences. The FAQ can summarise them, but it cannot amend them. A reader who finds a conflict between the FAQ and the terms should assume the terms are the document the operator will enforce. The FAQ is a guide; the terms are the law of the site.
FAQ
Does the Mojogo FAQ page bind the operator to what it says?
Process answers on an FAQ page are the operator's published position and can be quoted back to support. Figures on an FAQ page are summaries and may be outdated. The binding document for figures is the terms and conditions page, and where the two conflict, the terms page is what the operator will enforce.
Can the FAQ tell me why my withdrawal is still pending?
No. The FAQ can describe the general withdrawal process and the usual reasons for delay, but it cannot see your account or your transaction. A pending withdrawal depends on your verification state, your method, and the operator's review queue. Only support can tell you why your specific withdrawal is still pending.
Should I trust a figure I read in the FAQ?
Only as a starting point. Find the same figure on the cashier page, the promotions terms page, or the terms and conditions page. If it is not there, the FAQ figure is either a summary or outdated. The operator's own pages are the only binding source for any figure.
What should I do when the FAQ does not answer my question?
Look for the page that governs the topic: the cashier for payments, the verification page for documents, the promotions terms for bonuses, the responsible gambling page for account controls. If the question is about your specific account, open a support ticket. The FAQ is a map, not the destination.
This page is an independent summary of what an operator FAQ page covers and where it stops; it is not published by Mojogo, it states no figure or status for them, and the operator's own FAQ and terms pages are the only binding sources for anything about their service.
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.
