This guide shows how to most effectively use AV Casino help: which channel to choose for a given issue, how to write the first ticket so you can close the case in one go, and what evidence to attach right away. The aim is simple: one clear ticket, a complete set of attachments, and a quick decision instead of weeks of exchanging messages.
Regardless of wording, the rule remains the same: issues with accounts, payments, bonuses or documents should be described concretely, with numbers and a full set of evidence.
Live chat is best for urgent money troubles (deposit, withdrawal, code), straightforward account questions and quick status checks. Email is better for withdrawals, KYC, SoF and complex cases where several documents need to be attached. A phone call or callback may be required when the bank expects verbal confirmation of a transaction or when you want a brief note of the conversation in the system.
For every case open a single thread. In the subject use a simple description, e.g. “Withdrawal pending - wallet corridor - request ID 53421”. In the body three paragraphs: what happened, what you have already checked, what you specifically expect (add a deposit, speed up the withdrawal, manually add a bonus). Attach one ZIP file containing confirmations and screenshots.
SLA is the target time for the first reply. Chat usually answers within a few minutes. Email replies come during working hours, but the banking department operates on weekdays, so withdrawals and settlements must be planned with weekends and holidays in mind.
Use PNG for screenshots, and PDF for statements and invoices. All edges of the document must be visible, you may lightly highlight important lines, and file names like “2025-11-13_receipt_processorID.pdf” help agents navigate attachments.
Case ID is the unique case number. Always cite it in the subject when replying and do not open new threads within the same case. One well-organised thread with the full history moves through the queue much faster than several duplicate tickets.
| Channel | Best for | Typical first response time | When to escalate |
|---|---|---|---|
| Live chat | Money issues, codes, quick status check | 2-10 minutes | After 20 minutes without progress |
| Withdrawals, KYC, SoF, complex cases | 2-12 hours | After the declared window or after 24 h | |
| Phone / callback | Bank confirmations, urgent verifications | As scheduled | When the bank has a same-day deadline |
Mini-case: a withdrawal to the wallet was stuck in pending. The player on chat provided the request ID, and shortly after sent an email with a single ZIP archive containing screenshots from the till and the bank statement. The team quickly located the transaction in the queue, manually unblocked the corridor and the withdrawal was released later that same day.
Resetting the password always starts from the login screen. Open the link from the email on the same device, enter a new password not used before, then log in, log out of all sessions from the profile, and immediately update your backup 2FA codes.
Set up TOTP in your authenticator app, save backup codes offline and, if possible, add a second phone as a backup factor. If you lose access to the main device, support will ask for identity verification before temporarily disabling 2FA.
Too many failed login attempts, a suspicious device or sudden location changes can trigger a security lock. A short lock usually releases by itself, but if you’re pressed for time, send a brief ticket with your name, date of birth and a masked copy of the document to speed up manual verification.
When changing an email, verify the new address, and if you have access to the old one, confirm the change from that account as well. Changing the phone number may require an SMS and sometimes a selfie compared with the document. Data changes during withdrawal reviews may be temporarily blocked for security.
New devices require a one-time confirmation, usually via a link in the email. Sessions also expire after logging out from another device, changing the password or performing important actions in the cashier. If logins keep failing, clear the cache, log in again and sync the time on your phone.
| Symptom | Likely cause | Quick fix | Next step |
|---|---|---|---|
| Password reset loop | Old link or autofill | Open the latest email, disable autofill | Request a manual reset with the ID |
| 2FA code rejected | Skewed time or wrong profile | Sync time on the phone, check the account | Send a screenshot of the backup codes |
| Constant device authorization prompts | Blocked cookies | Allow cookies for the casino domain | Send a console screenshot to support if problems persist |
Find the processor confirmation, note the time, amount and descriptor from the statement, and take a masked screenshot of the line. If after the standard window the funds are still missing, submit one ticket with this package and request manual reconciliation with the processor. The exact schematics by corridor are described in the guide on deposits and withdrawals.
Match the billing address to the bank’s format, enable online or international payments in the bank app, and go through the 3DS step only once. When the page shows “processing”, do not submit further attempts, or you risk double charging.
Wallet tokens expire. If the wallet panel requests re-login, finish logging in in that window and confirm the amount again. Closing the panel too early leaves the transaction in a pending state and prevents the cashier from updating the status.
The typical path is: pending, approved, released. A status on hold means the team is waiting for KYC, SoF or corridor availability. Cite the request ID when asking for the next review time or for a possible split payout.
Some corridors have per-transaction limits. In that case you can request the withdrawal be split into several parts that fit within the limits. All tranches should be under the same Case ID, and you confirm each one individually when it arrives in the account.
After the declared time has passed, write a concise update with the request ID, timestamps, the corridor name and one question such as “please confirm the next review date and whether a split payout will speed up the process.”
| Problem | Evidence to attach | First action | SLA window | Escalation text |
|---|---|---|---|---|
| Uncredited deposit | Processor confirmation, descriptor, masked line from the statement | Wait the standard window, then raise a ticket | 1-12 hours | “Please reconcile on processor ID ...” |
| Withdrawal stuck in pending | Request ID, KYC status | Ask for time of next review | Same - next day | “Confirm next review and queue position” |
| Wallet reauthorization error | Screenshot from wallet window | Relink wallet | Immediately | “Wallet relinked, please refresh status” |
| Double charge suspicion | Two processor IDs for the same attempt | Stop further attempts, open a ticket | 1 working day | “Review and release the duplicate hold” |
After activation, check for a progress bar, ensure the stake is within the limit, and the game is on the allowed list. If the progress bar doesn’t move, quit the game, take screenshots and only then change slots - don’t chase WR on games that may be excluded.
Open the cashier, expand deposit details, paste the code as plain text and confirm before you pay the transaction. If the keyboard covers the field, rotate the screen or zoom out. If the mobile layout stubbornly hides the field, you can enter the code directly in the casino app’s cashier, where the code field is higher up in the form.
Cancel the bonus in the promotions panel before placing further bets that count towards the WR. Take a screenshot with the date and time. Check that the bonus balance has fallen to zero and that the game has switched to cash to avoid later disputes about max cashout.
Save a screenshot of the activation summary, the time, the code, the deposit amount and a short description of the process. In one folder also keep the payment confirmation. When submitting, attach three images and say whether the progress bar appeared at all.
Max cashout applies to the portion of winnings earned from a bonus. In the report quote the exact rule clause, show a screenshot of the balance composition (cash + bonus) and ask the agent to clearly confirm: how much is fully withdrawable cash, and which portion is subject to the limit. You can find examples of games with different limits in the bonuses and low wagering section.
| Error | Likely cause | Clean fix | Evidence |
|---|---|---|---|
| Code not accepted | Space, typo or code expired | Paste as plain text, try again | Error banner, code tile |
| No progress bar | Game not on the approved list | Switch to a slot from the whitelist | Game name, stake, timestamp |
| Winnings removed | Bet limit exceeded | Provide the session log | Bet list, regulation excerpt with cap |
The most commonly accepted IDs are a passport or national ID card with a clear photo and all edges in frame. Proof of address is a recent utility bill or bank statement with your full name and address. Clear, sharp screenshots are fine as long as nothing important is cut off.
Take photos in daylight, place the document on a flat, contrasting background and avoid reflections. Ensure that your first name, last name and address in the profile are written exactly as in the documents. Submit PNG or PDF files that fit the size limit.
SoF (source of funds) answers where the funds for deposits come from. Usually payslips, invoices for your business or bank statements are sufficient, provided the sums align with typical account funding levels. Non-game lines you may black out, leaving visible: the institution name, your name and the sums.
Common reasons for rejection include glare on the photo, cropped edges or overly strong blacking out of data. On retry use diffuse light, show all edges, and black out only details that truly don’t need verification.
Simple KYC often completes the same day if the files are sharp and profile data matches. When the given time passes, reply in the same thread with a brief summary and ask for the next review date. Do not open a new ticket for the same verification.
| Reason | Example | Quick fix | How to avoid in future |
|---|---|---|---|
| Document glare | Light band across the photo | Take a new photo in daylight | Matte background, no sharp spot lighting |
| Mismatched address | Different street format in profile and on the bill | Copy the format from the bill | When registering, use full data from the start |
| Excessive blacking out | Document issuer not visible | Unblur the issuer and the sums | Mask only fields not relevant to the case |
Escalate a case only after the declared SLA has passed or when you have new, substantive evidence that genuinely changes the picture. Escalations without new data slow the queue for other players and rarely speed up a decision. Keep a factual tone and avoid emotional phrasing.
Use three paragraphs: a brief problem summary with IDs and dates, a list of evidence and steps taken, one sentence with the desired outcome. Attach one ZIP archive named e.g. “2025-11-13_case53421.zip”.
A reversal returns a withdrawal in pending status back to the player's balance to correct data or change the corridor. Use it once per request – frequent reversals and resubmissions add work to the payments team and lengthen the queue.
Record the date, time, channel of contact, agent’s name and a brief summary of the response. Such a diary helps support immediately understand what has already happened and increases the chances of a same-day decision.
A small test withdrawal is also a great benchmark for support: it shows which corridor works, how fast the transfer arrives and which evidence proved decisive. If your aim is fast withdrawals when playing for real money, consider aligning sessions and payments with the schemes in the guide on real money play and fast cashouts.
After the dispute is resolved, write a short note: which corridor actually worked, which documents helped support, which steps could have been taken earlier. Based on this you can adjust your standard limits, preferred payment method or how you gather evidence. It’s also worth revisiting the quick start guide to harmonise “account hygiene” for the future.
| Day | Action | Expected reply | If no reply | Notes |
|---|---|---|---|---|
| 0 | Open the first ticket with the full package | Start of the SLA window | Wait the full window | Only one thread |
| 1 | Brief follow-up with Case ID | Status update | Ask for the time of the next review | No new threads |
| 2 | Escalation letter with the same package | Review by a senior agent | If needed, reversal decision | Calm, factual tone |
Mini-case: a dispute over the code “code not accepted” ended in 2 hours when the player sent a ticket with a ZIP archive containing the till screen, the code tile, the deposit confirmation and a one-line request for manual addition of the bonus or a new code. After verification, the agent manually allocated the promotion and added the missing free spins.