Desk
Leads
Kanban and table of leads: source, budget, wanted car, owner, calls, reply templates.
Available Route in Desk: /leads
Purpose
A lead is a person who has just enquired but is not yet a client. The "Leads" screen is where you move them from enquiry to contract.
How it should work
- Two views: a kanban by stage and a table with filters by source, manager and budget.
- Lead card: source (site, Telegram, Viber, widget, extension, API, import, marketplace), budget, wanted car, owner, next step.
- "Call": the button opens a call (
tel:) and asks you to record the result and next step. Stage 1 is manual logging; telephony integration (Binotel, Ringostat, Zadarma) comes later. - Call script: questions to ask with fields for answers that fill the sourcing request.
- One-click replies: ready templates for Telegram and Viber with the client's name.
- Auto-assignment of new leads among managers (round-robin) and a "lead without contact for 24 hours" reminder.
A new enquiry automatically creates a "call the new lead" task due in 1 day and notifies the manager: this is already built into the deal stages ("New lead" stage).
What already exists at the service level
The leads service in the core (@core/services) already accepts enquiries from the site, finds duplicates
by phone, email, Telegram and Viber and writes an event for notifications. There is no Desk screen on top of
it yet.