The situation an FAQ page handles
A reader lands on an FAQ page because something is stuck: a deposit has not appeared, a withdrawal is pending longer than expected, a document was rejected, or a game rule is unclear. The FAQ is the operator's attempt to answer the most common versions of those questions without a support ticket. What matters is not how many questions the page lists, but which category each question falls into. A question about process — what steps to follow, which documents are accepted, where a button is — can usually be answered on the page. A question about the reader's own account — why this deposit failed, when this withdrawal will clear, whether this document is enough — cannot, because the answer depends on data the FAQ does not hold.
Words With Friends publishes its FAQ as one of several help surfaces. The page is most useful when the reader treats it as a map of processes, not as a ruling on their case. Every answer on it describes what normally happens, not what has happened to the reader. The distinction controls how much weight the reader should give any sentence they find there.
What an FAQ can answer bindingly
An FAQ can state the operator's standard routes and document lists. If the page says a withdrawal is returned to the method used for the deposit, that is a process statement: it tells the reader what the system will attempt, and it holds unless the operator's own terms say otherwise. If the page lists the documents accepted for verification — a passport, a driving licence, a utility bill — that list is also a process statement. The reader can rely on it as the operator's published position, with one caveat: the page may be older than the current terms, and the terms page is the version that binds.
Questions an FAQ can settle include: which menu opens the cashier, what the minimum steps are to close an account, whether a bonus requires a deposit, and how to find the self-exclusion tool. These are questions about where things are and what the operator's standard flow is. The answer does not depend on the reader's balance, history or status.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted verification documents | Compliance requirements change; the list may be updated without notice | The FAQ's verification or KYC section; the terms page for the binding version |
| Withdrawal routes | Payment providers are added and removed; a route may be deposit-only | The cashier and the payments or withdrawals page, not the FAQ alone |
| Bonus eligibility rules | Promotions are revised frequently; an FAQ answer may lag | The specific promotion's terms, linked from the offer itself |
| Account closure steps | Process changes when the operator updates its back office | The FAQ's account section, confirmed by support if the steps fail |
| Self-exclusion options | Regulatory requirements evolve; the tool may gain or lose features | The responsible gambling page and the account settings |
The table's third column is the point. An FAQ is a convenience layer. It repeats what the operator wants the reader to know, but the binding statement of a rule is the rule's own document. When the FAQ and the terms disagree, the terms win, and the reader should not expect the FAQ to say which is newer.
Where the FAQ stops: account-specific questions
The most common reason a reader opens an FAQ is also the reason the FAQ cannot finish the job. "Why is my withdrawal still pending?" is an account-specific question. The answer depends on the reader's verification status, the withdrawal amount, the method chosen, and the operator's current queue. No FAQ can know those things, so no FAQ answer about them is binding on the reader's case. The page can say what normally causes delays and what the reader should check, but it cannot say what is true of this withdrawal.
The same applies to deposit failures. An FAQ can list common causes — a declined card, a mismatch between the account name and the payment method, a bonus restriction — but it cannot say which one applies. The reader's transaction history and the operator's payment logs hold that answer. The FAQ's value is to shorten the list of things the reader checks before contacting support.
This is not a weakness of Words With Friends' FAQ specifically. It is a structural limit of every FAQ. The page is static text; the reader's account is live data. No static page can rule on live data. The reader who expects an FAQ to explain their specific delay will read every answer as a promise and then feel the promise was broken. The reader who expects it to explain the categories of delay will use it correctly.
How to read an FAQ answer without being misled
Three moves make an FAQ answer safe to use. First, check the verb. If the answer says the operator "may", "can", "typically" or "usually" does something, it is describing a range, not a rule. The reader should treat it as background, not as a commitment. If it says the operator "will" or "must", the reader should still confirm the same statement appears in the terms or the relevant policy page, because the FAQ is not the document that binds.
Second, check the date. Most FAQ pages carry no revision date, which means the reader cannot tell whether an answer predates a rule change. A withdrawal route listed in an FAQ may have been removed from the cashier months ago. The cashier is live; the FAQ is not. The reader should always confirm any route, limit or document list against the page where the action happens.
Third, separate the answer from the question it answers. An FAQ often groups several related questions under one heading. The reader who skims may attach an answer about bonus wagering to a question about withdrawal limits. The two are different rules with different documents. Reading the question first, then the answer, then asking which document the answer points to, prevents most misreadings.
What the FAQ cannot tell you, and where that answer lives
Some answers are not on the FAQ because they cannot be. The exact wagering multiple on a bonus is in the promotion's own terms, not in a general FAQ, because it differs from one offer to the next. The exact withdrawal limit for a given method is in the cashier or the payments page, because it differs by method and by account status. The exact status of a verification document is in the reader's account, because it is a record, not a rule. The reader who asks the FAQ for these answers will get either a general range or a pointer, and the pointer is the useful part.
When the FAQ does not state an item, the absence is information. If the page does not name the testing laboratory or the regulator, there is nothing for the reader to verify, and that absence is itself the answer to the question. If the page does not list a withdrawal route for a deposit method, the reader cannot assume one exists. If the page does not state a processing window, the reader should not invent one. The FAQ's silence is not a gap in the page; it is the page saying that the answer lives elsewhere or does not exist as a published commitment.
FAQ
Does the FAQ tell me when my withdrawal will arrive?
No. An FAQ can describe the operator's standard processing stages and the common causes of delay, but it cannot know the status of a specific withdrawal. The reader's account and any support ticket are the only places where that status is visible. A timeframe printed in an FAQ is a general statement, not a promise about a particular transaction.
Can I rely on the document list in the FAQ for verification?
As a starting point, yes. The FAQ's list of accepted documents reflects the operator's published position at the time the page was written. But compliance requirements change, and the verification screen in the reader's account is the live version. If the two disagree, the live screen and the terms page are the versions that bind.
What should I do when the FAQ and the terms say different things?
Treat the terms as the binding document. An FAQ is a summary and may be older than the current terms. Where the two conflict, the reader should follow the terms and, if the difference affects a deposit or withdrawal, ask support to confirm which version applies to their account.
Why does the FAQ keep pointing me to other pages?
Because the FAQ is a map, not the territory. Rules that depend on the reader's account, the payment method, or the specific promotion cannot be stated once in a general FAQ and remain accurate. The pointers are the FAQ doing its job: routing the reader to the document that holds the binding answer.
This page is an independent summary of what an operator FAQ covers and where it stops; it is not published by Words With Friends, and it states no figure or status for that operator — the operator's own FAQ and terms pages are the only binding sources.
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.
