Using the AI assistant
The SiteOps assistant isn't a chatbot bolted on the side - it can read your real monitoring, research the open web, and make changes (with your confirmation). This is how to get the most out of it.
It's on by default
Every chat in the web app already has the SiteOps skill enabled - you'll see the chip near the message box. You don't need to turn anything on. If you want a plain, non-monitoring chat, click the × on the SiteOps chip to toggle it off for that conversation.
What you can ask it
The assistant acts as you - it only ever sees and changes your own account, and it never makes a change without asking first.
Read your monitoring (instant, free-ish)
| Ask this | What it does |
|---|---|
what am I monitoring? |
Lists your sites, their status, frequency, and site health scan mode |
how is my site doing? / any incidents? |
Open incidents + per-site health |
what are my monitoring settings? |
Your current config (frequency, alert thresholds, site health scan, timezone…) |
when does my SSL / domain expire? |
Live SSL certificate + domain-expiry check |
explain incident #123 |
Full detail on a specific incident |
Do things
| Ask this | What happens |
|---|---|
start monitoring example.com |
AI drafts a full monitoring setup, shows it, and asks you to confirm before creating it |
change my check frequency to every 5 minutes |
AI shows the exact change and waits for your "yes" before applying |
run a check on my site now |
Queues a real on-demand scan (rate-limited so you can't spam it) |
Research & explain
| Ask this | What happens |
|---|---|
search the web for how to fix a 502 on nginx |
Real web search, summarized with sources |
open example.com and tell me what's on the page |
Loads the page in a real headless browser and reports the rendered content + console errors |
On an incident: explain this |
Explains the root cause and, when useful, researches the error on the web and cites how others fixed it |
Safety: nothing changes without your "yes"
Any tool that changes your monitoring - adding a site, editing settings - works in two steps:
- Preview. The AI shows you exactly what will change (old → new).
- Confirm. Only after you reply yes does it apply.
Read-only questions (status, SSL, incidents) and research (web search, page rendering) run immediately - they can't change anything.
Working on your code too
If you attach a codebase (e.g. a GitHub repo) and keep SiteOps on, you get both toolsets at once - the AI can read your monitoring and read/fix the code that caused an incident, in the same conversation.
Tips
- Be specific. "run a check on example.com now" beats "check stuff."
- It cites sources. When it researches the web, it links what it used.
- It respects your plan. Heavy actions (on-demand scans) are rate-limited, and AI actions draw from your monthly credits - see Plans & AI credits.
- When it can't do something in code (an expired domain, DNS, a down host, an SSL problem, a suspended account), it says so plainly and gives you the manual steps instead of pretending code can fix it.
Want the exact list of everything the AI can call? See the AI tools reference. Building an agent that talks to SiteOps? See For AI agents.