Lead Management

CRM lead management guide — learn how to capture leads from web forms, assign owners automatically, work your pipeline, and convert won deals into customers.

1. 1

   Create a lead manually

   1. Open Leads → Add Lead.
   2. Enter name, company, email, phone, and optional address / social fields.
   3. Set Source, Status, and Owner (assigned staff).
   4. Save — the lead appears in your list and attribution reports.

   Screenshot — add asset to storage/mediafiles/

2. 2

   Or capture automatically

   Most teams prefer inbound capture: embed a Web-to-Lead form on your site, pass UTM parameters, and let the CRM auto-assign the lead. See Web to Lead Forms and Visitor to Paying Customer.

Work leads from the classic list or the visual Kanban board.

• Leads (list) — filter by source, status, owner, prospect type, and score; sort and export via DataTables (Excel, CSV, PDF).
• Leads → Kanban — drag-and-drop pipeline view (requires lead_kanban_module read permission).
• Use Call and SMS chips on the list to log a call or send a message without leaving the page.
• Open a lead to view timeline, notes, tasks, media, proposals, and reminders.
• Use Global Search (top bar) to jump to leads by name or company.
• Created/updated timestamps appear in the list for pipeline hygiene.

From a lead detail page, open the Proposals tab to create and email proposals before conversion.

• Add products/lines, taxes, and discounts — totals calculate automatically.
• Email the proposal PDF/link to the lead; track opens from the CRM.
• Attach tasks, media files, and reminders while the record is still a lead.

When a lead is won, click Convert to Customer.

1. Provide client portal credentials: username, password, and contact title.
2. Proposals, estimates, tasks, media, and reminders move to the new customer record.
3. The lead becomes read-only after conversion — continue work under Customers.

Conversion is one-way; use customer records for ongoing account management. On Kanban, moving a card to a Won stage triggers the same outcome flow — see Kanban vs legacy status below.

Mark unqualified leads as Poor-fit or Dead to keep your pipeline clean.

Use Normalize Lead if a lead was marked incorrectly and should re-enter the active pipeline.

Open Leads → Kanban for a visual pipeline board. Not yet implemented in this codebase.

1. Planned behavior: pipeline switcher, drag/drop stage movement, activity logging, and lead drawer timeline.
2. Planned behavior: filters by search, owner, source, tags, country, value range, and follow-up.
3. Planned behavior: stage probability and weighted forecast totals on each column.
4. Planned behavior: confirmation dialogs when moving to Won or Lost stages.

Configure pipelines under Leads → Pipeline. Not yet implemented in this codebase.

1. Planned behavior: create multiple pipelines and set a default pipeline.
2. Planned behavior: stage fields for name, color, won/lost flags, and probability percent.
3. Planned validation: probability range and mutual exclusivity for won/lost stage flags.
4. Planned behavior: drag-and-drop stage reordering.

Current release uses legacy Lead Source and Lead Status settings under Leads.

Pipeline and starting-stage fields on Leads → Add Lead are not yet implemented in this codebase.

• Current create form supports Source, Status, Owner, Temperature, Score, and Prospect Status.
• Current create form does not include Pipeline or Starting Stage selectors.
• Use legacy status values to track progression until pipeline modules are shipped.

Call logging from a Kanban drawer is not yet implemented in this codebase.

1. Current release supports call logging from the lead list and lead detail actions.
2. Use the Call chip on Leads list for note capture.
3. Twilio integration is available in Office settings where enabled by your installation.

Endpoint POST /lead/make_call_note/{lead} is available in the current release.

Tasks keep follow-up work tied to a lead.

• Open a lead and go to the Tasks tab (/lead/{id}/tasks/).
• Click New task in the card header to add a task immediately.
• From Kanban, open the lead drawer and jump to tasks without losing your place on the board.
• Assign owner, due date, priority, and description — same task model as the global Tasks menu.

See also Tasks & Reminders docs for cron and reminder setup.

