Tickz Support: How to Contact Help

How to Contact Tickz Support

Tickz offers three official support channels: in-app live chat, email through [email protected], and the help-centre articles inside the trading terminal. Pick the channel that matches the urgency of your issue.

Official support email checks

Email goes through [email protected] from any inbox you control, ideally the one tied to your Tickz account. Verify the domain matches tickz.com exactly — phishing senders often use lookalike addresses that swap letters or add hyphens. Send a single ticket per issue with a clear subject line and avoid forwarding chains that bury the original details. If a reply arrives from a different domain, treat it as suspicious and confirm through the in-app chat before sharing any documents.

• Official channel: [email protected]
• Verify the domain matches tickz.com exactly, no lookalikes
• Send from the email tied to your account
• One ticket per issue, clear subject line

App-store support route

The Google Play and App Store listings for Tickz (com.tickz on Android) publish a developer-support link that routes to the broker\'s support team. This is a useful alternative when the in-app chat is unavailable, but app-store routing is not a substitute for the broker\'s own channels — it usually loops back to the same support inbox. Read recent app-store reviews before relying on the store as your primary support route; sentiment shifts visibly over time and tells you what to expect.

• Google Play and App Store list a developer-support link
• Tickz Android package: com.tickz
• Store routing usually loops back to the same broker support team
• Read recent store reviews for current sentiment

In-app help availability

Live chat sits inside the Tickz web terminal and the mobile apps — usually a chat icon in the corner of the trading screen. It is the fastest channel for login problems and quick clarifications. The help centre is reachable from a Help or FAQ link inside the app and covers common login, deposit, and withdrawal topics. Always start from the official tickz.com domain or the official app — never trust support contacts from unsolicited messages, and a legitimate agent will never ask for your password or 2FA code.

• Live chat icon inside the web terminal and mobile apps
• Help centre reachable via the Help or FAQ link
• Never share password or 2FA code with anyone, including a support agent
• Treat unsolicited support contacts as phishing

Chat for speed, email for evidence, help centre for standard procedures — official channels only.

What Support Can Help With

Support can resolve account access, KYC verification, deposits, withdrawals, technical app issues, and explain platform features. It cannot give trading advice or guarantee market outcomes.

Login and account access

Login problems are the most common support ticket and usually clear quickly. The standard flow covers forgotten passwords, locked-account recovery after too many failed attempts, two-factor reset when you have lost the authenticator app, and email-confirmation issues after a fresh signup. Agents can also help if your device fingerprint changes — for example, a new phone or a VPN session triggers an extra verification step. Have your registered email ready and avoid sharing credentials through chat.

• Forgotten password and reset-link issues
• Locked accounts after failed attempts
• Two-factor reset when the authenticator is lost
• Device-fingerprint re-verification after new phone or VPN

Verification and KYC

KYC tickets are the slowest support category and the most common source of withdrawal disputes. Agents confirm which documents are required for your country, the status of an in-progress verification, and what to do when a document is rejected for image quality or mismatched details. Submit clear, full-page photos with all four corners visible and a recent utility bill or bank statement as proof of address. Complete KYC before requesting the first withdrawal to avoid the most common delay.

• Required documents vary by country — ask before uploading
• Photos must be full-page with all corners visible
• Proof of address: recent utility bill or bank statement
• Complete KYC before the first withdrawal request

Deposits and withdrawals

Cashier support covers deposit confirmation, withdrawal status, payment-method changes, and refund handling on failed transactions. What support cannot do: predict whether a trade will be profitable, override the cashier\'s processing time, or recover money lost to your own trading decisions. Trading carries real risk and you can lose more than you deposit. Tickz is licensed offshore (MISA, Comoros) — investor protection is weaker than under CySEC/FCA/ASIC, so cashier discipline matters more, not less.

• Deposit confirmation and failed-transaction refunds
• Withdrawal status and method changes
• Support cannot predict trade outcomes or override processing times
• Document every cashier action with a dated screenshot

Support handles account mechanics — trading decisions and outcomes are not their job.

Information to Include

A first-message ticket that contains the right details resolves in one or two rounds. A vague ticket usually needs five or six. The list below covers what every Tickz support agent will need.

Account email and user ID

