Implement slip/relapse supportive response flow

[BillChirico]

🤝 Implement Slip/Relapse Supportive Response Flow

Overview

Handle the most sensitive moment in recovery — a reported slip — with zero shame and maximum support.

---

Goals

• Immediate supportive acknowledgment
• No statistics, no streak reset shaming
• Offer helpful next steps (not demands)
• Follow up with care (not surveillance)
• Learn from the moment (if user wants)

---

Response Flow

Step 1: Immediate Acknowledgment (0 seconds)

Principles: Warm, non-judgmental, human

Messages:

• "Slips happen. You're not starting over — you're continuing."
• "Thank you for being honest. That takes courage."
• "One moment doesn't erase your progress."

Never say:

• ❌ "Your streak is reset" (no stats)
• ❌ "You were doing so well" (implies failure)
• ❌ "What happened?" (interrogative)

---

Step 2: Supportive Suggestions (if enabled)

Principles: Optional, gentle, actionable

Options presented:

1. "Find a meeting near you" → Tool: meeting finder
2. "Call your sober friend" → Tool: quick dial
3. "Try a breathing exercise" → Tool: breathing
4. "Text your sponsor" → Tool: message composer
5. "Just talk to me" → Continue conversation

UI: Card with 4-5 buttons, user can dismiss

---

Step 3: Follow-up Check-in (24 hours later)

Principles: Caring, not checking up

Messages:

• "How are you feeling today?"
• "No pressure to respond — just thinking about you."
• "If you want to talk about yesterday, I'm here."

---

Step 4: Pattern Learning (opt-in)

Principles: User-controlled, helpful, not invasive

If user agrees:

• "You mentioned work stress — want to explore triggers?"
• Store trigger context for future anticipation
• Suggest coping strategies that worked before

---

Technical Implementation

interface SlipResponseFlow {
  // Step 1: Immediate
  immediateMessage: string;
  tone: 'supportive' | 'gentle' | 'direct';
  
  // Step 2: Suggestions
  suggestionsEnabled: boolean;
  availableTools: Tool[];
  
  // Step 3: Follow-up
  followUpScheduled: boolean;
  followUpTime: Date;  // 24 hours later
  followUpMessage: string;
  
  // Step 4: Learning
  learningPrompt?: string;
  storeTriggerContext: boolean;
}

---

Implementation Tasks

• Design slip response message templates
• Build suggestion cards UI
• Implement tool integration for each suggestion
• Create 24-hour follow-up scheduler
• Build opt-in pattern learning flow
• Add "not helpful" feedback capture
• Test with recovery counselors
• Write comprehensive documentation

---

Acceptance Criteria

• Response sends within 1 second of slip report
• No statistics or streak mentions in any message
• Suggestions are dismissible
• Follow-up sends exactly 24 hours later
• User can disable slip suggestions in settings
• Pattern learning is opt-in, not automatic
• Messages tested with 5+ recovery professionals

---

Testing Scenarios

1. First-time slip vs. multiple slips
2. Different tones (warm, direct, gentle)
3. User disables suggestions mid-flow
4. Follow-up when user is doing better
5. Follow-up when user reports another slip

---

Related

• Parent: [Epic] Sobers Buddy Implementation #412
• Depends on: Set up Vercel AI SDK infrastructure #413, Build message generation and scheduling system #417
• Related: Build user preference settings #415 (settings), Add meeting finder tool integration #419 (meeting finder)

---

Part of Sobers v2

[Mnehmos]

Idea: allow agents to use these tools automatically, with permission.

A recorded slip could be designed to automatically send a message to the users sponsor among other ideas.

Could be invasive, could be worth it. Thoughts?