Contact the bigbaazi editorial desk.

Editorial desk.

The editorial desk reads everything sent to it. We are particularly interested in:

• Corrections to published material.
• Story tips that are verified and within our scope.
• Accessibility feedback on the site or the reader.

Corrections policy.

Corrections are published on the affected page with a dated correction note at the bottom of the page. Material corrections are also reflected in the next scheduled update. We do not silently edit published material.

What this desk does not handle.

• Customer-care or KYC issues — those belong to the platform support team.
• Account disputes, withdrawal problems or verification rejections.
• Bonus claims or referral disputes.
• Anything outside the editorial scope of this reader.

For those, the right contact is on the customer-care page.

Routing your message to the right desk.

The most common reason a message gets a slow reply is that the message is routed to a desk that does not handle the topic. The editorial desk here handles three kinds of outreach — editorial corrections, press or partnership enquiries, and reader feedback on the published content. The desk does not handle account support, withdrawal disputes, KYC escalations, or any issue that requires access to a player's account. Routing matters; the right message reaches the right desk faster.

• Editorial corrections. A correction request should include the article URL, the paragraph or the claim, the primary source that contradicts the claim, and a contact email. A correction request that does not include a primary source is treated as a comment, not a correction, and may be acknowledged without changing the article.
• Press and partnership enquiries. A press enquiry should include the publication, the deadline, the topic, and any specific question. A partnership enquiry should include the partner's role, the proposed scope, and the contact details of the decision-maker. The desk responds to both within the working week.
• Reader feedback on the published content. A reader comment, a question about a published article, or a suggestion for a future article is welcome. The desk reads every feedback message and may publish a response on the article, may reply by email, or may use the feedback to inform a future article.
• Topics the desk does not handle. Account support, withdrawal disputes, KYC escalations, and any topic that requires access to a player's account are handled by the platform's customer-care team, not by the editorial desk. The contact page on the operator's verified route is the right place for these. Sending the message to the editorial desk adds a hop and slows the reply.

What the desk does with the message.

Every message is read by a human within the working week. The reply is a real reply, not a templated acknowledgement. The reply may include a follow-up question, an editorial decision, or a redirect to a more relevant desk. The decision to publish a correction, the decision to publish a response, and the decision to revise a future article are all made by the editorial desk, not by an automated system.

The desk does not sell or share the contact list with any third party. The contact details are used only to reply to the message, to follow up on the topic if the reader has asked for follow-up, and to inform the editorial calendar if the message is a suggestion. The desk's privacy position is the same as the site's privacy policy, and the privacy policy is published in plain language on the privacy page.

Working hours, response windows, and the slower routes.

The desk operates on Indian Standard Time, weekdays, with the working week running Monday through Friday. The reply window for routine messages is the working week. The reply window for correction requests is shorter when the primary source is provided with the original message. The reply window for press enquiries is the working day when the deadline is the same day, and the working week when the deadline is longer.

The slower routes are the ones that should be on the reader's list as well. A platform support issue that has not been resolved through the platform's customer-care route can be escalated to the platform's regulator or to the card-issuing bank's dispute team. The editorial desk cannot do that escalation on the reader's behalf, but the editorial desk can publish a clear pointer to the relevant routes in the platform review.

The slowest route is the one that does not exist. A message sent to an unverified email, a chat widget on a cloned site, or a forwarded handle is a message that does not reach the editorial desk. The safest habit is to use the contact channel published on the verified domain, and to verify the sender before replying to any reply that claims to be from the desk. The reply should come from the same domain the original message was sent to; a reply from a different domain is a signal to pause.

Response windows, weekly notes, and the archived Q&A.

The desk publishes a weekly note that summarises the desk's editorial work, the corrections published, the platform reviews updated, and the policy notes that have appeared on the news desk. The weekly note is the cheapest way to keep up with the desk's work without checking the publication feed daily. The note is published on the same domain as the desk's articles, with the same editorial line, and with the same dated correction policy that applies to the rest of the desk's content.

The desk also publishes an archived Q&A for the most common editorial questions. The Q&A covers the topics that come up most often in the feedback inbox: the editorial line, the affiliate relationships, the platform-review process, the verification of the news notes, the responsible-play chapter, and the desk's editorial independence. The Q&A is a living document; the desk updates it whenever a new question becomes common enough to be worth publishing. The honest read is to check the Q&A before sending a feedback message; the answer is often already published.

How the desk handles corrections that arrive through the contact form.

A correction request that arrives through the contact form is treated as a publishable input. The desk reads the request, the primary source, the article URL, and the specific claim. If the primary source is verifiable, the desk publishes the correction within the working week, with a dated correction note at the top or bottom of the affected article. The reader who sent the correction is acknowledged by name if the reader has consented to the acknowledgement; otherwise, the correction is published without naming the reader.

A correction request that does not include a primary source is treated as a comment, not a correction. The desk may acknowledge the comment, may reply by email, and may use the comment to inform a future article. The desk does not publish the comment as a correction unless the primary source is verifiable. The honest read is that the desk's correction policy is the same as the desk's editorial policy: the source is the source, the date is the date, and the publication is the publication.

What the desk does with the contact list.

The desk does not sell or share the contact list with any third party. The contact details are used only to reply to the message, to follow up on the topic if the reader has asked for follow-up, and to inform the editorial calendar if the message is a suggestion. The desk's privacy position is the same as the site's privacy policy, and the privacy policy is published in plain language on the privacy page.

The desk does not add the reader to a marketing list without explicit consent. The desk's weekly note is published on the site, not sent by email, and the reader who wants the weekly note is invited to subscribe through the subscription form on the homepage. The subscription form is a real subscription form — the reader can unsubscribe at any time, and the unsubscribe link is in every email the desk sends. The honest habit is to treat the contact list as a list of readers who have chosen to be on the list, not as a list of targets the desk has assembled.

The slower route — when the desk is not the right desk.

The desk is not the right desk for several kinds of messages. Account support, withdrawal disputes, KYC escalations, and any topic that requires access to a player's account are handled by the platform's customer-care team, not by the editorial desk. The platform's contact page on the verified route is the right place for these. The editorial desk does not have access to player accounts and cannot act on messages that require access.

The desk is also not the right desk for legal advice, tax advice, or financial advice. The desk's editorial position is to publish what is known, flag what is unclear, and direct the reader to a qualified professional for the specific case. The reader's own legal, tax, and financial position is the reader's own, and the desk's role is to give the reader the best information available at the time of the read, not to replace the reader's qualified professional.

The slowest route is the one that does not exist. A message sent to an unverified email, a chat widget on a cloned site, or a forwarded handle is a message that does not reach the editorial desk. The safest habit is to use the contact channel published on the verified domain, and to verify the sender before replying to any reply that claims to be from the desk. The reply should come from the same domain the original message was sent to; a reply from a different domain is a signal to pause.