Support for Siteimp Watch
Clear, practical help for using Siteimp Watch, with support material focused on local-first monitoring, in-app guidance, notifications, and support logs.
Support built around Watch
Watch In-App Support
The first Siteimp Watch support section is Watch In-App Support , a small but practical library of page-by-page guidance that mirrors the help built directly into the application.
These documents explain what each Watch page is for, what you can do there, and how the page fits into the local monitoring workflow. If you are setting up Watch, checking a property, reviewing a target, or adjusting notifications, start there.
Local-first monitoring help
Monitoring overview
Siteimp Watch is not a hosted uptime platform. It is a local-first desktop monitoring app. It checks the targets your computer can reach, including public websites, localhost development servers, staging environments, LAN tools, and private operational pages.
The monitoring support pages explain how Watch organizes properties, targets, check results, schedules, statuses, and inherited defaults. They are written for the app as it actually works, not for a cloud product wearing a borrowed cape.
Settings, notifications, and support logs
Settings
The Settings support page explains app-wide monitoring defaults, notification defaults, Slack and Discord destinations, test notifications, and the local support log tools built into Watch.
Watch keeps support logs local unless you choose to copy, save, or open them. Monitoring notifications use user-owned Slack or Discord destinations. Support requests use the application-owned support path. Those boundaries are intentional.
What Watch support will look like
Siteimp Watch is small on purpose. The support section follows the same idea: practical guidance for the screens and workflows people actually use, without pretending the product is larger, cloudier, or more mysterious than it is.
Page-by-page guidance
Each Watch support document explains one screen or workflow in plain language, including what the page is for, what you can do there, and what to check when something needs review.
Local-first explanations
Watch runs on your computer. The documentation explains what that means for monitoring, schedules, sleep, support logs, localhost targets, and private pages that hosted services cannot see.
Notifications without fog
Watch can send monitoring alerts and recovery notices to destinations you configure. The support pages explain the difference between app defaults, property routing, target eligibility, and support delivery.
Support logs under user control
Support logs are local files. Watch can list them, copy them, save them, or open the folder, but it does not attach those logs to support requests automatically.
What exists today
Right now, Watch support is intentionally focused. The app is ready for deeper testing, so the priority is useful web-based support for the screens that exist today.
Watch In-App Support
A dedicated support section for the screens and workflows built into Siteimp Watch. It mirrors the in-app HelpDrawer support documents and gives each page a stable web home.
Add property
A practical guide to creating a monitored property and its first target, including primary URLs, monitoring defaults, notification routing, and common setup validation messages.
Property dashboard
A support page for reviewing a monitored property, managing targets, pausing or resuming monitoring, and understanding property-level notification routing.
Settings
Guidance for Watch settings, including app defaults, Slack and Discord notification destinations, test messages, and the support log tools in the Settings page.
Why this section exists
Siteimp Watch is a local-first Windows application for monitoring targets from the computer where it runs. That makes its support needs a little different from a hosted monitoring service. Users need to understand not just what the app shows, but what it means that the app is local.
A local monitoring app can check localhost, staging sites, LAN tools, private pages, and public websites without sending those targets through a hosted scanner. It also means Watch only runs while the app process is alive and the computer is awake. Good support should make those tradeoffs obvious before they become confusing.
This section is being built with that goal in mind. It gives the Watch app a public support home, keeps the in-app help and website help aligned, and explains local-first monitoring in practical terms.