Contact Guru11 India: corrections, broken links, and tips
This page is the front door to the Guru11 India editorial inbox. The channel exists for corrections, broken-link reports, and tips about the Guru11 fantasy app. It does not exist for account recovery, payment disputes, or coupon redemptions on the reader's behalf. Read the scope below before writing, so the message lands in a queue the desk can actually answer.
The inbox in plain language
The Guru11 India inbox is one shared mailbox used by the editor and the reviewer named on the about page. Messages arrive in plain text, are read in the order they land, and are sorted into three internal folders within a working day. The first folder is for drift reports, where a reader points out that an operator page has moved since the hub was last re-read. The second folder is for new tips, where a reader has noticed a change in the app itself. The third folder is for everything outside the editorial scope, which receives a short pointer back to the operator's support routes or to the responsible-play hub.
Because the inbox is small, the desk does not run a ticket system, a chat widget, or a phone line. There is no live agent, no queue position number, and no estimate of when a reply will arrive beyond the "few working days" baseline that appears on every hub page. The shape of the inbox is the shape of the desk: two people, one shared mailbox, a single weekly re-read cycle, and a refusal to grow the operation into something the funding model could not support.
The inbox is monitored twice a day, and the response time is usually within 24-48 hours. The inbox is not monitored on weekends, which means a message sent on Friday evening will get a response on Monday or Tuesday. The response time is published in the contact page header, and the response time is the baseline for any escalation. A response that takes longer than the published window is a sign that the message was lost or filtered, and the player should follow up with a second message.
What the channel handles
The channel handles three kinds of message. A correction is a note that a specific claim on a Guru11 India page no longer matches the operator's public terms. A broken-link report is a note that an outbound link on a Guru11 India hub no longer resolves to the page it pointed to. A tip is a note that something inside the Guru11 app has changed in a way the hubs have not yet caught, such as a new offer wording, a new deposit method, or a new responsible-play message inside the app itself.
The desk verifies each of those three kinds against the operator's published page before changing anything. Corrections ship as dated updates with a brief credit line. Broken-link reports ship as silent fixes on the affected hub, with the credit line visible only in the editorial changelog. Tips ship as a new section on the relevant hub once the operator has confirmed the change, with the same credit-line convention. The cycle from report to update is rarely shorter than two working days, and is sometimes longer when the operator's own page is slow to load.
The channel handles: factual errors in published content, broken links, outdated screenshots, missing information on a specific topic, and editorial suggestions for new posts. The channel does not handle: account-specific support issues, payment disputes, login problems, or any topic that requires access to the player's account. The split is intentional - editorial coverage and operator support are different functions, and the channel is set up to handle one and not the other.
What the channel does not handle
The channel does not handle account recovery. If a reader is locked out of a Guru11 account, has lost access to the phone number on file, or has had a session expire in a way the app does not resolve, the operator's published support route is the right path. The desk does not have the operator's backend tools, does not have the ability to verify identity on the reader's behalf, and cannot issue a temporary password or a one-time unlock code.
The channel does not handle payment disputes. If a UPI debit has hit the reader's bank statement but the deposit has not landed in the operator's wallet, if a withdrawal has been pending for longer than the published window, or if a bonus has been clawed back without an explanation in the reader's account history, the operator's customer-care line is the right path. The desk can explain the kind of record the operator usually asks for, but the desk cannot intervene once the operator's queue has the file.
The channel does not handle coupon or referral redemptions. If a coupon code the reader typed into the field did not unlock the bonus the reader expected, if a referral link did not attribute the new account, or if a welcome bonus has been voided with a server-side note the reader cannot see, the operator's support ticket is the right path. The desk cannot see the reader's account state, cannot see which server-side rule voided the bonus, and cannot override the operator's bonus logic from outside the app.
The channel does not handle: account-specific support issues (use the operator's support channel), payment disputes (use the operator's support channel first, then the bank's dispute resolution), login problems (use the operator's support channel), or any topic that requires access to the player's account. The split is intentional because the editorial team doesn't have access to the operator's account systems, and the operator's support team doesn't have editorial authority over the published content.
What to leave out of a message
The channel does not need personal documents to act on a correction or a tip. Readers should redact phone numbers, UPI handles, account numbers, Aadhaar numbers, PAN numbers, and one-time passwords before attaching any image. The desk will not open attachments that contain any of those, and the desk will not respond to messages that ask for help bypassing an OTP or a password reset on the reader's behalf. The channel is editorial, not operational, and the boundary is what keeps the desk small enough to read every message.
The channel also cannot accept attachments that contain a forwarded APK file, a copied install prompt from an unofficial store, or a screen recording of the operator's KYC step. Those items are useful for the operator's security team, not for the editorial inbox, and the desk forwards those messages to the operator only when the reader has given explicit written consent to do so. Without that consent, the desk replies with a pointer to the operator's published security reporting route.
The message should not include: the player's account password, the player's OTP, the player's UPI PIN, the player's PAN number, the player's Aadhaar number, or any other sensitive personal information. The channel is monitored by the editorial team, not by the operator, and the editorial team does not need any of this information to handle editorial issues. A message that includes sensitive information is a security risk, and the editorial team will delete the sensitive parts before processing the message.
How to write a useful correction
A useful correction includes the URL of the Guru11 India page the reader was on, the section or paragraph the reader was reading, and a short description of what changed. A short description reads better when it is one sentence: "The minimum deposit on the coupon hub reads ₹100 but the operator's page now says ₹200." That sentence is enough for the desk to verify, update, and credit. A longer description is fine if the change is structural, but the desk prefers a single sentence to a paragraph when the change is small.
For payment corrections, the message should include the date of the transaction, the payment method used (UPI, wallet, net-banking, or card), the amount, and any reference number visible in the operator's app or in the SMS or email the operator sent. The reference number is enough; the reader's full bank statement is not needed and should not be attached. The desk verifies against the operator's public terms, not against the reader's account, so the public record is the source the desk works from.
For offer corrections, the message should include the exact wording the reader saw, where it was shown (in-app banner, push notification, group chat, creator reel), and the date. Screenshots are useful when the wording is unusual, but the desk prefers a text quote over a screenshot when both are available, because text quotes are easier to compare against the operator's published terms in a verification pass.
A useful correction includes: the URL of the page with the error, the specific sentence or paragraph that's wrong, the source of the correct information, and a screenshot if the error is visual. The URL and the specific sentence are the most important parts - without them, the editorial team has to spend time hunting for the error, and the hunting is the delay that turns a same-day fix into a multi-day fix. The source of the correct information is the second most important part, because the editorial team needs to verify the correction before publishing it.
How the desk handles personal data in messages
The desk does not need personal data to act on a correction, and the desk never asks for an OTP, a password, an Aadhaar image, a PAN image, or a card number. The reader can describe what changed without sharing any of those. Where a reference number is needed, the operator's own reference is enough. The privacy policy explains how the channel treats server logs, and the inbox workflow is reviewed alongside the policy so the two documents stay aligned.
Emails sent to the contact channel are read by the editor and the reviewer only. They are not shared with the Guru11 operator, with a marketing partner, or with a third-party service. If the desk forwards a message to the operator's security team, the forwarding happens with the reader's explicit consent, and the original email is deleted from the editorial inbox once the forwarded copy has been confirmed as received by the operator.
The desk handles personal data in messages according to the privacy policy, which is published in the footer of every page. The data is used only to process the message, and the data is deleted after the message is processed. The data is not shared with the operator, with any third party, or with any other channel. The data retention period is 30 days, and the data is deleted automatically after 30 days. The deletion is verified by a monthly audit, and the audit results are published in the editorial page.
Operator support routes for account and payment issues
For account, deposit, bonus, or withdrawal issues that only the Guru11 operator can resolve, the operator's published support routes are the right starting point. Most fantasy apps in India publish a help section inside the app, a help page on the operator's main site, and a customer-care phone or email line. The payment gateway hub lists the kind of record a reader should keep before raising a support ticket, so the operator has the detail it needs to act quickly rather than asking for another screenshot.
When a support ticket is open with the operator, the reader should keep every message, reference number, and screenshot. The payment gateway hub explains how long a typical UPI refund takes, why a wallet hold can last a few working days, and when a bank dispute is the right next step. The desk does not act on a reader's behalf with the operator, but the hub is written so a reader can speak to the operator with the right context already in hand.
The operator's support routes are: the in-app help section, the operator's website support page, the operator's email support, and the operator's phone support. The in-app help section is the fastest for most issues because the help section has access to the player's account context. The email support is the slowest but is the right path for issues that require attachments or detailed descriptions. The phone support is the right path for urgent issues that can't wait for the email response.
Press, partnership, and legal enquiries
Press enquiries, partnership enquiries, and legal notices should be sent by email with a clear subject line. Legal notices are forwarded to the address listed in the terms of use. The desk does not accept guest posts, paid links, or sponsored placements, and the desk does not reply to messages that ask the editorial pages to publish a promotional line for the Guru11 app. That refusal is part of the editorial principles on the about page and is not negotiable through the contact channel.
If a message describes an inaccuracy that has caused a reader real harm, the message should include the Guru11 India page URL, the date the reader read the page, and a short description of the impact. The desk reviews harm reports separately from general corrections and replies with a timeline. Harm reports are not mixed with general editorial inbox traffic, and the review of a harm report includes the reviewer as a second reader before any reply is sent.
Press, partnership, and legal enquiries are handled through a separate channel that's published in the editorial page. The channel is monitored by the editorial lead, and the response time is usually within 48-72 hours. The channel is the right path for any enquiry that requires a formal response, and the channel is not the right path for routine editorial issues. The split is intentional because the formal enquiries need a different tone and a different review process.
Response times and what to expect
The desk reads messages in the order they arrive and replies when the topic fits the editorial scope. A typical reply window is a few working days, though it can stretch longer when the desk is verifying against the operator's published terms or when the operator's own page is slow to load. The desk does not run a chat channel and does not reply outside working hours, so a reader who needs an urgent answer on a payment step should still raise a ticket with the operator first rather than waiting on the editorial inbox.
Where the desk cannot help, the reply says so. Where the desk can help, the reply includes the next step and, where relevant, the page the desk is going to update. The desk treats every correction as a chance to make the Guru11 India hubs a little more accurate, and the contact channel is the main way that improvement happens. A reader who writes in is shaping the next version of the site, and the reply will usually show what changed because of the report.
The response time is published in the contact page header, and the response time is the baseline for any escalation. The response time varies by message type: editorial issues are usually within 24-48 hours, formal enquiries are usually within 48-72 hours, and operator-specific issues are redirected to the operator's support channel. The response time is a commitment, not a guarantee, and the editorial team holds itself to the commitment but acknowledges that occasional delays are unavoidable.
How to escalate when the channel isn't responsive
If the contact channel hasn't responded within the published response window, the player can escalate through the operator's support channel, the bank's dispute resolution mechanism (for payment-related issues), or the consumer court (for material disputes). The escalation paths are published in the operator's help centre, and the player should know the escalation paths before they need them, not after. The cost of knowing the paths is a 5-minute read; the cost of not knowing them is a potentially permanent unresolved issue.
The escalation path that is most often effective is the bank's dispute resolution mechanism, because the bank is the regulated entity that holds the funds during the dispute. The bank's dispute team has the authority to reverse a transaction, and the reversal is usually faster than the operator's support flow. The bank's dispute flow is initiated through the bank's customer support, and the bank's customer support is available 24/7 through the bank's app, website, or phone banking.
The escalation path that is least often effective is the consumer court, because the consumer court process is slow and the dispute amounts in fantasy sports are usually below the threshold for a meaningful court case. The consumer court is the right path for material disputes - large financial losses, repeated fraud, systematic non-resolution - but it's not the right path for routine support issues. The player should reserve the consumer court for the disputes that can't be resolved through any other path.