Sol (AI): sales and engineering
Sol is a user row in your team list, marked AI. Assign a lead to Sol in your prospect list and Sol runs the existing pipeline as tools, in order: it reads the prospect, reuses the 3D roof a request from the configurator already carries or reconstructs the roof from the address, places the panels for the target size, simulates the year with the battery sizes your package offers, lists your packages and active price templates, prices the configuration through the rules engine, saves one offer draft, renders the PDF in your template and writes the email to the homeowner in their language. Sol holds no business logic and has no tool to set a price: every total comes from your packages and price templates.
Every step is on the prospect's timeline with its duration and cost. The price and the email are approval items: a person with the prospects permission reads them and clicks Approve or Reject, with a reason the next run sees. Approving the price records that a person saw the total; it changes nothing. Each organisation has a daily budget for Sol's runs and a kill switch.
Engineering notes and the AI disclosure
Sol's engineering notes list what to check on site, in a fixed schema: the roof's suitability per face (tilt, azimuth, area, panel count), shade and any degraded steps in the reconstruction, obstacles kept or dropped, the main fuse question (16, 20 or 25 A), the notice that föranmälan to the grid company is required, where the battery and the inverter go, and the roof material when the classifier is unsure. The draft email asks the homeowner the open questions: main fuse size, yearly consumption, roof age and material, where the electrical cabinet is, EV plans. Every email Sol drafts says that an AI helped prepare it and names the person who reviewed it, per article 50 of the EU AI Act; Sol's display name always ends in (AI).
Write Sol a line
On the prospect page and on Sol's own page there is a text box of up to 2 000 characters. A line such as Huawei package, 10 kWh battery, offer due Friday sets the package (matched by title), the size in kW or panels, the battery, the template, the due date and the language; each resolved choice is shown in the run detail. A choice that matches nothing stops the run and asks you. One run per prospect at a time; a new prompt queues after it.
Admin (AI): the catalogue in order
Admin is the second AI member, with its own tool set. Ask it to raise a price across packages, add or archive a package, change a team member's permissions, invite a colleague, or find stale prospects, duplicates and missing data. Every change comes back as a proposal — a diff such as Package X: 89 900 kr → 92 500 kr — that an owner or admin approves in the approvals inbox; nothing is applied on its own. A bulk change shows a preview and is one undoable batch, with the old values kept in the audit trail. Admin cannot change its own permissions or any AI member's, cannot remove the last owner, cannot touch billing, cannot delete data (archive only) and cannot send an invite without the person's click. Only users with the admin permission can give Admin work.
What never happens without a person
No email, no price and no status change leaves your organisation without a person's approval. Sol and Admin cannot sign, pay, invoice or price outside your packages: those tools do not exist. Text from a homeowner — lead notes, later email replies — goes to the model as data, never as instructions. The data sent is the minimum: no personal identity number, meter number, property designation or phone. The installer is the data controller, Numsolar the processor and the model provider a sub-processor, listed in the data processing agreement before the first run.
