Customer care is the path you take when the app, the contest, or the KYC flow stops working. The path deserves a calm, documented approach. This guide covers the verified channels, the information you should prepare, the scam warnings, and the escalation steps when the first response is not enough.

Verified channels only

Use only the contact channels published on the operator's official site. Treat social-media DMs, WhatsApp messages, and unsolicited phone calls as scams. The operator's official help section is the source of truth; if a channel is not listed there, do not use it.

An adult reviewing blank support evidence pages on a clean desk
Verified channels only: the operator's official help section is the source of truth.

Document the issue

Before contacting customer care, document the issue: the date, the time, the device, the app version, the screen flow, and the error message. A timeline is the most useful thing you can send; it saves a back-and-forth and it accelerates the resolution.

A laptop and phone showing a fake vs genuine login URL side-by-side
Document the issue: date, time, device, app version, screen flow, error message.

Response expectations

Most operators respond within 24 to 72 hours. For KYC and withdrawal issues, the response can take up to 7 working days. If the response stalls beyond the published SLA, escalate.

An adult waiting calmly beside a phone and analog clock after submitting a support request
Response expectations: 24 to 72 hours for general issues, up to 7 working days for KYC and withdrawal.

Escalation checklist

If the first response does not resolve the issue, escalate: send a second message with the original ticket reference, the timeline, and a clear statement of what you want. If the second response stalls, contact the operator through a second channel — typically email plus in-app chat.

Adult sorting blank support records into an orderly escalation sequence
Escalation: second message with the original ticket reference, then a second channel.

Verified channels in detail

Verified channels are the only channels you can trust. Social-media DMs, WhatsApp messages, and unsolicited phone calls are the most common scam vectors. The operator's official help section is the source of truth; if a channel is not listed there, do not use it.

Verified channels also include the operator's official email. The official email is the second-most-trusted channel after the in-app chat; the email is also the most useful channel for issues that require documentation.

Documenting the issue in detail

Before contacting customer care, document the issue: the date, the time, the device, the app version, the screen flow, and the error message. A timeline is the most useful thing you can send; it saves a back-and-forth and it accelerates the resolution.

Documenting the issue also includes screenshots. Screenshots are the most useful tool for showing the error message; take them before clearing the screen. The screenshot is the most useful single piece of evidence you can send.

What to do if you are scammed

Document the scam, contact your bank, file a complaint with the cyber-cell, and inform the operator. Do not send additional money to anyone claiming to be the operator. The scam recovery process is slow, but the documentation is the most useful input.

If you are scammed, also change the passwords for any account that shared the compromised password. The compromised password is the most common entry point for follow-up scams. The password change is the most useful single step you can take.

Fantoss questions on customer care

Where do I find the operator's official channels? On the operator's official website, in the app's help section, and in the registration email. Do not trust channels listed anywhere else.

What if I am scammed? Document the scam, contact your bank, file a complaint with the cyber-cell, and inform the operator. Do not send additional money to anyone claiming to be the operator.

Can Fantoss resolve operator issues? No. Fantoss is an editorial publication. For operator issues, contact the operator through the verified channels.

Move from customer care to account safety

After the issue is resolved, audit your account: change the password, enable 2FA, and review the active sessions.

Open login guide

Why verified channels matter

Verified channels are the only channels you can trust. Social-media DMs, WhatsApp messages, and unsolicited phone calls are the most common scam vectors. The operator's official help section is the source of truth; if a channel is not listed there, do not use it.

How to document an issue

Before contacting customer care, document the issue: the date, the time, the device, the app version, the screen flow, and the error message. A timeline is the most useful thing you can send; it saves a back-and-forth and it accelerates the resolution.

What to do if you are scammed

Document the scam, contact your bank, file a complaint with the cyber-cell, and inform the operator. Do not send additional money to anyone claiming to be the operator. The scam recovery process is slow, but the documentation is the most useful input.

How to read this page across a season

The most useful way to read this guide is to revisit it after every contest night. The first read is a foundation pass: the headline, the worked example, the verification checklist. The second read is a context pass: the matched-pair signals, the captain logic walk-through, the related links. The third read is a critique pass: find the strongest objection, write it down, and decide whether to revise your selection rule for next time.

The three-pass habit is what turns a guide into a season-long tool. Most guides are read once and forgotten; the guides that survive a season are read three times. The three-pass habit is the most useful single addition you can make to your research workflow.

What other readers found useful

The most-read sections of this guide are the worked example, the captain logic walk-through, and the verification checklist. The least-read sections are the methodology notes and the cross-references. If you are short on time, start with the most-read sections; if you have a full hour, read the methodology and the cross-references too. The reading order is part of the value of the guide.

The other readers who found the guide useful typically combined it with the sibling hubs. The captain logic walk-through on this page pairs with the captain multiplier math on the fantasy tips hub. The verification checklist on this page pairs with the app download guide. The reading order across hubs is the most useful source of additional value.

How to send corrections

If you find an error in this guide, use the contact page to report it. Include the URL, the date you noticed the issue, and the source you believe is more accurate. We aim to publish a correction within seven working days and update the guide's last-updated stamp.

Corrections are part of the publication's value. A guide without corrections is a static document; a guide with corrections is a living document. The corrections process is the most useful source of trust in the publication.

The discipline of writing your own notes

The most underrated habit in fantasy research is writing your own notes. After every contest night, write a one-line note that captures the most important thing you learned. The note should be specific, dated, and actionable. "Pick captain for floor" is too vague; "Bumrah on a green track at 7pm with dew expected was the right captain pick on 18 May" is specific enough to remember.

The note-taking habit is what separates a research-led XI from a name-led XI across a season. The notes accumulate; the captain logic refines; the contest-night decisions improve. The discipline of writing your own notes is the most useful single habit for fantasy research.

Common objections to this guide

Every guide on Fantoss is read by a second editor who writes the strongest possible objection. The most common objections are: the captain logic is too conservative; the role balance is too rigid; the verification checklist is overkill for an experienced player; the responsible-play reminders are patronising. Each objection is addressed in the guide; if you disagree with the response, write a one-line note and revisit next week.

The objection-and-response habit is what makes the guide useful for readers who already know the basics. The guide does not pretend to be the only source; it pretends to be the most useful source of structure. The structure is the most useful single contribution.

How this guide compares to operator-published material

Operator-published material is the authoritative source for the operator's own rules, terms, and eligibility lists. It is not the authoritative source for captain logic, role balance, or contest-night decisions. Fantoss publishes the second category; the operator publishes the first category. The two sources are complementary, not competitive.

Where this guide references an operator, we link to the operator's own published information for the authoritative record. We do not paraphrase ownership, company, or legal information. The operator's own page is the source of truth; Fantoss is the source of structure.

What to read after this guide

The reading order across the site is built around three passes. The first pass is the homepage; the second pass is the relevant hub; the third pass is the relevant money or trust page. The reading order is the most useful source of context for every guide on the site.

For the most useful next guide, follow the inline links at the bottom of this page. The links are part of the reading order; they are not filler. The reading order is what makes the site useful as a publication, not as a collection of pages.