Reader Feedback
Feedback is one of TickStock's editorial inputs. This page describes how to send substantive feedback and what readers can expect when they do.
Last updated 22 May 2026
How to Send Feedback
Direct contact routes by category:
- Editorial feedback — coverage choices, story suggestions, framing concerns, missing context: editorial@tickstock.io.
- Corrections — factual errors, misattributed quotes, figures or claims you can show are wrong: corrections@tickstock.io. See the full corrections policy.
- Confidential tips — material we should look at, on confidential terms: tips@tickstock.io. See the sources policy.
- Platform issues — technical problems with the site or app: platform@tickstock.io.
What Readers Can Expect
- Acknowledgement. Substantive emails get a real reply, not an autoresponder. We aim for a working-day response on most editorial feedback, and within 24 hours on corrections.
- Substantive engagement. Where feedback raises a legitimate point, we engage with the substance, not just the form of it. Where we disagree with feedback, we explain why.
- No defensive posture. Readers raising fair points about our coverage are not adversaries. Defensive or dismissive replies are not how we want to operate.
What We Do With Feedback
Feedback isn't only about the email it arrives in. It feeds into:
- Per-article action. Errors get corrected; framing issues get reviewed; missing context gets added.
- Editorial standards iteration. Patterns in feedback inform updates to systems, the style guide, and our prompt library.
- Coverage planning. Reader requests for coverage of specific issuers, sectors, or themes are recorded and considered in editorial planning.
What We Will Not Engage With
- Demands to remove or alter accurate, fairly-reported coverage on the basis that the coverage subject didn't like it
- Sustained abusive or threatening communication — we reserve the right to disengage and, where warranted, escalate
- Off-the-record commercial pitches dressed up as editorial feedback
- Anonymous tips that don't meet the sourcing bar set out in the sources policy
Escalation
If feedback isn't resolved through the editorial team and the reader believes a substantive issue remains, escalation goes to the publisher: publisher@tickstock.io. The publisher reviews substantive escalations personally.
Contact
All routes above; the catch-all is editorial@tickstock.io.