Every Tracking Together / Anthony Vasquez lead source, link, and file — gathered into one place and organized by source. Real artifacts only.
The single source of truth. 520 leads digitized 2026-06-04 from Anthony's event-capture sheets, served behind the secured portal (never as a public file).
The full 520-lead dataset: id, name, phone, service, event, status, rep, notes. Served per-login behind Supabase row-level security.
Master + subscriber logins, assign/edit/price, CSV export, Stripe billing. Supabase Auth + RLS.
The client-facing overview East sent Anthony (what the portal does, security model).
Spreadsheet links shared with Anthony, either direction.
docs.google.com/spreadsheets link through Beeper (Google Voice or Google Messages). His leads came in as physical event sheets and were digitized straight into leads.json. The portal replaces the spreadsheet entirely. If a sheet was emailed instead, see section 05.
Canonical thread: Google Voice chatID 381 (pinned). The GVoice bridge spawns a new chatID per session — 381 + 388–469 are all the same Anthony line.
602×440 PNG East sent Anthony showing the live portal. The only image attachment in the thread.
Anthony sent NO CSV, XLSX, or PDF lead file through Beeper. The lead handoff was verbal / physical-sheet, not a file drop.
Apple iMessage threads (via BlueBubbles, not bridged into Beeper).
Lead sources that may live in email and are not reachable from Beeper.
Any "leads" / "Tracking Together" / "Net Meter" / "PFC Farms" email carrying a CSV/XLSX/PDF or a Sheets link — forward to east@xlrd.org to merge into leads.json.
Folder exists but holds no lead file (scaffold only). If the capture sheet is on paper or another device, forward it for digitization.
Named in the account config as TT client automation lists but no file present. Forward the raw lists if they exist.
Computed live from leads.json. Top capture events and statuses.