---
title: "Which alert channel should I use? — Lemwatch Help"
description: "Use PagerDuty for on-call rotations, Slack or Teams for daytime triage, Telegram or ntfy for solo owners, and webhooks for custom pipelines."
canonical: "https://lemwatch.com/help/choosing-integration-channel"
source: "https://lemwatch.com"
---

# Which alert channel should I use?

> Use PagerDuty for on-call rotations, Slack or Teams for daytime triage, Telegram or ntfy for solo owners, and webhooks for custom pipelines.

## Quick answer

 Match the channel to the response pattern: PagerDuty for wake-me-up rotations, Slack/Teams/Discord for team triage during working hours, Telegram/ntfy for solo owners, and webhooks for custom automation.

## Recommended by team size

- Solo : Telegram + email

- Small team (2–5) : Slack or Discord + email

- Agency : PagerDuty for tier-1, Slack per client channel

- Enterprise : PagerDuty + Teams + webhook to SIEM

## Where to find it in Lemwatch

 **Settings → Integrations** — each channel has its own routing rules.

## FAQ

### Should I add all channels?

 No — alert fatigue is real. Start with one primary and one fallback.

### Can I quiet a channel overnight?

 Yes — quiet hours per channel in alert rules.

## Related

- Integrations overview

- Test and verify

- PagerDuty setup


## Related

- [Help centre](https://lemwatch.com/help)
- [What integrations does Lemwatch support?](https://lemwatch.com/help/integrations-overview)
- [How do I test an integration is working?](https://lemwatch.com/help/integration-testing-and-verify)
- [PagerDuty Integration](https://lemwatch.com/help/pagerduty-integration)
- [What does an alert payload look like and how is it signed?](https://lemwatch.com/help/integration-payloads-and-signatures)
- [Lemwatch pricing](https://lemwatch.com/pricing)
- [Client Dashboards](https://lemwatch.com/help/client-dashboards)
- [Changing Your Plan](https://lemwatch.com/help/changing-plan)