v3.2.0 — Telegram Best Practices & Market-Adaptive Channels

What's New in v3.2.0

Telegram Upgraded to Strategic Channel

Telegram is no longer a "secondary channel" — it's now a full SDR-capable channel with unique advantages over WhatsApp.

New: skills/telegram-toolkit/

Feature	Description
Bot Commands	/catalog, /quote, /status, /contact, /language — structured self-service
Inline Keyboards	One-tap BANT qualification (product → volume → timeline), 3-5x faster than free-text
Large File Routing	2GB limit vs WhatsApp's 50MB — catalogs, certifications, video demos
Nurture Cadence	Full Telegram nurture sequence (Day 0 → Day 60+) with no window restrictions
Channel Broadcast	One-to-many product announcements via Telegram Channel

Market-Adaptive Channel Priority

Channel priority now depends on the customer's market — no longer hardcoded:

Market	Primary	Secondary
Africa / Latin America / South Asia	WhatsApp	Email
Middle East / Southeast Asia	WhatsApp	Telegram
Russia / CIS / Iran / Eastern Europe	Telegram	Email
Europe / Turkey	WhatsApp	Telegram

WhatsApp 72h Window Auto-Switch

New HEARTBEAT check (#13):

• 48h warning: Send follow-up on WhatsApp before window expires
• 72h expired: Auto-switch to Telegram (no window limit) or Email
• Never mark CRM as "contacted" if delivery actually failed

Other Changes

• WhatsApp corrected to "Business App" (not API) throughout documentation
• TOOLS.md Telegram section expanded from 2 lines to comprehensive guide
• README updated: 13 cron jobs, 7 pre-built skills
• All changes synced to openclaw-delivery/_template

Full Changelog

• a42980c feat: Telegram best practices — market-adaptive channels, bot commands, inline keyboards
• 721f120 feat: upgrade to 4-layer anti-amnesia architecture (v2.0)
• 92e6aef feat: wire anti-amnesia operating protocol into workspace MD files

---

Telegram Quick Setup:

# 1. Get bot token from @BotFather
# 2. Edit config
TELEGRAM_ENABLED=true
TELEGRAM_BOT_TOKEN="your-token"
# 3. Deploy — done. Full SDR pipeline works on Telegram.