TM TreeMA Customer Support

Support

Customer Support

TreeMA is still an early product. Support is scoped around the current public website, local app setup, workspace initialization, Vercel-hosted landing surface, and product clarification for the MVP.

1. What Support Covers

  • Problems opening the public site, legal pages, or landing routes.
  • Questions about how the local browser app, Electron shell, or CLI entrypoints are intended to work.
  • Questions about the current TreeMA MVP scope, public pages, and documentation.
  • Reports about broken links, incorrect copy, or deployment regressions on the hosted site.

2. What Support Does Not Guarantee

  • Custom implementation work inside your own repository, workspace, or third-party infrastructure.
  • Guaranteed turnaround times, SLA coverage, or always-on staffed support.
  • Recovery of locally stored files, credentials, or project state lost on your own machines.
  • Third-party provider issues outside TreeMA control, including GitHub, Vercel, OpenAI, or GitHub Copilot outages.

3. Best First Steps

Before reaching out, use the self-serve paths that already exist in the repository and public site.

  • Read the repository overview in README.md.
  • Check the product scope in docs/MVP_SPEC.md.
  • Review the repository map in docs/PROJECT_STRUCTURE.md.
  • Confirm whether the issue is happening on the public deployment, your local environment, or a third-party integration.

4. What To Include In A Support Request

If you contact TreeMA support, include enough concrete detail to reproduce the issue quickly.

  • The page or route involved, such as `/privacy`, `/terms`, `/landing`, or the local app surface.
  • Your environment, such as browser, operating system, or whether you are using the local server, Electron shell, or Vercel deployment.
  • The exact behavior you expected and the exact behavior you saw instead.
  • Any relevant error messages, screenshots, or reproduction steps.

5. Response Expectations

TreeMA does not currently publish formal service levels. Support is handled on a reasonable-effort basis for the current MVP. Priority is usually given to deployment breakage, route failures, critical public-site regressions, and issues that block the basic local product workflow.

6. Contact Path

Until a dedicated support mailbox or form is published, the primary support path is the source of the TreeMA distribution you are using. For the current public MVP surface, use the repository or published product channel where TreeMA was provided.

If you are using a hosted deployment tied to a custom domain, reference the exact URL in your message so the issue can be traced to the right environment.