Contact the 11Tiger editorial desk
How to reach the desk for editorial submissions, corrections, partnership queries, and the public editor line.
A contact page that lists every channel the desk actually monitors and how to use each one. The desk reads every submission but cannot promise individual replies on every channel.
Channels the desk monitors
The desk monitors four named channels: an editorial inbox, a corrections email, a public editor line, and a submissions portal. Each has a stated purpose and a stated response window.
The editorial inbox is for reader questions that may turn into a published answer on the relevant page. The corrections email is for “you got X wrong” messages, with an expected 48-hour review. The public editor line is a published weekly note on what changed and why. The submissions portal accepts brand submissions for the review pages only; submissions for any other page route to the editorial inbox instead, where they are triaged against the topic.
Response windows and what to expect
How to send a useful submission
The desk reads every submission. Three things make a submission more likely to produce a published answer or correction: a stated source, a stated context (which page, which event), and a proposed reading. Submissions that lack any of those three are responded to, but the response is usually a request for the missing piece rather than a publication.
The desk will not publish a submission that names another reader, a platform’s user, or a specific contest entry. The desk will publish a method-level comment about a contest structure, but not the names attached. Anything that smells like disclosure of a real-money outcome on a specific entry is referred back to the platform’s own dispute channel, with a published note that the desk did not publish the underlying claim.
What the desk does not respond to
🚫 Refunds and disputes
Refund and dispute resolution belongs to the platform’s own support channel and the partner brand’s terms page. The desk redirects rather than handling.
🚫 Brand-only stories
Submissions that promote a single brand without an editorially relevant comparison are routed to the submissions portal, not the editorial inbox.
🚫 Vague complaints
A complaint without a named page, a quoted passage, or a stated source receives a request for the missing context rather than a published answer.
🚫 Out-of-jurisdiction requests
Legal-advice requests are out of scope. The desk publishes legal reading notes that link to authoritative sources, and the reader’s own due-diligence remains the reader’s responsibility.
Frequently asked questions
Does the desk reply to every email?
The desk reads every email. Replies are routed by purpose — corrections, submissions, editorial inbox — and the reply window varies by channel.
Where do brand submissions go?
Brand submissions for review pages go to the submissions portal. Submissions for any other page are triaged into the editorial inbox.
Can I send an anonymous tip?
Yes. Tips on the public editor line can be sent anonymously. Tips that name another reader or a specific contest entry are not published.
How are disputes resolved?
Disputed facts are logged on the relevant page’s unknowns list and reviewed on the corrections cadence (48 hours).
Where do partnership and affiliate queries go?
Partnership and affiliate queries go to the channel listed on the contact page and are routed to the desk’s business manager. Editorial decisions stay separate.
Continue reading
Reading checklist
A working checklist for the reader who lands on this page to file a submission. The contact page lists every channel the desk monitors; the checklist is a quick way to pick the right channel without re-reading the entire page.
Three questions to ask before sending. Which channel best matches the question: corrections email, editorial inbox, public editor line, or submissions portal? What response window applies to that channel? What supporting material is required for the desk to action the request on the first pass?
What the desk does well. The contact page lists each channel alongside its response window. The submissions portal routes submissions for review pages only; submissions for any other page route to the editorial inbox instead, where they are triaged against the topic.
What the desk is still working on. A public editor line that runs faster than weekly on corrections escalations. A corrections email auto-responder that confirms receipt within an hour.
A reading cadence the desk recommends. Read the contact page once on a quiet afternoon. Re-read the response-window table whenever the desk announces a change to a channel’s cadence.
Desk note: how to read the desk’s response-window table
The response-window table on this page is grounded in a median across the desk’s last 30 tests per channel. The table is updated whenever the median shifts by more than a stated margin, and the change is announced on the news desk.
A reader who lands on this page to file a submission should read the table first. The channel the reader chooses determines the response window the desk publishes, and the submission’s format should match the channel’s purpose. A reader who files a KYC question through in-app chat is queuing the question in front of a first-line agent who cannot action it; the median time-to-first-reply on in-app chat does not apply to that case.
Three habits produce the strongest tickets. Lead the ticket with a reference number, where the platform has issued one. Attach a clear screenshot of the error or the affected screen, with edges visible. Include a short time-stamped journal of what the reader did before the issue surfaced. A calm one-line re-state of what the reader expects closes the ticket well; a frustrated re-state reduces the chance of a useful reply.
The desk’s reviews of the response-window table are the data the desk trusts. A reader who has a different experience from the published median is welcome to send the corrections email; the desk reads every email and the next review reflects reader-submitted evidence on the dimension score.
Limits of the contact channel
The contact channel is not a substitute for the partner brand’s own support. Refund, dispute and platform-policy questions route to the partner brand’s support and to the consumer-dispute forum named on the platform’s terms page.
The contact channel is not the right channel for legal advice, tax advice or financial planning. The desk publishes what is verifiable from public records and links to authoritative sources; the reader’s own counsel and accountant remain the reader’s responsibility.
The contact channel is not a hot-line for live-fixture escalations. A reader who needs an answer within the fixture window should contact the platform’s in-app chat or phone helpline; the desk’s contact page is not monitored at that cadence.
Caveats on the contact page
Three caveats the desk publishes on the contact page. The contact channel is a desk channel, not a partner-brand-controlled channel; the partner brand’s own support remains the primary route for refund, dispute and platform-policy questions.
The second caveat: the desk does not have visibility into the partner brand’s internal support queue. The response-window table on this page is grounded in tests the desk files in the open; a reader’s experience on a specific ticket may differ from the published median.
The third caveat: the desk’s contact channel is not monitored at the cadence of a live-fixture escalation. A reader who needs an answer within a fixture window should contact the partner’s in-app chat or phone helpline; the desk’s contact page is monitored on the stated response window.
A reader who has found a discrepancy between the desk’s published channel and the partner’s published channel is welcome to send the corrections email; the next contact-page refresh reflects reader-submitted evidence on the relevant channel.
Closing note from the desk
The contact desk closes its read with a note on the response-window table. The table is grounded in the desk’s last 30 tests per channel; the table is updated whenever the median shifts by more than a stated margin and the change is announced on the news desk.
The four channels the desk monitors are an editorial inbox, a corrections email, a public editor line and a submissions portal. Each channel has a stated purpose and a stated response window.
The desk’s submission policy is published on this page. The editorial inbox is for reader questions. The corrections email is for “you got X wrong” messages. The public editor line is a published weekly note on what changed and why. The submissions portal accepts brand submissions for the review pages only.
Where the reader wants to escalate a privacy request beyond the desk’s published channels, the reader’s own counsel and the appropriate data-protection authority in the reader’s jurisdiction are the authoritative route. The desk does not act as the reader’s proxy.
The desk’s miss record on the contact page is published alongside the channel table. A reader who has a different experience from the published median is welcome to send the corrections email; the next refresh reflects reader-submitted evidence.