How Support Works

How Support Works


MOODS Support exists to help with the product itself.


This inbox is used for:

  • bugs and technical issues
  • account and access problems
  • operational questions about how the tool functions

Support is focused on keeping the system working as intended.

What Support Is Not For


Support does not provide:

  • interpretation of sessions
  • explanation or debate of archetype responses
  • philosophical or personal guidance
  • crisis support

Those conversations are outside the scope of this inbox.

How to Get Help Efficiently


Clear information helps us respond effectively.


If you’re reporting a bug, include:

  • your device and browser
  • what you clicked
  • what you expected to happen
  • what happened instead
  • screenshots, if possible

If you’re having an account issue, include:

  • the email you used to sign in
  • the exact error message you’re seeing

If you’re sharing feedback, keep it brief and specific, and include what you were trying to do in the tool.

How Responses Work


Support is handled by email. There is no real-time chat. Response time varies. Not every message requires a detailed reply. Some questions are best answered by pointing to existing documentation rather than continuing a back-and-forth.

The Role of the Support Codex


The MOODS Support Codex is the primary reference for common questions.


If your question is covered there, support will reply with a link to the relevant article. This is intentional and part of how the system is designed to work.

Closing


MOODS is built for direct exploration.

Support exists to help with the mechanics, not the meaning.

Related Documentation


If you’re unsure what support can help with, where boundaries are set, or when MOODS isn’t the right place to reach out, these pages clarify the scope:


Related Articles