Sophy OS
CS/Ops — Test Environment
Acting as
Connecting to Supabase…
🔌 Connected to the real "Testrun" Supabase project. Reads and writes here hit real rows in outreach_leads, whatsapp_groups, tickets and ticket_messages — this is no longer a local simulation. PDF parsing is still simulated client-side (no real OCR), but the leads it creates are real inserts.
Team side — internal ops

📥 New Leads — import

outreach_leads
📄
Drop a lead-list PDF here, or click to simulate an upload
Extraction is simulated, but the leads are written for real to outreach_leads
Parsing PDF and extracting leads…

📤 Outreach Queue

LeadFirst messageStatus

🎫 Tickets

What's real here vs. still simulated

  • All four tables are the real Testrun Supabase project — outreach_leads, whatsapp_groups, tickets, ticket_messages.
  • PDF drop → lead extraction is simulated client-side; the resulting rows are real inserts into outreach_leads.
  • "Send via WhatsApp" only flips status/sent_at here — actually sending the message and creating the follow-up ticket/group is your n8n/Unipile pipeline's job, not this page's.
  • AI replies you see in a ticket thread are real rows written by your actual AI agent (is_from_ai = true) — this page never fabricates AI messages, only real staff replies and the demo-only "simulate incoming client message" tool.
  • tickets has no lane (CS/Sales/Bookkeeper) or deadline/SLA column yet — those exist in your ops docs but not in the schema, so this view doesn't show them. Worth adding if you want them tracked here.
  • This page uses the Supabase anon key with RLS policies scoped to these four tables. There's no login — anyone with the URL has the same access this page does, so keep the link unlisted.
Lead side — what the client sees on WhatsApp
S
Sophy & Co.
Select a ticket
💬
No conversation selected.
Pick a ticket from the list above or the team panel to see its real message thread.