Front-load the core account identifiers at the top of every ticket. Without them, the agent has to ask you in the first reply and the round-trip clock starts again. Include the registered email tied to your Tickz account and, where available, the account number or user ID from your profile screen. Never include your password, 2FA code, or full card number in a support message — a legitimate agent will never ask for them.

• Registered email address (the one tied to your Tickz account)
• Account number or user ID from the profile screen
• Clear one-sentence description of the issue
• Never share password, 2FA code, or full card number

Transaction ID and timestamps

For any cashier or trading dispute, exact identifiers and timestamps turn a vague ticket into one a support agent can investigate quickly. Pull the transaction ID from the cashier history, include the payment method, amount, and currency, and note the date and time with the timezone. For trading-platform issues, include the order ID or position number. The information to include in a first message, in order, is summarised below as a single ordered list.

1. Registered email and account or user ID
2. One-sentence description of the issue
3. Exact date and time with timezone
4. Transaction ID, payment method, amount, currency (for cashier issues)
5. Order or position ID (for trading issues)
6. Screenshots showing the error or affected screen
7. Document upload status (for KYC issues)
8. Device model, OS version, app version (for technical issues)

Screenshots and error messages

Screenshots are the single best evidence in any ticket. Crop sensitive numbers but keep the timestamp visible — the timestamp is what lets the agent locate your transaction in the broker\'s logs. For error messages, include the full text rather than a paraphrase, because the exact wording often maps to a specific internal error code. For KYC issues, include a screenshot of the verification status shown in your profile alongside the document you uploaded, the time of upload, and any rejection message received.

• Crop sensitive numbers but keep timestamps visible
• Copy the full error-message text, not a paraphrase
• KYC: include profile status, upload time, and rejection message
• Technical issues: include device model, OS and app versions, and whether the issue reproduces on web

Email, account ID, timestamps, screenshots, transaction IDs — front-load the evidence in message one.

Withdrawal and Payment Complaints

Withdrawal complaints are the most common escalation at any offshore broker. Most resolve within KYC; some need a written complaint and, in extreme cases, an external chargeback.

Escalation steps

Start every withdrawal complaint inside the broker\'s own process — internal complaints are the first and most useful escalation path. Confirm KYC is fully approved before requesting a withdrawal, and match the withdrawal method to the deposit method where possible. If the withdrawal exceeds the broker\'s published processing window with no update, send a written complaint via email and reference the cashier transaction ID. Keep escalations factual, with dated evidence rather than emotion.

1. Confirm KYC fully approved before requesting the withdrawal
2. Match the withdrawal method to the deposit method
3. Wait until after the published processing window before escalating
4. Send a written email complaint referencing the cashier transaction ID
5. If unresolved, contact the MISA regulator and your local consumer body

Stop repeated deposits

The first sign that a withdrawal dispute is heading off the rails is pressure to deposit more — often framed as a "verification deposit," a "tax payment," or a "release fee." Stop. No legitimate broker requires additional deposits to release a pending withdrawal. Tickz is licensed offshore (MISA, Comoros) — investor protection is weaker than under CySEC/FCA/ASIC, and that gap makes recovery scams more likely to follow a genuine dispute. Treat any pay-to-release request as a fraud indicator regardless of who delivers it.

• No legitimate broker requires extra deposits to release withdrawals
• Treat "verification deposit" or "tax payment" demands as fraud indicators
• Recovery scams often follow a genuine dispute — watch for unsolicited offers
• Trading carries real risk and you can lose more than you deposit

Keep written records

Keep screenshots of every cashier action in a dated folder — they are the strongest evidence in any dispute. Save the email thread with full headers if escalation reaches a regulator. For card deposits, your bank chargeback window is finite (usually 120 days), so do not delay if you suspect fraud — speak to your bank about the chargeback option in parallel with the broker complaint. Written records survive when memory does not, and they are the single asset that makes external escalation viable.

• Screenshot every cashier action in a dated folder
• Save full email threads with headers for regulator escalation
• Bank chargeback windows are usually finite — typically 120 days for cards
• Talk to your bank in parallel with the broker complaint if fraud is suspected

Verify KYC first, match deposit and withdrawal methods, document every step — chargeback windows are short.

App and Technical Issues

