---
title: Channel Routing Policy
area: automation
tags: [automation, assistant, integrations, reference]
created: 2026-03-20
updated: 2026-03-20
status: active
related: [[Infrastructure/Architecture]]
---

# Channel Routing Policy

Use the right communication surface for the right kind of work so zap stays useful without creating context soup or notification fatigue.

## Core rule

Use **Telegram for interrupts** and **Discord for depth**.

## Telegram

Use Telegram for:
- direct personal chat
- reminders
- alerts / watchdog notices
- quick status checks
- lightweight mobile interaction

Avoid using Telegram as the main place for:
- long debugging sessions
- architecture work
- noisy experiments
- multi-step implementation discussions

## Discord

Use Discord for:
- technical debugging
- ongoing project work
- brainstorming / planning
- noisy experiments and model/tool testing
- thread-based scoped work items

Prefer Discord when the work is longer than a few turns, technical/investigative, likely to branch into subtopics, or worth separating into a thread.

## Notification split

Telegram should carry:
- reminders
- watchdog alerts
- backup failures/staleness
- cron failures
- important operational summaries

Discord should carry:
- active debugging work
- investigation notes
- implementation progress in threads
- noisy experiments / test output when a human is actively watching

## Practical examples

- "remind me in 20 minutes" → Telegram DM
- "backup is stale" → Telegram Automation
- "figure out why IMAP is broken" → Discord #dev thread
- "compare three architecture options" → Discord #brainstorming
- repeated webhook/model/provider tests → Discord #automation-lab
