Leads
Owner & Manager proposed · D145Everyone who messaged you but isn’t a customer yet, by where they came from and how far they got (§29).
Owner & Manager access only
Leads hold phone numbers of people who aren’t customers yet (§22, D145). Staff see their own bookings only.
New leads, 30 days
48
+15 vs last 30 days
Booked
29 60%
22 booked in the chat, 7 by staff
First reply
1m 12s
AI receptionist; staff 14 min
Best source
Click-to-WhatsApp ad
“oct-cleaning” · 21 leads, 14 booked
Where leads come from (30 days)
| Source | Leads | Booked | Visited | Booked % |
|---|---|---|---|---|
| Click-to-WhatsApp ad “oct-cleaning” | 21 | 14 | 9 | 67% |
| QR at the door | 9 | 6 | 5 | 67% |
| Facebook bio link (Messenger) | 11 | 6 | 4 | 55% |
| Website button | 7 | 3 | 2 | 43% |
Also in Custom reports as the “Leads” source. Lost leads with no booking are deleted after 12 months (§22).
Implementation notes for Cursor
Entities: Lead (channel, name, phone_enc/phone_hmac, source, source_ref, interest, status new/contacted/booked/visited/lost, lost_reason, assigned_staff_id, customer_id, booking_id, conversation_id).
Key states: created by the New lead automation on a first message from an unknown number (one open lead per phone); status moves by itself (first reply → contacted, booking → booked, completed → visited); staff can drag a card back or mark lost with a reason; 90 days idle → lost (no reply); Book for them opens New appointment with the phone and name filled.
Forbidden inventions: no bulk messaging from this page; no full phone numbers (masked; full number only inside the chat); no Staff access.
Governs: ARCHITECTURE §29, §22; D145; PLAN-428.