Current release uses legacy lead status as the primary stage model.

• Status is shown on list and detail views and is required on create/update.
• Pipeline-stage placement and Kanban synchronization are not yet implemented in this codebase.
• Customer conversion continues to follow the existing Won lead flow.

Summary of the latest lead module capabilities in this release:

• Refreshed lead create/list/detail interfaces with faster actions.
• Inline call/SMS actions from lead list rows.
• Lead task workflow improvements (task page and add-task entry points).
• Web-to-lead capture with UTM and attribution fields (Channel, drilldowns, landing page data).
• Marketing reports — Attribution Dashboard, Lead Source Report, and Campaigns under Marketing (see Marketing & Attribution docs).
• Read-only Marketing Attribution block on lead detail pages.

Configure lead access under Staff → Roles.

• lead_module read/create/update/delete controls lead list, create, update, and delete actions.
• create-lead is required for call-note and SMS actions from the leads list.
• delete-lead is required for delete actions and any future bulk-delete workflow.
• lead_kanban_module and lead_pipelines_module control Kanban and pipeline settings (see Kanban sections above).
• lead_sources_module controls Leads → Lead Sources (see Marketing & Attribution docs).

Expected result: users only see the lead screens and actions granted to their role.

Recommended daily workflow for sales users in the current release:

1. Open Leads and filter by owner, source, and status.
2. Use list-row Call and SMS chips to contact prospects quickly.
3. Open high-priority leads and update status, notes, reminders, and tasks.
4. Convert qualified leads to customers when won.

Use Leads → Kanban for drag/drop stage updates when your role grants lead_kanban_module access.

Lead operations use both session-auth CRM routes and Sanctum API endpoints.

• Session-auth (web): GET /lead, GET /lead/create, POST /lead, PUT /lead/{lead}, DELETE /lead/destroy/{lead}.
• Session-auth actions: POST /lead/send_sms/{lead}, POST /lead/make_call_note/{lead}, POST /lead/sort.
• Session-auth location helpers: GET /api/getCountries, GET /api/getStates/{id}, GET /api/getCities/{id}.
• Sanctum API: GET /api/lead/get_titles, GET /api/lead/getSources, POST /api/lead/storeSource, GET /api/lead/getStatuses, POST /api/lead/storeStatus, POST /api/lead/check_email_availability.

Expected result: browser users use session routes; SPA/mobile integrations use Sanctum API routes where token auth is configured.

Marketing analytics are available under Marketing → Lead Source Report (/marketing/lead-source-report) and on the Home dashboard / Attribution Dashboard.

• Lead source CRUD is under Leads → Lead Sources (/lead/source).
• Charts include leads by source, revenue by source, ROI tables, and campaign performance.
• Export CSV or Excel from the report page header.

Full setup and permissions: see the Marketing & Attribution documentation page.

Use this checklist after updating CRM code and docs:

1. Back up database and application files before deployment.
2. Run php artisan migrate --force.
3. Clear caches: php artisan config:clear && php artisan cache:clear && php artisan view:clear.
4. Verify lead CRUD, source/status lookups, call-note, and SMS actions with a staff role.
5. If Kanban/pipeline modules are expected, confirm their routes and policies exist in your deployed build before enabling user documentation.

Leads screen shows fewer records than expected

Non-admin users only see leads owned by or created by them. Verify owner assignment and role access.

Call/SMS buttons are visible but actions fail

Check role permission create-lead, Twilio/SMS office settings, and browser console/network errors.

Cannot delete a lead

Won leads are protected from delete. Also confirm delete-lead permission.

Where is the Kanban board?

Open Leads → Kanban (/lead/kanban). If the menu is missing, enable lead_kanban_module read on the user’s role.

Lead operations in v3.0 now emphasize faster daily execution: refined lead create/list experience, stronger call/SMS actions, Kanban pipeline views, and marketing attribution on lead detail. Source/status APIs remain available for integrations; full marketing ROI reporting lives under Marketing & Attribution docs.