Most Tickz app problems trace back to outdated app versions, OS-level permission settings, or network restrictions. A short triage checklist clears the majority of tickets before they even reach support.

Update and reinstall checks

Most app issues clear after a basic update-and-restart cycle. Update the Tickz app to the latest version on Google Play or the App Store, update your device OS to a currently supported release, and restart the device once. If the symptom persists, clear the app cache on Android or reinstall on iOS. These steps fix a surprising share of crashes, chart-loading errors, and order-ticket bugs without any further investigation. Try the same action in the web terminal at tickz.com — if it works there, the issue is device-specific.

• Update the Tickz app via Google Play or the App Store
• Update the device OS to a supported release
• Restart the device, then clear cache (Android) or reinstall (iOS)
• Try the action in the web terminal to isolate device-specific issues

Device and network details

Permissions and network routing cause more app failures than code bugs. Confirm the app has permission to use the network and notifications, and that battery-saver mode is not killing background sessions. If you use a VPN, disable it and retry — VPN routing sometimes blocks broker endpoints or triggers extra security checks. Switch between Wi-Fi and mobile data to isolate network-side issues. Note the device model, OS version, and app version for the ticket if the issue persists.

• Check network and notification permissions
• Disable VPN to rule out endpoint blocking
• Switch Wi-Fi and mobile data to test network routing
• Note device model, OS version, app version for the ticket

Bug report evidence

If the issue persists after the basic triage, open a ticket with specific evidence rather than a vague description. A short video or screenshot of the error, the exact steps to reproduce, and the device details listed above turn a debug session from days into hours. Send the package to [email protected] with a clear subject line and one ticket per issue. Specific data points get specific answers; vague tickets get vague replies, and the round trip multiplies.

• Short video or screenshot of the symptom
• Exact reproduction steps in numbered form
• Device model, OS version, app version, and web/app where the issue appears
• One ticket per issue, sent to [email protected]

Triage first, evidence second — most technical tickets clear themselves before a human ever reads them.

When to Seek External Help

If a complaint reaches a stalemate inside Tickz support, the next steps are the offshore regulator and your local consumer-protection body. Each is limited, but each is real.

Regulator or app-store complaint

External escalation makes sense after you have exhausted the broker\'s internal complaints process and have written evidence of the dispute. For a MISA-licensed broker, the escalation paths are narrower than at a CySEC or FCA broker, so set expectations accordingly. File a formal complaint with the MISA regulator in Comoros — response time is slower than tier-one regulators. App-store complaints to Google Play or the App Store can also prompt broker engagement when the dispute concerns the app\'s behaviour rather than a cashier issue.

• Exhaust internal complaints first with written evidence
• File a formal complaint with the MISA regulator in Comoros
• Use Google Play or App Store complaint forms for app-related disputes
• Tickz is licensed offshore (MISA, Comoros) — investor protection is weaker than under CySEC/FCA/ASIC

Bank dispute considerations

For card-deposit disputes, talk to your bank about a chargeback within the bank\'s window — typically 120 days from the disputed transaction date. The chargeback route runs in parallel with the broker complaint, not after it; banks need the evidence file while the dispute is still fresh. For e-wallet or bank-transfer disputes, the recovery options are usually narrower and run through the wallet provider\'s own dispute process. Trading carries real risk and you can lose more than you deposit.

• Card chargeback windows are usually finite — typically 120 days
• Run the bank dispute in parallel with the broker complaint
• E-wallet disputes go through the wallet provider, not the bank
• Bank transfer disputes are usually the hardest to reverse

Recovery scam warning

Once a withdrawal dispute is public, recovery-scam offers usually follow within days. Operators harvest broker complaints from public review sites and contact users with promises to recover the lost funds for an upfront fee. None of those offers are legitimate. No legitimate recovery service requires upfront payment, no regulator endorses third-party recovery agents, and paying the fee is the second loss after the first dispute. Post a factual review on WikiFX or a similar site, but expect contact attempts and ignore them. Verified against Tickz\'s Google Play listing, WikiFX and third-party reviews on May 20, 2026.

• Recovery scams target public complaint posts within days
• No legitimate recovery service requires upfront fees
• No regulator endorses third-party recovery agents
• Ignore unsolicited recovery contact attempts

Internal first, regulator second, consumer body third — and never trade money you cannot afford to lose.