DESK
How to reach the editorial desk
iplfantasyteam.com publishes editorial coverage of IPL fantasy cricket. The contact page is for corrections, source notes, methodology questions and editorial feedback. It is not for account recovery, payment disputes or customer-care enquiries about a third-party platform. Routing the right kind of message to the right place is the fastest way to get a useful response, because the desk can answer most correction requests within two business days and most other editorial questions within a week.
Where the enquiry is about a fantasy platform's product, account or payment, the platform's own customer-care channel is the right destination. The desk cannot recover a password, cannot see a wallet, cannot lift a withdrawal hold and cannot speak for a third-party operator. The desk can, however, help a reader frame a question to the right channel and, in some cases, publish a correction to its own copy where the desk's description was the source of the confusion.
What the desk responds to and what it does not
The desk responds to corrections, source notes and methodology questions. A correction request should include the page URL, the disputed wording, the better source and the date at which the change became apparent. A source note should include the URL of the primary source and the time at which the desk might reasonably cite it. A methodology question should ask about a specific page or a specific label, not about the desk in general.
The desk does not respond to account recovery requests, withdrawal disputes, KYC escalations, password resets, deposit holds or bonus disputes. These messages are routed back to the reader with a pointer to the relevant trust page. The reason is not indifference; it is that the desk has no way to resolve an account-level problem with a third-party platform, and pretending otherwise would slow down the corrections work that the desk can actually do.
How to send a correction request
The most useful correction request includes four things. First, the page URL or the URL of the article in question. Second, the disputed sentence or the passage that needs to change. Third, the wording the reader proposes as the corrected version, or a pointer to the source the reader thinks the desk has missed. Fourth, the date at which the change became apparent — the publication date of a squad update, for instance, or the time of a press conference the desk has not attended.
A correction request without these details still gets read, but the desk usually has to ask for them before the request can be acted on. The round-trip cost is small when the reader remembers the URL; it is large when the reader describes the page by feel. A reader who can copy the URL and the disputed sentence into a single message saves themselves a day and saves the desk an hour.
Response times and what to expect
The desk acknowledges most correction requests within two business days. The acknowledgement may be a short reply confirming receipt or asking for one more detail. The substantive answer follows once the desk has had time to read the source, compare it with the current copy and decide on the amendment. For methodology questions the reply is usually faster because the desk can point to an existing page or a label the reader has not seen.
On match days the desk prioritises corrections that affect a predicted XI, a venue reading or a player availability note. Other corrections are queued for the next quiet window. The queue is not a sign of disregard; it is the cost of having a small editorial desk. Where a correction matters for a payment or a support step, the desk recommends that the reader verify the relevant detail through the platform's own channel first and treat the desk's correction as supporting context, not as the deciding source.
Where the desk cannot help and what to do instead
The desk cannot help with account recovery. If a reader has lost access to a fantasy platform's account, the right channel is the platform's customer-care route, ideally reached through the platform's own domain. The desk cannot help with deposit or withdrawal disputes; those are also routed to the platform, and if the platform does not resolve them, the next step is the payment provider or the appropriate consumer forum.
The desk also cannot help with KYC escalations. KYC is performed by the platform and, where applicable, by its payment partner; the desk does not see identity documents, does not store them and cannot intervene on a reader's behalf. Where a reader has a complaint about how identity information was handled, the appropriate authorities are the platform's data-protection officer, the payment partner's data-protection officer and, in India, the relevant grievance officer under applicable rules.
| Topic | Where to take it | What to keep with you |
|---|---|---|
| Account recovery | The platform's customer-care channel, reached via the platform's own domain. | Use the platform's verified support route, not search results. |
| Withdrawal dispute | Platform customer-care first, then payment partner and consumer forum. | Keep the transaction ID and the date of the dispute. |
| KYC escalation | The platform's data-protection officer, then the relevant grievance authority. | Do not share identity documents over chat attachments. |
| Bonus or promo dispute | The platform's customer-care channel; refer to the offer T&Cs. | Capture the offer page at the time you applied the code. |
| Suspected scam | Stop using the suspected channel, change passwords from a clean device, report to the platform. | Do not try to recover money through the suspected channel. |
Confidentiality and what the desk does with a message
The desk keeps correction messages confidential by default. Where a correction is published, the desk usually does not name the reader who sent it unless the reader has asked to be credited. Source notes are handled the same way: the desk may publish a correction that mentions the source but does not name the reader who pointed at it. The reason is straightforward — a desk that names its sources discourages the next reader from sending one.
The desk does not sell, rent or trade reader messages. Where a correction requires the desk to keep a copy of the disputed copy and the source for a defined period, that copy is stored on the desk's own infrastructure and is deleted once the version history has been refreshed. The privacy notice on this site covers the data the desk holds; the contact page is not a separate policy.
Working with named sources and on-the-record comments
Where a reader wants to provide a tip, a leak or an on-the-record statement, the desk can agree on attribution before publication. The desk does not pay for tips; the desk does not promise outcomes; the desk does promise to read what the reader has sent. The desk's editorial position is that a tip is useful when the desk can verify it independently, and that verification is what the desk publishes, not the tip itself.
The desk can also accept anonymous tips where the reader has a legitimate reason for anonymity. An anonymous tip is treated as a starting point, not as a finding, and the desk will usually say so if a paragraph in an article began with an anonymous tip. The reader who sends the tip is not entitled to see how the desk used it; the desk's reporting is the desk's reporting. The two rules keep the newsroom honest in different directions.
Sending screenshots, documents and other attachments
A correction request can include a screenshot where the screenshot shows the disputed line in context. The desk prefers a URL to a screenshot where both are available, because a URL lets the desk see the page as it currently stands and the time it was last updated. A screenshot can be useful for a paragraph the desk has already corrected and wants to compare with the older version.
The desk does not accept attachments that contain identity documents, banking details or passwords, even when the attachment is offered in good faith. The desk's storage is not designed for sensitive personal data, and the desk would rather not hold it. A reader who wants to share a sensitive document is asked to summarise the relevant detail in plain text and to keep the original with the platform's data-protection officer.
A note on tone, abuse and patience
The desk is happy to receive strongly worded corrections. A correction request that disagrees with a desk position is welcome; a correction request that consists only of an insult is not actionable and the desk will not respond to it in kind. The desk's editorial position is that a polite disagreement is more useful than an angry agreement, because a polite disagreement usually carries the source the desk needs to revise.
The desk's patience is finite but not fragile. A reader who sends three corrections in a row and sees all three adopted is not owed a fourth correction in advance. A reader who sends a correction that turns out to be wrong is thanked for the effort and told why. The desk's relationship with its readers is built on the slow work of revisions that survive a second look, not on the fast work of replies that please everyone.
Reader questions
How quickly does the desk reply?
Can the desk recover my account?
Can I send a tip anonymously?
Will the desk name me if I send a correction?
Can I attach a screenshot?
What if my correction is wrong?
Continue with care
Send corrections with the page URL, the disputed wording, the proposed correction and a primary source where one is available. The desk acknowledges most messages within two business days.