Support
Find the support route and prepare a useful issue report.
Choose a channel
Sign in and open Support. The Help desk is for product questions, Feature suggestions is for ideas, and Announcements is for team updates. Only staff can start announcement threads. Use New thread where available, choose a category and describe the issue. Threads are visible to signed-in members, so keep confidential material out of them. If the service is unavailable, use the contact details on the company page.
Find a relevant thread
Filter the loaded list by tag or status, search titles, authors and tags, and sort by newest or most active. Load more threads to inspect older entries. Tags cover topics such as Account & clubs, Readings & tokens, Billing, API & MCP and Bug, plus workflow labels such as Known issue or Planned. A Planned tag is not a release commitment, and an empty filtered list is not evidence that no issue exists.
Answers and resolution
Threads can be Open, Answered or Resolved. Team answered marks a staff response, and staff replies are labelled MoatDefender team. Use Mark resolved or Reopen only when the control is available to you; the thread retains resolution history. A team response or a resolved status describes the support conversation, not independent verification of a company's evidence or investment quality.
Include useful context
Describe the action, expected result and what appeared. Include the URL, approximate time and exact error. For readings, provide the identifier and date instead of a confidential deck. Remove passwords, API keys, private share tokens and unnecessary personal information from screenshots.
Check the right source
For payment availability and token balances, start with pricing and your ledger. For an incorrect fact in a reading, identify the source and the correction you can substantiate. An unavailable page, a missing report and a measured zero mean different things, so preserve the wording you saw.