A reader's three ways to reach the editorial desk, in the order the desk recommends

Message 1: a reader question for the news pages. The reader-question column is the most useful place to send a question that other readers would also benefit from. The desk picks one question a week and answers it in the column. The question is read in full, but the desk does not name the reader.

Message 2: a correction, clarification or update. If the reader spots a factual error, an out-of-date link, or a missing piece of context, the desk treats the message as a correction request. The desk reads the request, verifies the correction against the desk's sources, and publishes an update note at the top of the affected article. The reader does not need to identify themselves.

Message 3: a commercial or partnership inquiry. Commercial and partnership inquiries are handled by the desk's commercial team, not by the editorial desk. The desk does not mix commercial and editorial conversations. A commercial inquiry is forwarded to the commercial team and answered inside one business day.

The desk does not handle individual account queries. A reader with a stuck withdrawal, a KYC question, or a bonus query should contact the platform's support line, not the desk. The desk is an editorial guide, not a support channel.

The desk reads every message. The desk does not promise to reply to every message, but the desk does promise to read every message that arrives. The desk's typical response time is one to three business days, longer during the monthly update cycle.

The desk does not sell message data. The desk does not share message data with third parties beyond what is required to run the contact form. The desk deletes message data after the conversation is closed, in line with the privacy policy.

The desk is small. A small team reads every message; a small team writes every response. The desk's size is a feature, not a bug, because it means the desk reads what the desk publishes. The desk writes about the same things the desk hears about.

First: did the desk receive the message? The desk's contact form sends a confirmation. The reader checks the confirmation. A missing confirmation is a flag the reader should report.

Second: did the desk understand the question? The desk's response is short, in plain language, and refers to the source material the desk has read. The reader checks the response for accuracy. An inaccurate response is a flag the reader should report.

Third: did the desk act on the question? The desk's editorial work is published on the news pages, the strategy pages, or the responsible-play pages. The reader checks the relevant page. A missing publication is a flag the reader should report.

The reader does not expect an instant reply. The desk's typical response time is one to three business days, longer during the monthly update cycle. The reader waits the published timeline before following up.

The reader does not send the same message twice. A duplicate message is a noise signal. The desk deduplicates messages; the reader does not need to. The reader trusts the desk's deduplication.

The reader does not use the contact form for account support. A stuck withdrawal, a KYC question, or a bonus query belongs to the platform's support line, not the desk. The desk is an editorial guide, not a support channel.

A short subject line in five words or fewer.

A clear opening sentence stating what the message is about.

A specific question or request, not a multi-question message.

A note on the source material with the article title and URL.

A note on the reader role (new reader, regular reader, platform reviewer).

A polite closing such as thank you or best regards.

A paper trail in a dedicated folder for the message and the response.

A note on the response window: one to three business days, longer during the monthly update cycle.

When the desk receives a reader question, the desk reads the question in full before responding. The desk does not skim. The desk treats the question as a working question, not a one-line prompt. The desk's response addresses every point in the question, in the order the reader raised them.

When the desk receives a correction request, the desk verifies the correction against the desk's sources. The desk does not assume the correction is right; the desk reads the source material and confirms. If the correction is right, the desk publishes a correction note at the top of the affected article.

When the desk receives a commercial inquiry, the desk forwards the inquiry to the commercial team. The desk does not mix commercial and editorial conversations. The commercial team answers inside one business day.

When the desk receives a question that belongs to the platform, the desk redirects the question to the platform's support line. The desk is an editorial guide, not a support channel. The platform's support line is the right place for individual account queries.

When the desk receives a question that the desk cannot answer, the desk says so in the same paragraph, not in a footnote. The desk is honest about the limits of what the desk can verify. The desk does not pretend to know what the desk does not know.

When the desk receives a question that requires a long response, the desk writes a long response. The desk does not trim a long response to a short one. The desk treats the question as a working question, and the response as a working response.

When the desk receives a question that requires a source citation, the desk includes the source citation. The desk does not paraphrase a source without attribution. The desk does not invent a source.

When the desk receives a question that requires an update, the desk publishes the update. The desk does not bury the update in a footnote. The desk publishes the update at the top of the affected article, with a visible date.

A reader who wants to read more about the desk's response playbook can read the desk's about page. The about page lists the editorial calendar, the changelog, and the desk's contact form. The reader can also submit a question for the reader-question column through the contact form.

A reader who wants to read more about the platform's support playbook can read the customer-care page. The customer-care page lists the in-app chat, the email, the phone, and the regulator. The reader uses the platform's support line for individual account queries, not the desk.