# Alerts

Stay one step ahead of bugs, spikes, and user-flow issues.

Zipy watches every session in real time. **Alerts that turn raw stream into actionable pings** so the right person can jump in on the issue. Choose your channel—Slack, Email, Web-hooks and get notified the moment something goes wrong.

### Which alert is right for you?

| Alert Type                                                     | Why you’d use it                                                          | What it can fire on                                                          |
| -------------------------------------------------------------- | ------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| [**Slack Alerts**](/product-features/alerts/slack-alerts.md)   | Instant visibility for engineering & on-call                              | <p>• Daily or Weekly Digest<br>• Every new error<br>• Error-rate surge</p>   |
| [**Email Alerts**](/product-features/alerts/email-alerts.md)   | Keep cross-functional teams (PM, CS, execs) in the loop                   | <p>• Daily or Weekly Digest<br>• Every new error<br>• Anomaly detection</p>  |
| [**Live Alerts**](/product-features/alerts/live-alerts.md)     | Real-time, user-specific nudges while people are on your site             | Any custom event you emit—e.g. live visit, pricing-page view, signup failure |
| [**Custom Alerts**](/product-features/alerts/custom-alerts.md) | Laser-focused rules with filters, frequencies, and multi-channel delivery | Any metric or error plus filters on browser, OS, URL, release, etc.          |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.zipy.ai/product-features/alerts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.