Investigation: What is the actual state of channel onboarding UX across all...

Documentation for Sessions

📝 Investigation: What is the actual state of channel onboarding UX across all...

Date: 2026-03-21
Time: 17:14:21 UTC
Session: gspace1-250.6
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

What is the actual state of channel onboarding UX across all channel types?

Task: S250: Channel onboarding UX audit

🎯 Decision Made

Chosen:

Audit revealed severe inconsistency: WhatsApp is 95% production-ready (5-step wizard, real validation, test message). Slack/Discord have fake validation ("looks good" without testing credentials). Email assumes SMTP expertise. Telegram and SMS have NO setup UI at all. Critical: Slack/Discord "Test Connection" always passes — users get false confidence their channel works.

Options Considered:

  1. Accept current state (unacceptable — fake validation misleads users)
  2. Full rewrite of channel setup (over-engineered)
  3. Targeted fixes: real validation, webhook URL display, Telegram/SMS forms (chosen for Plan B)

💭 Reasoning

ChannelManagerComponent (vitto-hub) has a multi-step wizard but completion varies dramatically. WhatsApp (S117) went through multiple iterations and is polished. Slack/Discord were added later with minimal UX work — the testConnection() method returns success without actually validating credentials. Email setup assumes users know SMTP configuration. Telegram and SMS are defined in the ChannelType union but have zero form UI. The webhook URL that users need to configure in Slack/Discord app settings is never shown during setup — users complete the wizard thinking they're done, but inbound messages won't arrive because the webhook isn't configured. This is the kind of gap that kills feature adoption: the setup appears to work but silently fails.

📁 Files Involved

🔗 Related

Auto-generated by MCP Smart Consolidation