# Post-MVP Channel Expansion Wave

## Summary

After the current Slack plus Telegram package and the Vietnam Zalo package are settled, expand the next channel wave deliberately.

Current target list:

- Discord
- WhatsApp
- Google Workspace
- Microsoft Teams

## Status

Planned

## Why

These channels matter, but they should not blur the earlier launch gates.

The backlog should show them as the next expansion wave instead of leaving them implied in README prose only.

## Scope

- define the first MVP slice for each target channel
- rank the channels by expected adoption and implementation leverage
- note major transport or auth differences that affect the current channel model
- split the highest-priority channel into a follow-up implementation task when ready

## Non-Goals

- full parity across every communication channel in one milestone
- replacing the current Slack or Telegram delivery work before it is stable enough

## Exit Criteria

- one prioritized channel-expansion list exists
- each candidate channel has a short MVP note
- backlog order reflects the intended expansion wave

## Related Docs

- [Launch MVP Path](../../../overview/launch-mvp-path.md)
- [Channels Feature](../../../features/channels/README.md)
- [API Channel MVP](2026-04-04-api-channel-mvp.md)
