Web Chat Pre-Survey Intake for Solar Installation Firms

A website question asking how many panels will fit on a roof cannot produce a reliable technical or commercial answer by itself. Location, roof type, usable area, shading, consumption facility, electricity use and application context must be reviewed before promising capacity, output or payback. The web chat assistant should not perform engineering. It should classify the opportunity, expose missing information and prepare the request for expert review.

Separate Project Type and Decision Stage in the First Message

A residential roof, commercial building, factory, land project and shared property should not enter one generic survey flow. Ask whether the visitor is gathering information, requesting a site survey, comparing proposals or progressing an existing application. This routes the person to useful expertise and content without applying premature sales pressure.

Clarify ownership and decision authority respectfully. A tenant, apartment resident, facilities manager and owner may face different approval and document paths. The assistant must not decide legal eligibility; it should carry decision-maker and stakeholder context into expert review.

Collect Eight Core Fields for Preliminary Review

Confirm the service region with district and project type before asking for a full address or document. If the opportunity fits, reveal required fields gradually. Use conditional checklists approved by experts instead of sending one document list to every visitor. A homeowner should not be asked for irrelevant industrial records, and a factory representative should not receive an incomplete residential form.

Do Not Present Web Chat as a Feasibility Calculator

A satellite image, approximate roof area or electricity bill does not establish feasibility. Structure, fire safety, electrical infrastructure, shading and connection conditions may require field and engineering review. Label any preliminary result as an estimate, and show its method and missing inputs.

EPDK's official unlicensed electricity generation page links to the regulation, document lists and related procedures. Recheck those primary sources during implementation instead of freezing application requirements into chat copy. The assistant should not issue regulatory approval; it should route the question to a professional reviewing current rules.

Request Bills and Documents with Data Minimisation

Consumption context can support a sizing conversation, but an electricity bill may contain a name, address, account number and other personal data. Let the visitor enter only required values as text where possible. When a document is necessary, explain which fields will be used, who can access it and how long it will be retained.

Do not make document upload a gate in the first message. A visitor may first need to understand the process. Open a secure upload step after interest and project type are established. Documents should move into controlled project storage rather than remain indefinitely in a general chat history, with access limited by role.

Do Not Invent Savings or Payback Promises

Electricity prices, load profile, production estimates, financing, maintenance and settlement conditions can change. Without approved current inputs, a specific savings percentage or payback period is misleading. Automation should collect the inputs, while a dated proposal presents the financial scenario with explicit assumptions and expert approval.

The Ministry of Energy and Natural Resources' official solar energy information page provides a general overview of photovoltaic technology and resources such as GEPA; the page itself notes that its information is not a binding official document. Keep educational material separate from project-specific engineering and regulatory decisions.

Match the Survey to Expertise and Region

An empty calendar slot does not mean that the right survey team is available. Residential roofs, industrial sites and land projects require different expertise, safety preparation and visit duration. Narrow the team pool by project type, location, roof access and document status, and do not create a field visit against an unconfirmed address.

• Confirm the decision-maker and site-access contact before the visit.
• Check safe roof-access conditions as a separate field.
• Share an arrival window that reflects route reality.
• Keep missing plans or consumption data visible in the appointment note.
• Do not promise capacity or price before the post-survey engineering review.

Give Sales a Source-Aware Handoff

The handoff should contain project type, location, building and roof context, shading clues, consumption, shared documents, decision stage and questions. Label each fact as a customer statement, document value or system estimate. Never place a conclusion such as suitable roof in the summary without engineering review.

Transfer when confidence is low, a regulatory question appears, shared ownership is unclear or the visitor requests a project-specific production guarantee. After a person takes over, automation should stop issuing new feasibility, price or timing promises.

Do Not Confuse Lead Quality with Response Speed

Fast answers help only when they route the right project to the right expert. Track missing information, incorrect project class, requests unsuitable for a survey, repeated questions, document completion time and reasons for moving from survey to proposal. The goal is not to close more chats; it is to produce cleaner records ready for engineering review.

See our B2B lead qualification guide for the general framework and the pricing page for website-channel scope. Beginning with one project class and one service region makes it easier to measure the value of each question.

Test Technical Boundaries before Launch

• Confirm that a roof photo alone never produces a fixed capacity.
• Test that visitors who decline a bill upload can enter consumption values as text.
• Verify that residential, factory and land projects reach different expert pools.
• Ensure unclear shared ownership and authority move to expert review.
• Recheck official source links regularly for access and current content.
• Confirm that the bot produces no savings, capacity or regulatory approval after human handoff.

Solar Pre-Survey Intake with BozLat AI

BozLat AI can collect project type, location, roof, consumption context and document status gradually through web chat, transfer uncertain requests to specialists and produce a source-aware summary for site-survey booking. It does not replace engineering judgment; it organises the context needed for that judgment. Start with one project type, a limited service region and a question tree approved by the engineering team.