> For the complete documentation index, see [llms.txt](/llms.txt).

If you've been through [Troubleshooting](/support/troubleshooting) and the [Known Limitations](/support/known-limitations) and you're still stuck, here's how to reach us and what to include.

## How to reach us

- **Email:** [hello@hardwarehunter.io](mailto:hello@hardwarehunter.io) — the fastest channel, and where account/billing issues get resolved.
- **X:** [@gethwhunter](https://x.com/gethwhunter) — good for quick questions and public signal.

There's no in-page chat widget right now. If you see one on an older page, it's legacy — use email instead.

## What to include in a report

The faster we can reproduce it, the faster we can fix it:

- **Account email** (or hunt name)
- **What you expected vs what happened**, in one or two sentences
- **Screenshots** if it's a display or UI issue
- **For alert problems:** which channel, and whether the channel's **Test** button worked
- **For scan problems:** which source and category, and whether other hunts are behaving

## What "it's broken" means to us

A few useful distinctions:

- A source being **down** (Reddit, ServerPartDeals, Best Buy, Newegg) is a known limitation, not a bug — see [Known Limitations](/support/known-limitations).
- A hunt returning **mostly SKIP** is usually criteria or pricing, not a fault — the verdict text says why.
- An alert **not arriving** is almost always a channel config issue — start with the channel **Test** button.
- The **API** returning an error is a bug — include the endpoint and the exact error body.

We don't run a public status page yet. If the site itself is unreachable, that's your fastest signal, and email is the way to tell us about it.