LeadCaptureMT is a multi-tenant lead capture and project processing system. It is designed for solar project lead management where a client team can capture leads, upload required documents, assign vendors, track vendor execution, and generate PDFs containing complete lead details, actions, documents, vendor progress and product information.
2. Main Portals
| Portal | URL Pattern | Used By |
|---|
| Super Admin | /admin/account/login | System owner / master administrator |
| Client | /client/{client}/account/login | Client admin, team leader and agent users |
| Vendor | /vendor/{client}/account/login | Vendor users assigned to solar projects |
| Help Manual | /help | All users |
Replace {client} with the client subdomain/slug, for example client1.
3. Installation and First Setup
- Publish the ASP.NET Core project to IIS or run it locally from Visual Studio.
- Configure SQL Server connection in `LeadCaptureMT.Web/appsettings.json`.
- Run `Db_Create_LeadCaptureDb.sql` on SQL Server Express or your SQL Server instance.
- For existing installations, run update scripts such as `Db_Add_LeadSolarFields.sql` and `Db_Add_VendorManagementAndUploads.sql` only once.
- Make sure the web application has write permission to `wwwroot/uploads` because lead documents and vendor progress uploads are stored there.
- Open `/admin/account/login` and log in as Super Admin.
- Create or verify the client, client users, features and master data.
4. Super Admin Help
Super Admin manages the master setup across all clients.
Typical Super Admin work:
- Create and activate clients.
- Manage master features.
- Enable or disable features for each client.
- Create or edit client users when required.
- Change the Super Admin password.
Recommended first steps:
- Go to Manage Clients and create the client.
- Go to Master Features and verify required features.
- Go to Client Features and enable features for the selected client.
- Create at least one Client Admin user.
- Share the client login URL with the client team.
5. Client Admin Help
Client Admin manages the operational setup for one client.
Client Admin can:
- Create and manage leads.
- Manage lead statuses.
- Manage users.
- Manage property/project site master.
- Manage vendor master.
- Assign a vendor to a lead.
- Upload required solar project documents.
- Download lead PDF.
- View vendor progress and vendor product details.
- Export lead data to CSV.
6. Lead Management
The Lead form includes contact fields, project details, pricing/payment fields and vendor assignment.
Important lead fields:
- Lead name, mobile, WhatsApp, email, city and pincode.
- Project floor.
- Roof type: concrete, asbestos, tin or editable value.
- Project type: on-grid, off-grid or hybrid.
- Phase: single phase or three phase.
- Consumer type: domestic, commercial or industrial.
- Consumer name and consumer number.
- Project price, discount and net project price.
- Payment type: cash, loan or both.
- Cash amount and loan amount where applicable.
- Project description.
- Main lead name and sub lead name.
- Vendor selection from Vendor Master.
7. Required Solar Documents
Lead Create/Edit provides an upload section for solar project documents:
- PAN card scan copy.
- Electricity bill scan copy.
- Self photo scan copy.
- Cancel cheque or bank passbook first page scan copy.
- ITR upload for loan above 2 lakh.
Documents uploaded against a lead are visible to the client team and to the assigned vendor. Vendors can download documents only for projects assigned to that vendor.
8. Lead PDF
The Lead PDF contains:
- Complete lead contact details.
- Consumer details.
- Project details.
- Pricing and payment details.
- Lead status and follow-up details.
- Uploaded required documents list.
- Lead action history.
- Assignment audit history.
- Vendor work progress.
- Vendor product details.
Use the PDF button from the Lead list or Lead edit screen to create a PDF for a lead.
9. Vendor Master
Client Admin can open Vendors from the client panel.
Vendor Master stores:
- Vendor name.
- Contact person.
- Mobile number.
- Email address.
- Vendor details/address.
- Username.
- Password.
- Active/inactive status.
Vendor login URL format:
/vendor/{client}/account/login
Only active vendors can log in.
10. Vendor Project Processing
When a lead is assigned to a vendor, the vendor can log in and view only assigned projects.
Vendor project listing shows:
- Lead number.
- Lead generation date.
- Customer information.
- Project information.
- Vendor project starting date.
- Vendor project complete date.
- Progress count.
Vendor project details allow the vendor to:
- Set project start date.
- Set project completion date.
- View and download uploaded lead documents.
- Submit daily work progress with compulsory progress date.
- Upload supporting files for progress steps.
- Fill company name and power rating/type for solar panel, inverter, cable and structure.
11. Vendor Work Progress Steps
Vendor work progress includes these steps:
- Registration and subsidy amount certificate generation - PDF upload.
- Slip of paid payment amount of customer - PDF upload.
- Product dispatch to customer.
- Basement work or concrete work.
- Structures work.
- Earthing work 3 point.
- Panel setting.
- Inverter installing.
- Wiring.
- Solar meter.
- Net metering.
- Subsidy amount to customer.
- Proper monitoring and remarks.
Progress date is compulsory. The system validates the date in the browser and again on the server.
12. Vendor Product Details
Vendor fills product details for:
| Sr.No | Product | Power Rating and Type | Company |
|---|
| 1 | Solar Panel | Vendor fills | Vendor fills |
| 2 | Inverter | Vendor fills | Vendor fills |
| 3 | Cable | Vendor fills | Vendor fills |
| 4 | Structure | Vendor fills | Vendor fills |
The client team can view these details from the Lead Edit page and in the Lead PDF.
13. Users and Access Control
Roles used in the system:
- Super Admin: full system setup.
- Client Admin: full client setup and all client lead operations.
- Team Leader: team-level lead handling according to configured logic.
- Agent: own and unassigned leads according to configured logic.
- Vendor: assigned solar project processing only.
Important security rules:
- A vendor can see only projects assigned to that vendor.
- A vendor can download only documents of assigned projects.
- Client users cannot log in from the vendor portal.
- Vendor users cannot log in from the client portal.
14. Assignment Audit and Lead Actions
Assignment Audit records who assigned a lead, from whom, to whom, action date, remarks, IP address and user agent where available.
Lead Actions are used to record follow-up activities such as call, WhatsApp, visit, status remarks or other communication. Lead actions are included in the lead PDF.
15. Upload Storage
Uploaded files are stored under wwwroot/uploads.
Important folders include:
- `wwwroot/uploads/lead-documents/...`
- `wwwroot/uploads/vendor-progress/...`
Recommended maintenance:
- Include `wwwroot/uploads` in daily backup.
- Do not manually rename or delete uploaded files unless database records are also handled.
- Ensure IIS application pool identity has write permission.
16. Backup
Recommended backup items:
- SQL Server database `LeadCaptureDb`.
- Application folder.
- `wwwroot/uploads` folder.
- `appsettings.json` after removing or securing credentials.
- Database scripts used for deployment.
17. Troubleshooting
Login not working
- Check correct portal URL.
- Check active status of user/vendor/client.
- Reset password if the password is not known. Password hashes cannot be decrypted.
Upload not working
- Check file size and file type.
- Check write permission on `wwwroot/uploads`.
- Check IIS request upload limit if uploading larger files.
Vendor cannot see a project
- Confirm the lead has selected vendor in Lead Edit.
- Confirm vendor is active.
- Confirm vendor is logging in under the correct client URL.
Vendor cannot download a document
- Confirm the lead is assigned to that vendor.
- Confirm the physical file exists in `wwwroot/uploads`.
- Confirm the upload folder has read permission for the application pool.
SQL column missing
- Run `Db_Add_LeadSolarFields.sql` and `Db_Add_VendorManagementAndUploads.sql` once on the existing database.
18. Deployment Notes
- Target framework: .NET 8.
- Hosting: IIS with ASP.NET Core Hosting Bundle installed.
- Database: SQL Server Express or compatible SQL Server.
- Connection string: configured in `appsettings.json`.
- Static files must be enabled because help files, CSS and uploads are served from `wwwroot`.
19. Quick Operating Flow
- Super Admin creates client and client admin.
- Client Admin logs in and creates users, statuses, properties and vendors.
- Agent or Client Admin creates a lead.
- Client Admin uploads required solar documents and assigns vendor.
- Vendor logs in and opens assigned project.
- Vendor enters dates, updates progress steps and fills product details.
- Client team reviews progress from Lead Edit and exports/prints Lead PDF.
20. Help Links
- Online help inside the application: `/help`
- Downloadable manual: `/help/LeadCaptureMT_HelpManual.docx`
- Static HTML manual: `/help/help-manual.html`