Lead / Support / Doc Intake

Open-source, local-first intake pipeline for lead routing, support triage, and document handling.

This project is a local-first reference implementation for operations teams. It shows a real multi-step flow:

1. Receive inbound events from a form or webhook-like source
2. Classify them as lead, support, or document intake
3. Enrich and summarize payloads
4. Route each item to the right workflow lane
5. Review everything in a product-style dashboard

Screenshots

Workspace Dashboard

Routing Lanes

What It Shows

• Lead intake routed to CRM
• Support tickets routed to Slack
• Document intake routed to a knowledge lane
• A simulated event form for creating demo payloads locally
• A lightweight API for listing, ingesting, and resetting events

Why This Exists

Most automation demos stop at "upload a file" or "send a webhook." Real ops workflows need:

• multiple event types
• clear routing
• structured enrichment
• a readable review dashboard
• local-first execution for fast iteration and portfolio use

Quick Start

python -m venv .venv
.venv\Scripts\python.exe -m pip install -r requirements.txt
.venv\Scripts\python.exe .\scripts\seed_demo_events.py
.venv\Scripts\python.exe -m uvicorn app.main:app --host 127.0.0.1 --port 8001
.venv\Scripts\python.exe -m streamlit run ui\dashboard.py --server.port 8501 --server.address 0.0.0.0 --server.headless true --browser.gatherUsageStats false

Or use the one-command launcher:

.\scripts\run.ps1

Tests

.venv\Scripts\python.exe -m unittest

Structure

lead-support-doc-intake/
  app/
    api/
    core/
    processing/
    schemas/
    services/
  data/
    demo_events/
    processed/
  scripts/
  tests/
  ui/
  docs/
    screenshots/

Current Demo Data

• Typeform lead submission
• Intercom support ticket
• Dropbox Sign document intake

Backend

• GET /health
• GET /events
• POST /events
• POST /reset

Positioning

Best short description:

Local-first intake automation dashboard for leads, support tickets, and document workflows

The demo uses simulated Typeform, Intercom, and Dropbox Sign events so the workflow can be run locally without exposing customer data or requiring third-party credentials.