> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sitespy.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting Support

> Send a support request with the context needed to answer it

The [Support page](https://sitespy.app/dashboard/support) is the fastest way to reach a person. A failing watch also links straight to it — **Get help with this watch** opens the form with that watch already selected.

## What the form asks

* **What's this about?** — one of: a watch isn't detecting changes, too many or irrelevant alerts, notifications aren't arriving, a watch shows an error, filters or selectors aren't working, billing or refunds, account and API keys, a feature request, or something else
* **Which watch?** — pick the affected watch, so we can look at its actual history rather than guessing
* **Email, subject, and message** — your reply address and the description
* **How urgent is it?** — Question, Something's broken, or I'm blocked
* **Attachments** — up to 3 files, screenshots included

## Diagnostics

The form offers to attach technical diagnostics, and this is **on by default**. Expand the section to read exactly what would be sent before submitting.

It covers the selected watch's recent behaviour: fetch backend and timing, content length, the last error with credentials redacted, the failure category and how long it has been failing, retry state, and how many filters of each type are configured. It does not include your API key or your password.

Turning it off is fine — it usually means we have to ask follow-up questions before we can help.

## Faster answers

Two things resolve most tickets before they are written:

* If a watch shows an error, read its [health state](/docs/dashboard/watch-health) first — it names the cause and the fix
* If alerts are too noisy, check [Smart Filters](/docs/dashboard/smart-filters) and [CSS & XPath Filters](/docs/dashboard/css-xpath-filters)

Pro and Business plans get priority handling.