Friend Follow-Up CRM

Core Concept

Track personal events and milestones of friends (travel, birthdays, sick family, big life events) and get proactive reminders to follow up — including a draft message.

Input Sources

  • Incoming messages: WhatsApp and Instagram messages mentioning events (parsed automatically)
  • Manual capture: User sends a note via WhatsApp or Telegram to Opus (e.g. “Lisa’s mom is in hospital” or “Tom flies to Japan on Friday”)

Storage

  • Structured database (likely SQLite) with fields:
    • Who (friend name/contact)
    • What (event description)
    • When detected (capture date)
    • When to follow up (calculated or manual)
    • Follow-up type (check-in, congratulate, wish safe travels, etc.)
    • Status (pending / sent / dismissed)
  • Needs deduplication if same event comes from multiple sources

Output

  • Surfaced in daily briefing at the right moment
  • Includes a proposed message (tone-matched, not generic)
  • User reviews, edits if needed, sends

Dependencies

  • Messaging ingestion pipeline (FR-026 email/WhatsApp access)
  • Inbox automation (FR-004)
  • Daily briefing system (FR-012)
  • LLM for message parsing + draft generation

Open Questions

  • SQLite vs structured markdown for storage?
  • How to parse unstructured messages into events reliably?
  • How to calculate the right follow-up moment? (e.g. “flying Friday” → follow up Saturday evening)
  • Privacy considerations — storing friend data

References