PTENES
MODULE 2.2

💬 Communication Channels

Telegram, WhatsApp, Discord, Slack, IMAP Email, and voice. Learn the BaseChannel contract and implement any channel in minutes.

6
Topics
60
Minutes
Basic
Level
Hands-on
Type
1

📱 Telegram — The Main Channel

Telegram is the default choice for good reasons: stable API, free, file support, inline buttons, groups, and channels. 95% of personal assistant use cases work perfectly on Telegram.

📡 Polling vs. Webhook

Polling (Recommended for development)

Bot periodically asks Telegram: “Any new messages?” Simple, no infrastructure. Latency of 1–2 seconds.

Webhook (For production)

Telegram sends messages directly to your URL. Requires public HTTPS. Zero additional latency. Ideal for VPS.

💡 Telegram Security

Set TELEGRAM_ALLOWED_USERS to only your IDs. Anyone can message a Telegram bot — without a whitelist, anyone can control your Jarvis.

2

🔗 BaseChannel — The Universal Contract

O BaseChannel is the abstraction that lets the Agent be channel-agnostic. It doesn’t matter whether you use Telegram or Discord — the Agent just calls send(), and the implementation takes care of the rest.

🧩 BaseChannel Interface

class BaseChannel(ABC):

@abstractmethod
async def start(self) -> None:
"""Initializes the connection and starts listening for messages"""

@abstractmethod
async def send(self, user_id: str, message: str) -> None:
"""Sends a response to the user"""

@abstractmethod
async def stop(self) -> None:
"""Closes the connection gracefully"""
3

💚 WhatsApp via Business API

In Brazil, WhatsApp is irreplaceable. The Meta Business API enables official integration — with no risk of a ban, and with support for approved media and templates.

📋 WhatsApp Integration Flow

1

Create a Meta Business account and app

2

Enable the WhatsApp Business API and generate a token

3

Configure a webhook with token verification

4

Implement WhatsAppChannel by extending BaseChannel

4

💬 Discord and Slack

For teams, Discord and Slack are the natural channels. A Jarvis inside the team workspace eliminates the need to leave the platform to ask the assistant questions.

🎮 Discord

  • • discord.py with on_message events
  • • Slash commands for structured interaction
  • • One thread per conversation for organization
  • • Reactions for approval/rejection

💼 Slack

  • • Bolt SDK with OAuth 2.0
  • • Events API for listening to messages
  • • Mention handler (@atlas)
  • • Block Kit for rich responses
5

📧 IMAP Email Channel

Email is the channel with the highest ROI for automation. Triage, categorization, and automatic replies to routine emails saves hours every week without requiring you to change your habits — Jarvis works in your existing inbox.

📬 Email Flow

# Flow Diagram
IMAP mailbox ──→ IMAP poll (30s) ──→ New email?
│
▼
Parse MIME + extract text
│
▼
Agent.process(email)
│
┌───────┴───────┐
Auto-reply Draft for review
6

🎤 Voice Wake Word

The voice channel turns Jarvis into a truly hands-free assistant. With Whisper for transcription and a configurable wake word, you speak naturally and Jarvis responds by voice.

💡 Latency Tip

For real-time voice responses, use Whisper tiny (speed) for transcription and a local TTS model for synthesis. Total latency under 1 second is possible with mid-range hardware.

🎙 Voice Pipeline

Microphone → VAD (detects speech) → Audio buffer
→ Wake word check ("Atlas"?)
→ Whisper STT → transcribed text
→ Agent.process(text)
→ TTS (text-to-speech)
→ Speaker (voice response)

✅ Module 2.2 Summary

✓
Telegram — Default channel: free, robust, polling or webhook
✓
BaseChannel — 3-method contract: start(), send(), stop()
✓
WhatsApp — Meta Business API, HTTPS webhook, high ROI in Brazil
✓
Discord/Slack — Team channels with slash commands and events
✓
IMAP email — Triage and automatic response, with the highest ROI in hours saved
✓
Voice — Whisper STT + wake word + TTS for hands-free interaction

Next Module:

2.3 — Memory and Knowledge: SQLite FTS5, BM25, 2 layers, and automatic compaction

← Module 2.1 Next: Module 2.3 →