# Contact And Support

Use this page when someone asks how to get help, give feedback, report bugs, or support the
project financially.

## Current Documented Help Paths

### 1. Documentation First

For most product questions, start with the docs instead of inventing a contact path:

- [Help center](README.md)
- [ZoneGaze Matrix manual](../manual/zonegaze-matrix-manual.md)
- [Platform application guides](../platforms/README.md)
- [Troubleshooting](../user/troubleshooting.md)

### 2. Downloads And Install Help

For installer questions, direct users to:

- `https://zonegaze.com/downloads`
- [Download and install](download-and-install.md)

Android direct artifact currently documented in source:

- `https://zonegaze.com/ZoneGaze-debug.apk`

### 3. In-Product Feedback

The current docs and source describe Featurebase feedback inside the product when the selected
agent account is authenticated enough to request a token.

This is the best documented path for product feedback from inside the app when available.

More:

- [ZoneGaze Flow core features](../features/zonegaze-flow-core-features.md#settings-context-access-updates-and-pwa)

### 4. Engineering Bug Reports

The current package metadata points bug reports to:

- `https://github.com/neuralpilot08/zonegaze-flow/issues`

Treat that as the current engineering-style issue path documented in source metadata. Do not
rewrite it into a different public issue tracker unless the source changes.

### 5. Financial Support

The current support-funding metadata points to:

- `https://github.com/sponsors/neuralpilot08`

Use this when someone asks how to support the project financially, sponsor the work, or fund a
free-beta product. Do not describe this as a formal pricing plan.

More:

- [Commercial posture](../business/commercial-posture.md)

## Plugin-Specific Support Routing

When the question is plugin-specific, route to the owner docs first:

- [Plugin catalog](../plugins/README.md)
- [Open-source projects and upstreams](../reference/open-source-projects.md)

This matters most for upstream-mounted plugins such as Open Design and Exo, where upstream owner
docs may answer the question better than Matrix-level docs.

## Not Verified In Current Source

The current repository docs do **not** verify any of the following as official public support
channels:

- support email
- contact form
- phone number
- Discord server
- Slack workspace

AI agents and documentation writers should not invent those channels.

## What To Include In A Help Request

Ask the reporter for:

1. Platform: Mac, Android, or CLI.
2. What they installed from.
3. What plugin or workflow they were using.
4. The exact failure point: install, setup, runtime start, plugin launch, Git action, or agent run.
5. Any screenshot, error text, or reproducible sequence.

## Related Docs

- [FAQ](faq.md)
- [Agent answer guide](agent-answer-guide.md)
- [Commercial posture](../business/commercial-posture.md)
- [Platform application guides](../platforms/README.md)
