From cb2fdcf8f13e6d4a21cb492f000f93d1a3598be0 Mon Sep 17 00:00:00 2001
From: Narasimha-sc <166327228+Narasimha-sc@users.noreply.github.com>
Date: Sat, 7 Feb 2026 15:47:37 +0200
Subject: [PATCH] plans: 20260207-support-bot.md

---
 .../plans/20260207-support-bot.md             | 178 ++++++++++++++++++
 1 file changed, 178 insertions(+)
 create mode 100644 apps/multiplatform/plans/20260207-support-bot.md

diff --git a/apps/multiplatform/plans/20260207-support-bot.md b/apps/multiplatform/plans/20260207-support-bot.md
new file mode 100644
index 0000000000..1b13f70451
--- /dev/null
+++ b/apps/multiplatform/plans/20260207-support-bot.md
@@ -0,0 +1,178 @@
+# SimpleX Support Bot - Strategic Plan
+
+## 1. WHY: Strategic Rationale
+
+### The Problem
+
+SimpleX Chat's unique privacy model creates a paradox: **the very features that make it secure also make it confusing for new users.**
+
+- Users abandon during onboarding because the connection model (no phone numbers, QR codes, links) is unfamiliar
+- When messages don't arrive instantly, users assume the app is broken rather than understanding the relay-queue architecture
+- Support requests go unanswered outside business hours, leaving frustrated users
+- Human support cannot scale with user growth
+
+### User Pain Points (from research)
+
+| Pain Point | Impact |
+|------------|--------|
+| "How do I add someone?" | Blocks first use entirely |
+| "Messages aren't arriving" | Destroys trust in the platform |
+| "No notifications" | Users miss messages, blame SimpleX |
+| "Battery draining" | Users uninstall |
+| "Groups don't work like Signal" | Feature confusion |
+
+### Strategic Value
+
+1. **Reduce churn at critical moments** - Help users when confusion strikes, not after they've given up
+2. **Scale support without scaling headcount** - Handle repetitive questions automatically
+3. **Improve consistency** - Every user gets the same high-quality answer
+4. **24/7 availability** - Support across all timezones
+5. **Preserve human bandwidth** - Escalate only complex issues to humans
+6. **Demonstrate the platform** - The bot itself showcases SimpleX capabilities
+
+---
+
+## 2. WHAT: Scope & Deliverables
+
+### Core Capabilities
+
+| Capability | User Need Addressed |
+|------------|---------------------|
+| **Onboarding Assistance** | Guide users through connection model, QR codes, sharing links |
+| **Delivery Troubleshooting** | Explain delays, suggest fixes, set expectations |
+| **Notification Help** | Platform-specific guidance for Android/iOS settings |
+| **Group Chat Guidance** | Explain capabilities and limitations vs other messengers |
+| **Battery Optimization** | Practical tips to reduce power consumption |
+| **Human Escalation** | Seamless handoff when bot cannot resolve |
+
+### User Outcomes
+
+Users should be able to:
+- Connect with their first contact within 5 minutes of asking for help
+- Understand why a message is delayed and what to do
+- Fix notification issues without leaving SimpleX
+- Know what groups can and cannot do before creating one
+- Reach a human when the bot cannot help
+
+### In Scope (MVP)
+
+- Automated responses for top 5 user pain points
+- Welcome experience for new connections
+- Recognition of "I need a human" requests
+- Logging of unresolved queries for improvement
+
+### Out of Scope (Future)
+
+- Proactive outreach (messaging users first)
+- Multi-language support
+- Voice/video call assistance
+- Account recovery
+- Payment/subscription support
+- Bug reporting intake
+
+---
+
+## 3. SUCCESS METRICS
+
+### Primary KPIs
+
+| Metric | Target | Why It Matters |
+|--------|--------|----------------|
+| **Automated Resolution Rate** | 70%+ | Bot handles majority without human |
+| **First Response Time** | <5 seconds | Instant help builds trust |
+| **Escalation Rate** | 15-25% | Too low = false resolutions; too high = bot not helping |
+| **User Return Rate** | Track | Do users come back with new questions? (good sign) |
+
+### Anti-Metrics (Things to Avoid)
+
+| Anti-Metric | Signal |
+|-------------|--------|
+| **Frustration Loops** | User asks same question 3+ times |
+| **Immediate Escalation Requests** | Bot responses unhelpful |
+| **False Resolution** | User stops responding but issue unresolved |
+| **Conversation Abandonment** | User disconnects mid-conversation |
+
+### Qualitative Signals
+
+- User thanks the bot
+- User successfully completes suggested action
+- Escalated conversations resolved faster (context preserved)
+
+---
+
+## 4. PRIORITIES
+
+### P0: Must Have (MVP)
+
+| Priority | Rationale |
+|----------|-----------|
+| Onboarding support | #1 user blocker - without this, users never start |
+| Message delivery troubleshooting | #1 complaint - perceived reliability |
+| Human escalation path | Safety net - bot must never be a dead end |
+| Reliability | Bot must always respond - silence is worse than wrong answer |
+
+### P1: Should Have (v1.1)
+
+| Priority | Rationale |
+|----------|-----------|
+| Notification guidance | High-frequency issue, platform-specific |
+| Feature education | Reduces confusion, increases engagement |
+| Conversation context | Humans need history when they take over |
+
+### P2: Nice to Have (v1.2+)
+
+| Priority | Rationale |
+|----------|-----------|
+| Platform-specific guidance | Android vs iOS nuances |
+| Comparison content | "How is this different from Signal?" |
+
+### P3: Future Vision
+
+| Priority | Rationale |
+|----------|-----------|
+| Learning from escalations | Bot improves over time |
+| Proactive onboarding | Reach out before users get stuck |
+| Analytics dashboard | Understand support patterns |
+| Multi-language | Expand global reach |
+
+---
+
+## 5. STRATEGIC ALIGNMENT
+
+### How This Supports SimpleX Mission
+
+| SimpleX Value | Bot Alignment |
+|---------------|---------------|
+| **Privacy** | Bot runs on SimpleX itself - no external services |
+| **Decentralization** | Bot uses same infrastructure as users |
+| **Transparency** | Open source, auditable responses |
+| **User empowerment** | Teaches users to help themselves |
+
+### Competitive Positioning
+
+- **Signal**: No in-app support - users search forums
+- **Telegram**: Bot ecosystem exists but privacy questionable
+- **SimpleX**: Private, instant, helpful support within the secure platform
+
+---
+
+## 6. RISKS & MITIGATIONS
+
+| Risk | Mitigation |
+|------|------------|
+| Bot gives wrong answers | Human review of FAQ content; easy escalation |
+| Bot creates false confidence | Clear "I don't know" responses; never guess |
+| Users expect AI chat | Set expectations in welcome message |
+| Bot becomes spam vector | Rate limiting; no proactive messaging initially |
+| Answers become outdated | Regular content review tied to releases |
+
+---
+
+## 7. DECISION LOG
+
+| Decision | Rationale |
+|----------|-----------|
+| Start with FAQ, not AI | Predictable, auditable, controllable |
+| MVP = 5 topics only | Focus on highest-impact pain points |
+| Human escalation from day 1 | Bot must never be a dead end |
+| Run on SimpleX, not external | Dogfooding; demonstrates platform capability |